Ergo Namespace - Assets

Author Yuriy Gagarin
Status Draft
Type Standard
Created 2023-11-04
Updated 2023-12-12
Requires CAIP-2, CAIP-19


Ergo supports custom tokens as first-class citizens as outlined in [EIP-0004].

A transaction can create tokens from thin air in its outputs if the Asset ID matches the ID of the transaction’s first input ([box]). Since the box identifier is cryptographically unique, it’s impossible to have a second asset with the same identifier. This rule also implies that only one new asset can be created per transaction.

The ID format for fungible (ERC20-equivalent) and non-fungible (ERC-721 equivalent) tokens is the same. The process for issuance of either is also the same. The only difference is that NFTs must have specific values (see [EIP-0004]) for certain properties.

Specification of Asset ID

Asset ID is a 32 byte array encoded as a hex string. When issued, it is equal to the ID of the transaction’s first input that issued this asset.


The syntax of Ergo Asset ID:

address:    namespace + ":" chainId + ":" + reference
namespace:  ergo
chain ID:   32-character prefix from the hash of the genesis block
reference:  Ergo Asset ID represented as hex string


# Ergo Mainnet

# Ergo Testnet

  • [Token][token] overview
  • [Ergo Box][box] overview
  • [About addresses in Ergo Documentation][address format]
  • [Ergo Assets standard][EIP-0004] [box]: [token]: [address format]: [EIP-0004]:

Copyright and related rights waived via CC0.


Please cite this document as:

Yuriy Gagarin, "namespaces/ergo-caip19: Ergo Namespace - Assets [DRAFT]," Chain Agnostic Namespaces, ergo-caip19, November 2023 / December 2023. [Online serial]. Available: