Assets

An Iroha asset is a numeric balance held by an account. Every concrete balance points to an AssetDefinition, and the definition describes how that asset can be named, minted, displayed, and partitioned.

Asset Definition

An AssetDefinition contains:

• id: the canonical asset definition address
• name: a human-readable display name
• description: optional human-readable description
• alias: optional alias in <name>#<domain>.<dataspace> or <name>#<dataspace> form
• spec: numeric precision and constraints for balances
• mintable: the mintability policy
• logo: optional SoraFS URI
• metadata: arbitrary key-value metadata
• balance_scope_policy: whether balances are global or dataspace-restricted
• owned_by: the account that registered or owns the definition
• total_quantity: total issued quantity
• confidential_policy: policy for shielded asset operations

Asset definition IDs are canonical opaque addresses. When a definition is constructed from a domain and a name, Iroha can keep that domain/name projection for UX and queries, but the canonical text form is the generated address.

Asset Balance

An Asset contains:

• id: an AssetId, which combines the asset definition, holder account, and optional balance scope
• value: a Numeric balance

The holder account is canonical and domainless. The asset definition may be projected under a dataspace-qualified domain, for example payments.universal.

Mintability

Asset definitions support these mintability modes:

Mode	Meaning
Infinitely	Elastic supply. The asset can be minted and burned repeatedly.
Once	Fixed-supply token. It can be minted once and then burned.
Not	Fixed-supply token that can be burned but not minted again.
Limited(n)	Minting is allowed for a limited number of additional operations.

Use Infinitely for normal elastic assets and Once or Limited(n) for fixed-supply or bounded-supply assets. Do not use Not as an initial policy unless the asset supply is already established.

Balance Scope

The balance_scope_policy controls how balances are bucketed:

• Global: one balance bucket per account and asset definition
• DataspaceRestricted: balances are partitioned by dataspace context

Dataspace-restricted balances are useful when the same asset definition is used across multiple Nexus dataspaces but balances must remain isolated.

Instructions

Assets can be registered, minted, burned, and transferred with Iroha Special Instructions:

• Register and Unregister
• Mint and Burn
• Transfer
• SetKeyValue and RemoveKeyValue

See also:

• CLI guide
• Rust tutorial
• Python tutorial
• JavaScript/TypeScript tutorial
• Data model