AMAX Whitepaper
  • 😌Armonia Meta Chain platform
    • 1.10 Introduction
    • 1.20 Objectives & Principles
    • 1.30 Armonia Key Innovation Technology Introduction
  • 🧰Overall Architecture
    • 2.10 Multichain Model
    • 2.20 Multichain Layered Architecture
    • 2.30 Multichain Transaction Routing
    • 2.40 Multichain Enabled Application Scenarios
    • 2.50 Cross-Chain in Armonia's Multichain Universe
    • 2.60 Cross-Chain Mechanism
  • βš™οΈArmonia Meta Chain
    • 3.10 Basic Profile
    • 3.20 Consensus Algorithm
    • 3.30 Account
  • πŸš€Armonia Meta Chain PRODUCT
    • Armonia RealMe Account
    • AMAX UP
  • 😎Armonia First Child Chain
  • 🫑Tokenomics
    • 5.10 Token Distribution
    • 5.20 Mining of Things (MoT)
  • 🌐Infrastructure Support for Web3
  • 😜xDAO Governance
  • πŸŽ›οΈTechnology Roadmap
  • πŸ‘¨β€πŸ‘©β€πŸ‘¦Core Team
  • πŸ“šReference
Powered by GitBook
On this page
  1. Armonia Meta Chain

3.30 Account

Rather than utilize a public-key derived address to denote each account, AMC adopts an account model based on an account name. One account can be bound from one or multiple public keys and the key requires its owner to register/activate it before any transaction can be made within the account. Each account name is composed of 12 alphanumeric characters ([1-5,a-z,.]) and can be extended to support 24 such characters ([1-9,a-z,.,#,@]). To participate in all kinds of transactions, account owners must stake a certain amount of $AMAX tokens to reserve a certain amount of system RAM, CPU, network and other resources.

Previous3.20 Consensus AlgorithmNextπŸš€Armonia Meta Chain PRODUCT

Last updated 1 year ago

βš™οΈ