Two Draft Token Standards Reach Canton's CIP Repository, Including an NFT Profile for Equity Certificates
PixelPlex proposes a way to publish and discover Canton tokens without manual coordination, and Fairmint proposes an NFT profile on Token Standard V2. Neither has been approved.
Two draft Canton Improvement Proposals (CIPs) that build on the network's token standards were opened in the Canton Foundation's CIP repository this week. Fairmint opened a draft NFT profile on 6 October 2026, and PixelPlex opened a draft "Open Token Standard" on 9 October. Both are open pull requests, not approved CIPs.
They sit on top of two approved standards: CIP-0056, the Canton Network Token Standard, approved on 31 March 2025 and now final, and CIP-0112, Token Standard V2, approved on 12 June 2026.
Fairmint: NFTs as single-unit holdings
Fairmint's draft is a Standards Track CIP by Boris Nelkin and Nick Mancuso. It defines how a non-fungible item fits into Token Standard V2 rather than creating a new token type:
- One item, one instrument. A conforming NFT is a CIP-0112 holding with an amount of 1.0 and one instrument per item, whose template also implements a thin NFT interface.
- Soulbound mode. The profile defines item identity, a mode for items that cannot be transferred, and where an item's content lives.
- No new transfer protocol. Transferable items use the existing CIP-0112 transfer and allocation flows. Marketplace behaviour is out of scope.
According to the pull request, Fairmint's SEC-registered transfer agent intends to issue equity certificates under the profile as its first production use.
PixelPlex: publishing a token so others can find it
PixelPlex's draft standardises how an instrument admin publishes a CIP-0056 token so that other nodes can install and integrate it without manual coordination. It defines:
- An OpenToken interface, one on-ledger contract per token, which a client can ping to confirm the admin stands behind the token's publication address.
- Public publication routes for a token card, package lists, package downloads, the version and migration announcements.
- A registration check a client runs before treating a token as verified.
- Peer exchange, a mutual link between two admins' publications verified on-ledger by both sides, which the draft says forms a graph with no central directory.
- A default fungible token that implements both the CIP-0056 V1 and CIP-0112 V2 interfaces, which issuers can deploy as it is or adapt.
What happens next
Both drafts still need discussion, a CIP number where one has not been assigned, and approval through the Foundation's process before they become standards. Fairmint's pull request says its discussion runs on the cip-discuss mailing list.
