Protocol family map

The Atomicals protocol family. Every Atomicals primitive starts from the same envelope written in a reveal transaction. The operation inside the envelope decides what is produced. The fungible branch produces direct FT issuance, fixed decentralised deployments, and their mint claims. The non-fungible branch produces plain NFTs, Containers with DMINT items, and the name primitives Realm, Subrealm, and Payname. The AVM is a separate beta layer that is not part of either branch today.

The Atomicals protocol family

Every Atomicals primitive starts from the same envelope written in a reveal transaction. The operation inside the envelope decides what is produced. The fungible branch produces direct FT issuance, fixed decentralised deployments, and their mint claims. The non-fungible branch produces plain NFTs, Containers with DMINT items, and the name primitives Realm, Subrealm, and Payname. The AVM is a separate beta layer that is not part of either branch today.

Primitives

Primitive	Creating operation	Result	Read
Atomicals NFT	nft	One non-fungible object with optional payload files	NFT overview
Direct FT	ft	Complete fungible supply in output zero	Direct issuance
Fixed DFT	dft	A deployment that others mint against	Fixed DFT
DFT claim	dmt	One mint of the deployment’s exact amount	Decentralised mint
Perpetual DFT	dft with perpetual parameters	Activation gated progressive minting	Perpetual DFT
Container	nft with a container request	A named collection identity	Containers
DMINT item	dmt item claim against a sealed manifest	A verified collection item	DMINT
Realm	nft with a realm request	A top-level name	Realms
Subrealm	nft with a subrealm request	A child name under a Realm	Subrealms
Payname	A Realm used as a payment destination	A resolvable name	Paynames

Transfer and maintenance operations

Operation	Applies to	What it does
normal allocation	FT and NFT	Default coloring when no operation payload is present
y	FT	Split behavior at the pinned revision
z	FT	Custom coloring, activation gated
x	NFT	Splat, separating multiple Atomicals held at one output
mod	Any	State update recorded in history
evt	Any	Event record
sl	Container, NFT	Seal, making further changes impossible
dat	Any	Permanent data storage

Exact payload shapes and activation conditions are version sensitive. See envelope and operations.

Universe product exposure

This column answers a different question from the one above. It is about what our services do, not what the protocol allows.

Capability	Universe status	Where
ARC-20 token discovery, details, holders, activity	Available	ARC-20 API
ARC-20 portfolio balances and UTXOs	Available	ARC-20 API
NFT, Realm, and Subrealm read model	Available	NFT and Realm API
Marketplace v1 for ARC-20, NFTs, Realms, Subrealms	Available, gated per action	Marketplace v1
Direct mint-ft issuance from a Universe product	Not exposed	Direct issuance
Container and DMINT read model	Not in the NFT and Realm projection	Containers
AVM execution	Testnet4 only. No mainnet writes	AVM status

The Universe NFT and Realm index deliberately projects plain NFTs, Realms, and Subrealms only. Fungible tokens, Containers, and DMINT items are excluded from that projection and served by the ARC-20 side. That exclusion is declared in the index’s own provenance manifest.