Energy Web Documentation
  • Energy Web Ecosystem
  • Launchpad by Energy Web
  • EWC Validator Documentation
  • Community Ressources
  • Legacy documentation
  • Welcome to Energy Web
  • Glossary
  • Solutions 2023
    • ↔️Data Exchange
      • Data Exchange Overview
      • Data Exchange Architecture
      • Use Cases and Refrence Implementations
        • Digital Spine for Electricity Markets
          • Digital Spine Integration Client Deployment Guide - from Azure marketplace
        • E-Mobility Management
    • 🔌Open Charging Network
      • Create and Manage an OCN Identity
      • Connect an OCPI/OCN Party to a Node
        • 1. Make your backend service OCN-ready
        • 2. Select an OCN Node and register in OCN Registry
        • 3. Manage your Whitelist and Blacklist
        • 4. Connect your service to an OCN Node
      • Run an OCN Node
      • Use the OCN Service Interface
        • Offer an OCN Service
        • Sign up for an OCN Service
      • Develop on the Test Network
      • Develop on the Production Network
      • Open Source Development
        • Maturity Model, Feature Roadmap and Releases
        • Developer Community Calls
      • E-Mobility Dashboard v0.1
  • EW-DOS Technology Components 2023
    • EW-DOS Overview
    • Worker Nodes
      • Worker Node Process Diagrams
      • Worker Node Architecture
      • Worker Node Guides
        • Deploy Worker Nodes
        • Customize Worker Logic
    • Identity and Access Management (IAM)
      • IAM Guides
        • Implement an SSI Hub instance
        • Verifiable Credential API
        • Sign-In with Ethereum
        • Using Switchboard
          • Switchboard Transaction Cost Estimates
      • IAM Patterns
        • Assets as Ownable Smart Contracts
        • Credential Lifecycle
        • Credential Metadata
        • SSI Credential Governance using ENS Domains
      • IAM Libraries
      • SSI Hub
      • Switchboard Application
    • Decentralized Data Hub (DDHub)
      • DDHub Message Broker
      • DDHub Client Gateway
      • DDHub Patterns
        • Channels and Topics
      • DDHub Guides
    • Green Proofs Contracts
    • Energy Web X
    • The Energy Web Chain
      • EWC Overview
      • System Architecture
        • Proof-of-Authority Consensus Mechanism
        • System Contracts
          • Name Registry
          • Holding Contract
          • Block Reward Contract
          • Validator-Set Contracts
        • Validator Node Architecture
      • Energy Web Block Explorer
      • Validator Node Installation Specifications
        • Volta Test Network: Validator Node Installation
      • Energy Web Chain Governance
      • EWC Guides and Tutorials
        • Getting started with Energy Web Chain
        • Developing on the Volta Test Network and Main Network (Energy Web Chain)
        • Run a Local RPC Node
          • Run RPC Node using Nethermind client
        • Deploy a Smart Contract on Volta with Remix
        • Interacting with Smart Contracts in EW-DOS
        • Set up MetaMask to interact with Energy Web Chain
        • Using the Ethereum Name Service
        • Using Oracles
      • Energy Web Token (EWT)
  • 🧠Foundational Concepts
    • Open-Source Software
    • Scaling Access to Grid Flexibility
    • Facilitating Clean Energy Purchases
    • Ethereum
      • Transactions and Transaction Costs
    • Self-Sovereign-Identity
      • Self-Sovereign Use Case Interaction
    • Cryptocurrency Wallets
      • Software cryptocurrency wallets
        • Metamask
        • Mycrypto wallet
      • Hardware cryptocurrency wallets
      • Hierarchical Deterministic (HD) Wallets
Powered by GitBook
On this page
  • What are cryptocurrency wallets used for?
  • Multisignature Wallets
  • Related Content
Export as PDF
  1. Foundational Concepts

Cryptocurrency Wallets

PreviousSelf-Sovereign Use Case InteractionNextSoftware cryptocurrency wallets

Last updated 3 years ago

What are cryptocurrency wallets used for?

Cryptocurrency wallets are used to:

  1. 'Store' and exchange cryptocurrency - tokens or cryptocurrencies are actually stored as records on the blockchain itself, but they are associated with a user's private key, which is stored in a cryptocurrency wallet.

  2. Authorize transactions on a blockchain

There are many different wallets available, many of which are built to be compatible with a specific blockchain like Ethereum or Bitcoin. You can choose to use a (discussed below), use only software or web-based wallets, or use a combination of both.

Cryptocurrency wallets are used in decentralized, peer-to-peer environments that have no central oversight or source of authority. Because of this, trust mechanisms are built into wallet functionality. Methods and implementations vary, but most cryptocurrency wallets use cryptographically seeded public-private key-pairs that serve as a way for users to identify themselves and safely validate and authorize transactions on the blockchain. The public key serves as their address in a network, and their private key (which should never be shared) serves as as a method for authorizing transactions. It serves as your digital signature. In EW-DOS, the user's public key is used as the identifier in their DID that is anchored on the blockchain. You can read more about this .

You should never lose track of or share your private key(s) with anyone. Anyone with access to the private key can access the funds of that key's account.

Regardless of your choice of hardware wallet, we highly recommend that you use when developing with or using EW-DOS. MetaMask is a browser-based cryptocurrency wallet. It is both an Ethereum-compatible wallet and a gateway for using decentralized applications built on . We discuss MetaMask's functionalities

Multisignature Wallets

A multi-signature wallet is a that allows multiple parties to agree on transactions before execution. It is analogous to a joint bank account.

One pain point of "traditional" crypto wallets is that anyone who has access to the wallet's private key has total authority over the wallet’s funds: they can move funds or perform transactions with no limitations or accountability.

If an account is managed by multiple people, each person knows the private key and can therefore make transactions at their discretion without group consensus. Risk remains even if an account is managed only by one person. In this case, if the private key is stolen, someone else now has total control over the wallet and the funds in it.

A multi-signature addresses these pain points. You can set multiple owners for a wallet and the number of minimum confirmations needed to perform transactions. It gives robust security for private users and businesses. Some benefits include:

  • No single-point-of-failure: If your wallet has 3 owners and 2 confirmations are needed to execute a transaction (2-­of-­3 scheme), and one of the private keys gets stolen or lost, the funds can still be accessed, or the compromised owner's address can be removed or changed. A wallet with 2-­of-­3 scheme can tolerate 1 failure, a wallet with 3-­of-­5 scheme can tolerate 2, etc.

  • Accountability: No more insider theft. The transaction history, details, and the approvers of a transaction can be viewed.

  • Daily withdrawal limit: an amount can be determined that can be withdrawn daily without confirmations

  • Ease of use: less operational burden than a hardware wallet

Related Content

There are a number of multi-signature wallets for the Ethereum network. One of the most widely used is the Gnosis Safe Multisig. You can view the smart contracts for Gnosis Safe .

🧠
here
Connect a Trezor Hardware Wallet
Set up MetaMask to interact with Energy Web Chain
here
MetaMask
Ethereum-based blockchains like the Energy Web Chain
smart contract
hardware wallet
below.