Docs · Network
Creating an asset
What is decided at creation, and cannot be changed afterwards.
Decided once
- Name, symbol and decimals — immutable.
- Supply model: FIXED or CAPPED_MINTABLE.
- For CAPPED_MINTABLE, the maximum supply — it can never be raised.
- For CAPPED_MINTABLE, the mint authority.
Everything in that list is permanent. There is no metadata update message, so a typo in a symbol is permanent too.
From the Console
The Console builds the transaction, shows exactly what will be signed, and signs it with the organization's key held in Bengar Custody. The Console never sees a private key and there is no screen that could show one.
- Open Assets and provision the organization's signing key, once.
- Fund that address, so it can pay a fee. Bengar does not fund it for you.
- Create an asset — name, symbol, decimals, supply model, and a cap and mint authority when the model is CAPPED_MINTABLE.
- Review. The screen shows the account, the sequence, the chain id and the fee that the signature will commit to.
- Confirm. Nothing you send with the confirmation can change what was reviewed: the intent is fixed under a fingerprint and the confirmation only names it.
AVAILABLE Provision the organization's chain signing key — /projects/[projectId]/assets
Where: Console → Assets
Requires: ADMIN
AVAILABLE Issue an asset from the Console — /projects/[projectId]/assets/new
Where: Console → Assets → Create an asset
First: An organization signing key, provisioned on the Assets page, and a funded chain account to pay the fee.
Requires: ADMIN
A FIXED asset is shown with no mint authority — not a disabled one. There is no message that could create more of it, so there is nothing to disable.
What the confirmation commits to
The reviewed transaction and the signed transaction are the same object. The Gateway builds one immutable intent, fingerprints it, and the confirmation names that fingerprint — so mutating the confirmation body changes nothing, and a fingerprint this deployment did not issue is refused.