Link Search Menu Expand Document


Version: 0.1

Status: Stable

Authors: Andrea Maria Piana [email protected]

Status interactions with the Ethereum blockchain

This specification documents all the interactions that the Status client has with the Ethereum blockchain.

All the interactions are made through JSON-RPC. Currently Infura is used. The client assumes high-availability, otherwise it will not be able to interact with the Ethereum blockchain. Status nodes rely on these Infura nodes to validate the integrity of the transaction and report a consistent history.

Key handling is described here

  1. Wallet
  2. ENS


The wallet in Status has two main components:

1) Sending transactions 2) Fetching balance

In the section below are described the RPC calls made the nodes, with a brief description of their functionality and how it is used by Status.

  1. Sending transactions
  2. Fetching balance

Sending transactions


EstimateGas tries to estimate the gas needed to execute a specific transaction based on the current pending state of the backend blockchain. There is no guarantee that this is the true gas limit requirement as other transactions may be added or removed by miners, but it should provide a basis for setting a reasonable default.

func (ec *Client) EstimateGas(ctx context.Context, msg ethereum.CallMsg) (uint64, error)


PendingNonceAt returns the account nonce of the given account in the pending state. This is the nonce that should be used for the next transaction.

func (ec *Client) PendingNonceAt(ctx context.Context, account common.Address) (uint64, error)


SuggestGasPrice retrieves the currently suggested gas price to allow a timely execution of a transaction.

func (ec *Client) SuggestGasPrice(ctx context.Context) (*big.Int, error)


SendTransaction injects a signed transaction into the pending pool for execution.

If the transaction was a contract creation use the TransactionReceipt method to get the contract address after the transaction has been mined.

func (ec *Client) SendTransaction(ctx context.Context, tx *types.Transaction) error

Fetching balance

A Status node fetches the current and historical [ECR20] ( and ETH balance for the user wallet address. Collectibles following the ECR-721 are also fetched if enabled.

A Status node supports by default the following tokens. Custom tokens can be added by specifying the address, symbol and decimals.


BlockByHash returns the given full block.

It is used by status to fetch a given block which will then be inspected for transfers to the user address, both tokens and ETH.

func (ec *Client) BlockByHash(ctx context.Context, hash common.Hash) (*types.Block, error)


BlockByNumber returns a block from the current canonical chain. If number is nil, the latest known block is returned.

func (ec *Client) BlockByNumber(ctx context.Context, number *big.Int) (*types.Block, error)


FilterLogs executes a filter query.

Status uses this function to filter out logs, using the hash of the block and the address of interest, both inbound and outbound.

func (ec *Client) FilterLogs(ctx context.Context, q ethereum.FilterQuery) ([]types.Log, error)


NonceAt returns the account nonce of the given account.

func (ec *Client) NonceAt(ctx context.Context, account common.Address, blockNumber *big.Int) (uint64, error)


TransactionByHash returns the transaction with the given hash, used to inspect those transactions made/received by the user.

func (ec *Client) TransactionByHash(ctx context.Context, hash common.Hash) (tx *types.Transaction, isPending bool, err error)


HeaderByNumber returns a block header from the current canonical chain.

func (ec *Client) HeaderByNumber(ctx context.Context, number *big.Int) (*types.Header, error)


TransactionReceipt returns the receipt of a transaction by transaction hash. It is used in status to check if a token transfer was made to the user address.

func (ec *Client) TransactionReceipt(ctx context.Context, txHash common.Hash) (*types.Receipt, error)


All the interactions with ENS are made through the ENS contract

For the stateofus.eth username, one can be registered through these contracts

Registering, releasing and updating


Usernames MUST be in a specific format, otherwise they MAY be slashed:

ENS names are propagated through ChatMessage and ContactUpdate payload. A client SHOULD verify ens names against the public key of the sender on receiving the message against the ENS contract

Copyright and related rights waived via CC0.