NFTs on Pact

The PCO publishes an open NFT standard and a complete, audited NFT framework for the Kadena chainweb — built so that creators keep their royalties, buyers cannot be cheated, and any business can open a marketplace. This is the documentation for all of it.

Two building blocks

The interface standard v1

Three frozen on-chain interfaces (nft-asset-v1, nft-market-v1, nft-xchain-v1) plus a normative specification. Marketplaces that implement them are compatible: one wallet, one indexer, one aggregator works across all of them.

  • For teams building standalone marketplace modules
  • Runnable conformance suite with adversarial tests
  • Audited MIT reference implementation to copy

The nft framework

A shared-ledger NFT ecosystem: one hardened ledger anchors every token, one settlement engine pays every sale, and composable policies carry each token's rules — royalties, guards, editions, collections — with it wherever it goes.

  • Marketplaces need no contract of their own
  • Auctions built in (ascending and declining-price)
  • Tokens move between chains, rules travel along

One owner: the community

Both are published on-chain by the PCO in a single namespace per network, and both are open source in the contract catalog. Deployed interfaces cannot be upgraded — what is published is the standard, permanently.

The promises the code makes

  • Nothing fails open.Every guard and account is required and validated — a malformed input aborts, it never degrades to "anyone can transfer".
  • One settlement, with the math checked. Every sale settles in a single step that asserts money in = money outto the currency's full precision. No stacked hook can skim.
  • Economics live on-chain, never in the buy transaction. Price, royalty, and fees bind when the seller signs the listing. Nothing a buyer (or a malicious frontend) sends can change them.
  • Royalties are real.A creator's cut is enforced at settlement — on every marketplace, through every auction, and across chain moves. There is no royalty-free exit unless the creator allowed one.
  • Identity cannot be forged.A token's id is derived from its creator's guard: nobody can mint a token that claims to be someone else's, and nothing can be minted twice.

Pick your path

Deployment status

The standard and framework are complete, audited, and open source today. They were published to the community testnet across all 20 chains in July 2026; a network-wide reset later removed everything on that testnet, and re-publication is pending the network's return. Because the namespace and module hashes are deterministic, the catalog records the expected values — when re-published, anyone can verify every module with describe-module against those tables.

Go deeper