E Money Network
  • Introduction to E Money Network
  • Add E Money Network to Metamask
  • Wallet Integration
  • E-Money Tokens
  • E Money Network Mainnet and Testnet Explorer​
  • E Money Network Faucet
  • E Money Network Whitelist
  • Launching Your Dapp on E Money Network
    • Developing and Deploying Contracts​
    • Contract Verification​
    • Contract Security Checks
  • Validating on E Money Network
    • Validator nodes
    • How to run a validator node on E Money Network
    • Running Validator Node
    • EMYC Token’s Utility & Purpose
    • Install Validator node​
  • Tendermint & EVMOS
    • ABCI Overview
      • Intro to ABCI
      • Motivation
    • Gas & Fees
      • How are Gas and Fees Handled on E Money Network?​
      • Gas calculation and Transaction execution on E Money Network
    • Keyring
    • Signing
    • Transactions
    • A Note on Determinism
    • Consensus Overview
  • E Money Card FAQs
    • Is a Know Your Customer (KYC) process required to obtain an E Money Card?
    • What details are required for the KYC process?
    • Do I need to create an E Money Wallet to order an E Money Card?
    • What happens if I lose my seed phrase?
    • What happens if I forget my password?
    • How do I order an E Money Card, and are there any costs?
    • Can I have the card shipped to a different address than the one I provided during KYC?
    • My card has been delivered, what’s next?
    • What should I consider before using the E Money Card for payments?
    • Where can I use the E Money Card?
    • Can I add the E Money Card to online payment services like Google Pay and Apple Pay?
    • Which countries’ citizens are eligible to apply for an E Money Card?
    • Are there any fees I should be aware of as a user?
    • How do taxes apply when using the E Money Card?
  • E Money Card Fees
  • Branding and Logos
Powered by GitBook
On this page
  1. Tendermint & EVMOS

Keyring

PreviousGas calculation and Transaction execution on E Money NetworkNextSigning

Last updated 3 months ago

Create, import, export and delete keys using the CLI keyring.

The keyring holds the private/public keypairs used to interact with the node. An initial validator key needs to be set up before running the node so that blocks can be correctly signed. The private key can be stored as a file in different locations called for the operating system's own key storage.

To create a new key in the keyring, run the add subcommand with a <key_name> argument. You will have to provide a password for the newly generated key.

This command generates a new 24-word mnemonic phrase, storing it to the relevant backend before it outputs this information about the keypair. If this keypair is to be used to hold value-bearing tokens make sure to write down the mnemonic phrase somewhere safe!

By default, the keyring generates an eth_secp256k1 key. The keyring also supports ed25519 keys, which may be created by passing the --algo flag. A keyring can hold both types of keys simultaneously.

"backends"