Skip to main content

Accounts

A Cudos account is a pair of keys used to uniquely identify a user (or entity) and allow them to authenticate and verify transactions on the Cudos Network.

Wallet accounts

There is a difference between a wallet account and a Cudos account.

Accounts on Cudos chain

There are two keys: A Public Key and a Private Key.

The Public Key is used to generate an Address (or multiple addresses).

An Account object is an implementation of an account keypair. It stores the following:

  1. Public Key (PubKey)
  2. Address derived from the Public Key
  3. Account number (AccountNumber)
  4. Sequence

Example Account object

type BaseAccount struct {
Address string `protobuf:"bytes,1,opt,name=address,proto3" json:"address,omitempty"`
PubKey *types.Any `protobuf:"bytes,2,opt,name=pub_key,json=pubKey,proto3" json:"public_key,omitempty"`
AccountNumber uint64 `protobuf:"varint,3,opt,name=account_number,json=accountNumber,proto3" json:"account_number,omitempty"`
Sequence uint64 `protobuf:"varint,4,opt,name=sequence,proto3" json:"sequence,omitempty"`
}

Public key

The Public Key - PubKey is safe to disclose and is used to verify a user or entity's identity.

Addresses

There are 3 types of addresses that specify a context where an account is used:

PubKey is used to generate Address using algorithms. This is the 'normal' account address associated with an account.

Address Types

Other address types can be generated from a single public key for specific purposes.

For example a Validator node can have two address types:

Validator address: This has the prefix cudosvaloper e.g. cudosvaloper123456vn9muexdczyv3agc6kacx

Normal address: This has the prefix cudos e.g. cudos1gj2xtqk66h123456zyv3ag9fcuem. This is the 'self delegate' address used for staking funds to a validator node.

Consensus address This has the prefix cudosvalcons. This address identifies validator nodes that are participating in consensus.

Addresses are public and safe to share. These are also known as Wallet Addresses.

Addresses are also used to identify users or entities on the Cudos Network. For example as owners of a wallet or authorised signatories.

Sequence is used to prevent replay attacks. Each transaction contains the current sequence number for the signer. This number increments every time a transaction is signed, therefore, the sequence number must match the sequence number on the chain.

A replay attack occurs when a malicious actor intercepts a network and is able to delay or resend a transaction or even perform it in advance due to network congestion.

Cudos Network utilises the Cosmos SDK auth module to protect the network at the transaction level. Transactions are protected by private key signatures and the sequence value to prevent selective replaying of transactions. :::

Create a new account

Use cudos-noded CLI to create a new account with a name of your choosing.

cudos-noded keys add <account_name>

You are prompted to save your mnemonic.

Example

cudos-noded keys add flamenco

- name: flamenco
type: local
address: cudos1a9dza8agsc0rse8u36gchke3qlhll5rhg4p48f
pubkey: '{"@type":"/cosmos.crypto.secp256k1.PubKey","key":"AsUvNj8klmJK2fXRBna+9c1CrLeTixQfRJMw198Nt9R7"}'
mnemonic: ""


**Important** write this mnemonic phrase in a safe place.
It is the only way to recover your account if you ever forget your password.

strike donate coconut patrol amazing accuse cherry bid twin fence decline dentist

View existing accounts

Use cudos-noded CLI to list all your accounts.

cudos-noded keys list

Example

cudos-noded keys list
- name: flamenco
type: local
address: cudos1a9dza8agsc0rse8u36gchke3qlhll5rhg4p48f
pubkey: '{"@type":"/cosmos.crypto.secp256k1.PubKey","key":"AsUvNj8klmJK2fXRBna+9c1CrLeTixQfRJMw198Nt9R7"}'
mnemonic: ""

Query account balance

cudos-noded query account <account-address>

Example

cudos-noded query account cudos1a9dza8agsc0rse8u36gchke3qlhll5rhg4p48f