Ravencoin assets, handled like first-class objects.
Mint a name. Sub-divide it. Pin metadata. Move the asset around the network the same way you move RVN itself.
Named assets
Reserve a globally unique asset name and decide supply, divisibility, and reissuability.
Sub-assets
Nest scoped tokens under an asset you control — useful for series and collections.
Unique assets
Issue one-of-one tokens for tickets, deeds, or proofs of ownership.
Burns & reissues
Adjust supply when the rules allow it. Permanent burns are honoured by the chain.
Issue an asset.
- 01
Pick a name
Asset names are global. The wallet checks availability against the chain before reservation. - 02
Set parameters
Choose total supply, divisibility (0–8 decimals), and whether the asset can be reissued later. - 03
Pin metadata
Attach an IPFS hash for descriptive metadata — images, terms, or a JSON manifest. - 04
Broadcast
Sign and broadcast the issuance transaction. The asset becomes spendable as soon as it confirms.
What you can actually do with Ravencoin assets from the wallet.
The wallet exposes the full Ravencoin asset surface: issuance, transfer, reissue, burn, sub-assets, unique items, and the restricted/qualifier pattern. Each is a single signed transaction; each is enforced by network consensus rather than by contract code. This section walks through what each operation looks like in practice, what it costs, and where the constraints actually bite.
A named asset is the standard case. You pick a globally unique name, set supply and divisibility, optionally pin metadata via IPFS, and broadcast a single issuance transaction.
The wallet checks the name against the chain before letting you broadcast — if "MYBRAND" already exists, the issuance transaction would be rejected, and the wallet warns you first. Once the transaction confirms, the asset appears in your balance list and can be transferred to any Ravencoin address that supports assets (Electrum RVN, Ravencoin Core, most hardware-wallet-paired wallets).
Sub-assets and unique items
Once you own a named asset, you can mint sub-assets under it for the cost of a sub-asset issuance fee — significantly cheaper than a fresh top-level asset. The naming convention is PARENT/CHILD, and only the holder of the parent asset can mint children. Unique assets use thePARENT#UNIQUE naming convention and are guaranteed to exist exactly once — useful for tickets, collectibles, deeds, and any other one-of-one item.
- Named asset — global namespace, fixed or reissuable supply.
- Sub-asset — scoped namespace under a parent you own.
- Unique asset — exactly one will ever exist with that name.
- Restricted asset ($X) — transfer is gated by a qualifier tag (#Y).
- All four are issued and transferred from the same Assets tab.
Asset transfers look exactly like RVN transfers from the wallet's perspective: pick the asset, pick the destination, pick the amount, sign, broadcast. The transaction is a normal Ravencoin transaction with an additional output encoding the asset payload, and it is signed by the same keys that hold your RVN. If the destination wallet does not support assets, the asset will simply sit at the address unredeemable from that wallet — recovering it requires importing the seed into an asset-aware client.
If the asset was issued as reissuable, the wallet exposes a Reissue action that lets you increase supply, change divisibility upward, swap the IPFS metadata, or flip the reissuable flag off (this last action is one-way — once reissuance is disabled it cannot be re-enabled). Burns are permanent and honoured by the chain: a burn transaction destroys the specified amount and reduces circulating supply for ever.
Restricted and qualifier assets
For regulated-asset use cases, the wallet supports the restricted/qualifier pattern: a restricted asset (prefixed$) whose transfers are policy-gated, and a qualifier asset (prefixed #) whose holders are permitted to receive the restricted asset. The protocol enforces the rule at the consensus layer — addresses without the qualifier tag literally cannot receive the restricted asset, regardless of what the sending wallet tries to do. Common uses include accredited-investor lists, jurisdiction-gated tokens, and KYC'd holder sets.
Every asset operation — issuance, transfer, reissue, burn — is a standard Ravencoin transaction and can be signed on a Ledger or Trezor paired with the wallet. The device shows the relevant outputs and amounts; you confirm on the device screen before anything is broadcast. For asset issuers managing meaningful supply, hardware signing is the right default. Start by installing Electrum RVN and pairing the device on first run.
Frequently asked
Continue with Electrum RVN
- what are Ravencoin assets — background on the asset layer
- Ravencoin multisig wallet — shared-control wallets for issuers
- RVN wallet download — start issuing and moving assets locally
Run your own Ravencoin wallet.
Open-source, lightweight, and built for the desktop user who wants real control over keys and assets. Download the wallet directly from our download page — signed installers for every operating system.