- Send transactions to transfer its token
- Raise up a proposal
- Vote for the proposal
- Deploy smart contracts
- Trigger the smart contracts released by itself or others
Account Type
AxiomLedger has two account types:- General account - Externally-Owned Account (EOA), controlled by anyone with the private key
- Contract account - a smart contract deployed on the AxiomLedger network and controlled by code. No one owns the private key of the contract accounts.
- Receive, hold, and send AXM or tokens
- Interact with deployed smart contracts
Account & Key Pair
An account consists of a cryptographic pair of keys - a public key and a private key. The public key can be mapped to an address, while the private key is used to sign transactions. This key pair helps to prove that a transaction was actually signed by the sender and prevents malicious attack. This prevents malicious actors from broadcasting fake transactions because you can always verify the sender of a transaction. For example, if Alice wants to send AXM from her account to Bob’s, she must create and sign a transaction and send it to the AxiomLedger network for verification. With the public key, Alice can prove that she originally initiated the transaction request. Without the encryption mechanism, malicious attacker Cathy might be able to publicly broadcast a similar request, “send 5 AXM from Alice’s account to Cathy’s account”, while no one can validate whether or not the transaction is exactly requested by Alice herself.External-Owned Account(EOA) Creation
AxiomLedger’s key pair generation algorithm is exactly the same as that of Ethereum, which uses the elliptic curve digital signature algorithm ECDSA-secp256k1. The process of key pair generation is:- First, generate a random private key, which consists of 64 hexadecimal characters.
- Then, a public key is generated from the private key according to the Elliptic Curve Digital Signature Algorithm.
- Finally, take the last 20 bytes of the Keccak-256 result of the public key.