VeChain Docs
  • Welcome to VeChain
  • Blockchain Basics
    • Introduction to blockchain
    • Introduction to digital property
    • The evolution of the internet
  • Introduction to VeChain
    • About the VeChain blockchain
      • Consensus Deep Dive
      • Governance
    • Dual-Token Economic Model
      • VeChain (VET)
      • VeThor (VTHO)
    • Acquire VeChain Assets
    • Sustainability
  • Core Concepts
    • Networks
      • Thor Solo Node
      • Testnet
      • Mainnet
    • Nodes
      • Node Rewards Programme
    • Blocks
      • Block Model
    • Transactions
      • Transaction Model
      • Transaction Fees
      • Transaction Calculation
      • Meta Transaction Features
        • Transaction Uniqueness
        • Controllable Transaction Lifecycle
        • Clauses (Multi-Task Transaction)
        • Fee Delegation
          • Multi-Party Payment (MPP)
          • Designated Gas Payer (VIP-191)
        • Transaction Dependency
    • Block Explorers
    • Wallets
      • VeWorld
        • User Guide
          • Setup
          • Wallet
          • Signing
          • Activities
          • Settings
        • FAQ
      • Sync2
        • User Guide
          • Setup
          • Wallet
          • Signing
          • Activities
          • Settings
        • FAQ
      • Sync
        • User Guide
          • Wallet
          • Ledger Device
          • Browser dApps and web
          • Interact with dApps
          • Activities
          • Settings
          • Report an Issue
          • Contributing
        • FAQ
    • EVM Compatibility
      • VeChain Modifications
      • Methodology
      • Test Coverage
        • Gas model
        • Raw transaction
        • hardhat specific
          • Ganache failures
          • evm_increaseTime
        • Failures in constructor
        • eth_sign
        • Contract address prediction
        • BadBeacon proxy address at 0x1
      • How to Recreate
      • Additional Information
        • Using Governance Contracts
        • ERC1820/ERC777 Testnet
        • Delegate Options
    • Account Abstraction
      • UserOperation
      • Bundler
      • EntryPoint Contract
      • Account Factory Contract
      • Paymaster Contract
    • Token Bound Accounts
  • How to run a node
    • Nodes
    • How to run a Thor Solo Node
    • Custom Network
    • Connect Sync2 to a Thor Solo Node
  • Developer Resources
    • Getting Started
    • How to build on VeChain
      • Connect to the Network
      • Read Data
        • Read Blocks
        • Read Transactions
        • Read Accounts
        • States & Views
        • Events & Logs
        • VET Transfers
      • Write Data
        • Transactions
        • Fee Delegation
      • Listen to Changes
        • Events
        • VET Transfers
        • Transactions
        • Blocks
        • Beats
      • Build with Hardhat
      • Utilities
        • BigInt and Unit-Handling
        • Name Service Lookups
    • Example dApps
      • Buy me a Coffee
      • Token Bound Accounts
      • PWA with Privy and Account Abstraction
    • EVM Compatibility for Developers
      • Key Architectural Differences and Optimizations
      • Practical Implications for Developers: Key Considerations
      • RPC Methods (Detailed Breakdown)
      • Frequently Asked Questions (FAQs)
      • VeChain Blockchain Specifications
      • Key Differences Between VeChain and Ethereum (Summary)
      • Best Practices for Developing on VeChainThor
    • How to verify Address-Ownership
      • Next.js Session Verification
    • Debug Reverted Transactions
    • Account Abstraction
    • VIP-191: Designated Gas Payer
      • How to Integrate VIP-191 (I)
      • How to Integrate VIP-191 (II)
      • How to Integrate VIP-191 (III)
    • Index with Graph Node
      • Setup with Docker
      • Index with OpenZeppelin
        • Create Subgraph Project
        • Configure Contracts
        • Deploy Subgraph and start Indexing
        • Track Subgraph Indexing
        • Access Subgraph
        • Update Subgraph
    • SDKs & Providers
      • SDK
        • Architecture
        • Accounts
        • Bloom Filter
        • Certificates
        • Contracts
        • Cryptography
        • Debug
        • Encoding
        • Polls
        • Subscriptions
        • Thor Client
        • Transactions
      • Thor DevKit
        • Installation
        • Usage
          • Cryptography
          • Accounts
          • Encoding
          • Transactions
          • Certificates
          • Bloom Filter
      • DApp Kit
        • v2
          • Installation
          • React
            • Installation
            • Usage
          • Vanilla JS
            • Installation
            • Usage
          • Core
            • Installation
            • Usage
          • Theme Variables
          • i18n
        • v1
          • Installation
          • React
            • Installation
            • Usage
          • Vanilla JS
            • Installation
            • Usage
          • Core
            • Installation
            • Usage
          • Theme Variables
          • i18n
          • Node Polyfills
          • V0 to V1
        • v0
          • Installation
          • Usage
          • React
            • Installation
            • Usage
          • Vanilla (UI)
            • Installation
            • Usage
          • Styles (UI)
          • i18n
      • VeChain Kit
      • DevPal
      • Web3-Providers-Connex
        • Installation
        • Usage
      • Connex
        • Installation
        • API Specification
    • Frameworks & IDEs
      • Hardhat
      • Remix
    • Built-in Contracts
    • VORJ
    • Useful Links
  • How to contribute
Powered by GitBook
On this page
  • What are blockchain wallets?
  • How does a blockchain wallet work?
  • What are the different types of wallets and what are their use cases?
  • What's a seed phrase and why should I never give it to anyone?
  • VeChain Wallets

Was this helpful?

  1. Core Concepts

Wallets

An intro and taxonomy of the different types of wallets.

What are blockchain wallets?

A blockchain wallet, also known as a cryptocurrency wallet, is a software application or a physical hardware device used to store and manage cryptocurrency assets. It provides a way for individuals to interact with a blockchain network, enabling them to send, receive, and store digital assets such as VeChain, bitcoin, ethereum and many more.

How does a blockchain wallet work?

A blockchain wallet consists of two primary components: a public address and a private key. The public address serves as the wallet's identifier and is used to receive funds. It is similar to a bank account number, and you can freely share it with others to receive payments or transactions.

On the other hand, the private key is a secret cryptographic code that grants ownership and access to the funds stored in the wallet. A private key is like the pin to your credit card, it should be kept secure and never shared with anyone, as it enables control over the associated cryptocurrency assets.

VeChain nor any of its affiliates will ever request you to share your private key. Never share your private key, this will most likely result in a loss of assets.

What are the different types of wallets and what are their use cases?

Wallets come in a wide variety of different implementations, so it's important to research and choose a reputable wallet provider that aligns with your security preferences and cryptocurrency needs. Generally, a user makes a tradeoff between security and convenience when choosing a wallet.

In fact, its good practice to have multiple wallets for different use cases. We do this in the real world when dealing with fiat money, we have a wallet with some cash, a credit account in a bank to easily withdraw from and a savings account, which requires more effort and time to access funds. The below table defines some of the configurations a wallet can come in.

Type
Description
Secure
Convenient

Self-custody

Wallet provider doesn't manage PK.

High

Medium

Custodian

Manages PK for a user.

Low

High

Cold wallet

Wallet is not connected to the internet.

High

Low

Hot wallet

Wallet is connected to the internet.

Low

High

Web wallet

A wallet in a web browser.

Low

High

Software wallet

A downloadable application to use on laptop, phone or tablet.

Medium

Medium

Hardware wallet

A physical device designed to securely store PKs.

High

Low

Paper wallet

Printing a public address and PK on a physical piece of paper.

High

Low

*PK: Private Key

The above entries are not mutually exclusive, for example, VeChain's new VeWorld wallet is a self-custody, hot, web wallet.

What's a seed phrase and why should I never give it to anyone?

A seed phrase is private key encoded in a human-readable format which typically consists of 12 or 24 randomly chosen words from a predefined word list. The seed phrase is a backup mechanism that allows users to restore their wallet and access their funds by generating the private keys. These words are generated using cryptographic algorithms that ensure they are unique and provide sufficient entropy to secure the private keys.

It is crucial to keep the seed phrase secure and confidential because anyone who possesses it can regenerate the private keys and gain access to the associated funds, regardless of whether they are using the same wallet you currently use. It is recommended to store the seed phrase in a safe and offline location, such as writing it down on a piece of paper and keeping it in a secure place like a safe deposit box. Experts also advise storage in multiple locations, to protect yourself from a natural disaster destroying the paper the phrase is written on.

VeChain nor any of it's affliates will ever request you to share your seed phrase. Never share your seed phrase, this will most likely result in a loss of assets.

VeChain Wallets

VeChain has a selection of wallets for you to use to securely and conveniently manage your VeChain based assets.

PreviousBlock ExplorersNextVeWorld

Last updated 11 months ago

Was this helpful?

VeWorld

Sync2

Sync