Skip to main content
You don’t need these details to issue or accept an asset: the SDK builds and reads asset transactions for you. Arkade Assets live on unspent outputs, next to BTC, and move through Arkade transactions. Each transaction records its asset transfers in one OP_RETURN output, so Bitcoin needs no changes to support them.

Asset ID

Each asset is identified by a pair: (genesis_txid, group_index).
  • genesis_txid is the ID of the genesis transaction, the transaction that first issued the asset.
  • group_index is the position of the asset in that transaction. One transaction can issue several assets.
The asset ID never changes. Wallets and integrators identify an asset by its ID, not by its name or ticker. The SDK writes an asset ID as 68 lowercase hex characters: the genesis transaction ID, then the group index as 2 little-endian bytes. The first asset issued in transaction <txid> has the ID <txid>0000.

Control Assets

A control asset is an Arkade Asset that lets its holder issue more units of another asset. The issuer names the control asset in the genesis transaction. It can’t be added later.
  • To reissue, a transaction must spend the control asset. A transaction that creates more units than it spends, without the control asset, is rejected.
  • Burning the control asset fixes the supply for good. Existing units keep circulating.
  • Whoever holds the control asset can reissue. To hand over this right, send the control asset to another wallet.
  • An asset can’t be its own control asset.
  • Control isn’t transitive. If asset B controls asset A, reissuing A needs only B, not the control asset of B.

Asset Metadata

Metadata is a set of key-value pairs that the issuer sets in the genesis transaction. It can’t change after issuance. Four fields have a known meaning: name, ticker (a short symbol such as "USDT"), decimals (the display precision), and icon (an image URL). Any other key-value pairs are valid too. The genesis transaction carries the full set in its asset packet. The metadataHash is the Merkle root of the set, with one leaf for each key-value pair:
This matches the BIP-341 taptree construction. A short proof shows that one key-value pair belongs to the metadata, without the full indexer state.

Burns

A transaction burns units of an asset when it spends them and assigns them to no output. The SDK’s burn call builds this transaction. The operator rejects an Arkade transaction that spends outputs holding assets without an asset packet that lists every one of those assets. Bitcoin can’t reject an onchain transaction that does the same, so indexers treat those assets as burned and remove them from their state. A tool that spends onchain outputs holding assets must include an asset packet, or the assets are lost.

Transaction Format

Asset Packet

Every Arkade Asset transaction holds one asset packet, in exactly one OP_RETURN output. The packet is a TLV (type-length-value) stream that starts with the ASCII magic bytes ARK (0x41524b):
The asset record has type 0x00:
A transaction is rejected if it has more than one OP_RETURN output with the ARK magic bytes, or more than one type 0x00 record across its TLV streams.

Asset Groups

The asset payload is an ordered list of asset groups, one for each asset that the transaction issues or moves. Each group lists how many units of the asset the transaction spends, and which outputs receive them. The position of a group in the list is its group index. In each group, the output amounts can’t exceed the input amounts. A fresh mint, and a reissuance that spends the control asset, are the two exceptions.

Assets in Batch Swaps

Virtual outputs expire, and a batch swap renews them before they do. When a batch swap renews a virtual output that holds assets, the new virtual output holds the same assets. The operator provides no asset liquidity for this. Moving assets between virtual outputs and onchain outputs is planned.

Issue Assets

Create assets with the TypeScript SDK

Send Assets

Transfer assets between wallets

Virtual Outputs

How offchain outputs work