Issue Assets

Setup

Import the SDK and create a wallet:

import { MnemonicIdentity, RestArkProvider, Wallet } from '@arkade-os/sdk'

const identity = MnemonicIdentity.fromMnemonic("abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon about")

const wallet = await Wallet.create({
  identity,
  arkProvider: new RestArkProvider('https://arkade.computer'),
})

Your wallet needs available BTC before it can issue. Each asset sits on a virtual output that also holds BTC. See Receiving Payments to fund your wallet.

Basic Issuance

Create a new asset with a fixed supply. Asset amounts are bigint values in base units:

const { arkTxId, assetId } = await wallet.assetManager.issue({
  amount: 1000n,
})

Response shape:

interface IssuanceResult {
  arkTxId: string           // Arkade transaction ID
  assetId: string           // permanent asset identifier
}

The returned assetId is the permanent identifier for this asset. See Asset ID for how it’s calculated. To inspect the issuance transaction, open https://arkade.space/tx/<arkTxId> in the Arkade Explorer. Since no control asset is specified, the supply is permanently capped at 1000 units.

Without a control asset, the supply cannot be increased after issuance.

Issuance with a Control Asset

To retain the ability to reissue (increase supply), reference a Control Asset during issuance. The control asset is itself an Arkade Asset that authorizes supply changes. A common pattern is to first issue a control asset, then use it to authorize the main asset:

// 1. issue a control asset (a simple 1-unit asset)
const { assetId: controlAssetId } = await wallet.assetManager.issue({
  amount: 1n,
})

// 2. issue the main asset, referencing the control asset
const { assetId } = await wallet.assetManager.issue({
  amount: 500n,
  controlAssetId,
})

console.log('Asset ID:', assetId)
console.log('Control Asset ID:', controlAssetId)

As long as you hold the control asset, you can reissue more units of the main asset.

The control asset is a regular Arkade Asset. Transferring or burning it transfers or revokes reissuance authority. See Control Assets for the full rules.

Issuance with Metadata

Attach metadata at issuance time. Metadata is immutable once set — see Asset Metadata for how it’s committed.

const { assetId } = await wallet.assetManager.issue({
  amount: 100_000_000n, // [100.000000]
  metadata: {
    name: 'Tether USD',
    ticker: 'USD₮',
    decimals: 6,
    icon: 'https://tether.to/images/logoMarkGreen.svg',
  },
})

Known Metadata Fields

Field	Type	Description
`name`	`string`	Human-readable asset name
`ticker`	`string`	Short symbol (e.g., “USD₮“)
`decimals`	`number`	Decimal places
`icon`	`string`	URL to an image for display

You can include additional custom fields beyond these. Each value must be a string, a number, or bytes (Uint8Array). To read back the metadata after issuance, see Verify Asset Metadata.

For Issuers

For Integrators

Setup

Basic Issuance

Issuance with a Control Asset

Issuance with Metadata

Known Metadata Fields

Next Steps

Reissue & Burn

Send Assets

​Setup

​Basic Issuance

​Issuance with a Control Asset

​Issuance with Metadata

​Known Metadata Fields

​Next Steps

Reissue & Burn

Send Assets

Setup

Basic Issuance

Issuance with a Control Asset

Issuance with Metadata

Known Metadata Fields

Next Steps