What Are DigiAssets? DigiByte’s Native Token and NFT Layer

DigiAssets are DigiByte's native layer for issuing custom tokens and NFTs directly on the DigiByte blockchain, without needing a separate chain or a smart-contract virtual machine. The protocol builds on the same colored-coin concept used by early Bitcoin token systems: a small amount of data written into a transaction's OP_RETURN output encodes the creation, transfer, and metadata of an asset, while the underlying DigiByte UTXO carries the asset the way it would carry ordinary DGB. Because DigiAssets ride on DigiByte's base chain, every transfer inherits the same roughly 15-second block time and the same proof-of-work security as a normal DGB transaction.

Rich metadata, images, descriptions, and other media, does not need to live on-chain to stay attached to an asset. Instead, DigiAssets reference that content through IPFS, the decentralized storage network: the on-chain transaction encodes a Content Identifier that points to the metadata, keeping the blockchain itself lean while the descriptive and visual content stays verifiably linked to the asset. Assets can be locked, a fixed, non-reissuable supply with the asset's ID derived deterministically from its creation transaction, or left open for further issuance, depending on what the creator needs.

In practice, DigiAssets have been used for collectibles, tokenized real estate, supply-chain tracking, and academic credentials, among other applications, anywhere you want a verifiable, transferable digital record secured by a real blockchain. You can browse existing DigiAssets, including their metadata and current holders, for any DigiByte address in the DigiScope DigiAsset explorer.

Frequently asked questions

What is a DigiAsset?
A custom token or NFT issued directly on the DigiByte blockchain, using OP_RETURN data and the colored-coin concept to encode creation, transfers, and metadata.
Do DigiAssets need a separate blockchain?
No. They are issued and transferred on DigiByte's existing UTXO chain, inheriting its roughly 15-second block time and proof-of-work security.
Where does DigiAsset media like images and descriptions live?
Rich metadata is stored on IPFS and referenced on-chain by its Content Identifier, keeping the blockchain itself lean.
Where can I view DigiAssets on an address?
The DigiScope DigiAsset explorer lets you browse the assets, metadata, and holders behind any DigiByte address.
How a DigiAsset lives on DigiByte An issuance transaction has three outputs: asset dust to the holder, an OP_RETURN carrying the metadata hash, and change. The hash resolves to a metadata JSON on IPFS, which links to the media. DigiByte transaction issuance · 1 input · 3 outputs vout 0 0.0001 DGB → holder address (carries the asset) vout 1 · OP_RETURN 44 41 01 · sha1 · sha256 · amount · flags vout 2 change → issuer IPFS metadata bafkrei… (CIDv1) assetName, description, issuer, urls[] Media image / file sha256 → CID urls[0] DigiAsset Core pins the JSON, never the media
DigiAssets at a glance

Explore DigiAssets

Learn DigiAssets

Build with DigiAssets

  • Read DigiAssets on any address — Query holdings and asset records from DigiAsset Core, derive the metadata CID from the on-chain SHA-256, fetch bytes from your own Kubo, and serve media without turning your explorer into an XSS or SSRF surface — walked through DigiScope’s asset browser code.
  • Issue and transfer a DigiAsset — Pin metadata as a raw leaf, build the 60-byte issuance payload, derive the asset ID from your first input, order the outputs, guard the broadcast, and transfer with the remainder rule — from DigiScope’s builder and the open-source ATB Wallet.