Skip to content
LogoLogo

UTXO & native assets

Arrekta is a UTXO chain like Bitcoin, with one change that matters for issued assets: every output carries an asset id next to its amount and lock.

output = asset_id 32 ‖ amount u64 ‖ lock

The native coin, ARRK, has its own id. Every other asset is created by an issuance record inside an ordinary transaction, so there are no token contracts to audit: issuance, minting, freezing and clawback are consensus rules (§7).

Conservation

For every asset other than ARRK, the inputs plus newly issued and minted units must equal the outputs (burn outputs count as outputs). For ARRK, inputs must be at least the outputs, and the difference is the fee. Issuing an asset also costs an issuance fee in ARRK (10 ARRK on mainnet, 1 ARRK on testnet and regtest).

Issuing an asset

An issuance record declares:

FieldRule
ticker^[A-Z][A-Z0-9]{1,9}$, unique chain-wide, not ARRK/TARRK/RARRK
name1–64 Unicode code points, no control characters
decimals0–18
amount, max_supplyfixed supply: amount == max_supply; mintable: amount ≤ max_supply
flagsMINTABLE (0x01), FREEZABLE (0x02), CLAWBACK (0x04)
metadata_hashSHA3-256 of a ARRK-AMS-1 metadata document, or zero

The asset id is TH("asset", prevout_of_input_0 ‖ u32(issuance_index)). It is unique because an outpoint can be spent only once.

Authority and control tokens

Issuer powers are themselves UTXOs, so they can sit behind multisig or a policy lock:

  • A MINTABLE asset gets one authority token. Minting requires spending it in the same transaction, and the total can never exceed max_supply.
  • A FREEZABLE or CLAWBACK asset gets one control token. Freezing a holder's lock, unfreezing it, or clawing back their coins requires spending it.

Issuer controls are opt-in and public

  • Controls are fixed at issuance, visible in the asset record, and cannot be added later.
  • Freeze sets a flag on an (asset, lock) pair: that lock can neither spend nor receive the asset. Other assets on the same lock are unaffected.
  • Clawback spends a holder's coin without their signature (the witness is empty); the value goes wherever the transaction's outputs send it, so conservation still holds.
  • ARRK can never be frozen or clawed back.
  • Burning the control token removes the controls permanently.

For regulated assets, the issuer service adds registries, transfer restrictions through co-signed managed addresses, governed controls and a public transparency log on top of these consensus rules.

Metadata (ARRK-AMS-1)

The metadata_hash commits to a canonical JSON document (sorted keys, no whitespace) with at least schema, ticker, name and issuer. Assets with controls must also publish a controls_policy. The node's POST /v1/tools/metadata-hash computes the hash (Assets API).