Docs · Network
The asset lifecycle in the Console
Create, mint, burn and transfer, and who may do each.
The four operations
There are four, and there is nothing else. No generic administrator, no freeze, no blacklist, no authority transfer and no mutable metadata — so none of those appears in any screen, because x/assets has no message for them.
| Operation | Where | Who |
|---|---|---|
| Create | Assets → Create an asset | ADMIN, with the organization's signing key |
| Mint | Assets → an asset | ADMIN, CAPPED_MINTABLE only, up to the cap |
| Burn | Assets → an asset | ADMIN, from the organization's own balance |
| Transfer | Assets → an asset | ADMIN, and the chain's rules for the asset |
AVAILABLE Mint, burn and transfer from the Console — /projects/[projectId]/assets/[assetId]
Where: Console → Assets → an asset
First: The same signing key. A FIXED asset has no mint at all.
Requires: ADMIN
Two conditions, not one
Asset operations require ADMIN, and ADMIN alone is not sufficient. The organization must also have a signing key provisioned in Bengar Custody, and the caller must be the principal it is bound to.
The two are held by different mechanisms and revoked independently: taking ADMIN away stops the person asking, on the next request; retiring the key stops any signature being produced, for everybody, without touching anybody's role. An organization that wants issuance separated from administration provisions the key to somebody who is not the day-to-day administrator.
ADMIN is not universal authority. It cannot approve, author policy or register a permit, and no new role was invented for assets: a sixth name in a table, grantable by the same administrator, would be a word rather than a control.
AVAILABLE Provision the organization's chain signing key — /projects/[projectId]/assets
Where: Console → Assets
Requires: ADMIN
Results, and the one that is not an answer
- Committed — in a block, with a height and a transaction hash.
- Refused — the chain rejected it, with its own code and words. It is not in a block and never will be.
- Unknown — nobody knows yet whether it landed.
UNKNOWN is not a failure, and there is no retry. The same signature at the same sequence either lands once or the account has moved on, and a second different transaction at that sequence is the failure the sequence slot exists to prevent. The way out of UNKNOWN is somebody finding out what happened and recording it.
Every derived figure carries the height it was derived at. A supply read from the index is not the same fact as a chain-confirmed result, and the Console does not present them as one.