← All intelligence

web · August 28, 2025

Canton Token Standard Support — DFNS

dfns.co · Read at source ↗

DFNS supports CIP-56 for Canton Coin, unlocking tokenized assets, stablecoins, and treasury workflows for institutions on the Canton network.

DFNS has added support for Canton’s official token standard, CIP-56, to its Wallet-as-a-Service platform, enabling full data indexing and transfers for Canton Coin. The release extends its Tier-1 integration and completes the company’s Canton wallet roadmap.

Canton integration reaches completion

DFNS initially introduced Canton Coin transfers through a Tier 2 integration. Its subsequent Tier 1 upgrade added real-time indexing, webhook notifications and automation.

The company also introduced Bring Your Own Validator (BYOV), which lets applications and institutions connect their own Canton node rather than use DFNS’s shared node. With the latest release, BYOV supports Canton Coin under CIP-56, including full support for transfer offers.

Other CIP-56 tokens can be supported on request, provided their issuers supply a dedicated RPC node.

Common rules for Canton tokens

CIP-56, short for Canton Improvement Proposal 56, serves as Canton’s counterpart to Ethereum’s ERC-20 standard. It defines common rules for token creation, transfers and management using DAML, Canton’s privacy-focused smart contract language.

Standardized balances, transfers and approvals allow wallets, custodians, settlement systems and applications to work with tokens without separate custom integrations. The standard is intended to provide an interoperable, scalable foundation built for compliance for Canton Coin and other CIP-56 tokens supported on request.

Its central transfer function governs secure token movement between parties, including bilateral transfers and atomic Delivery-versus-Payment (DvP) workflows.

Wallet features and institutional use

DFNS says it is the first wallet infrastructure provider to offer full indexing and transfers for CIP-56 Canton Coin, and the first institutional wallet infrastructure provider to support it fully.

The platform’s capabilities include:

  • Live balances: Canton Coin balances under CIP-56, with other compliant tokens available on request.
  • Real-time transaction records: Indexing of all transfers for auditing and reporting.
  • Ownership visibility: Access to holdings and reconciliation information without interpreting raw chain data.
  • Free-of-Payment (FOP) transfers: Transfers that participants can approve or reject onchain.
  • Approvals and allowances: Delegated transfers for treasury operations and structured finance.

Fintechs and institutions can use these features to custody, transfer and report on Canton Coin across Canton’s privacy-preserving settlement network. DFNS says the service draws on the same infrastructure reliability supporting millions of wallets across leading blockchains.

Operational control and planned API

Institutions can use BYOV to operate their own Canton nodes for compliance and operational control. Combined with CIP-56 support, DFNS says this gives institutions flexibility to issue, custody and transfer assets using their own validators, fees and namespaces.

The integration also allows institutions to test tokenized-finance workflows with Canton Coin while preparing for additional CIP-56 tokens supported on request. DFNS positions these capabilities as a foundation for banks, custodians and stablecoin issuers working on a network designed for privacy, compliance and interoperability.

A low-level API for building any type of transaction, including transactions enabling DvP, is listed as coming soon rather than part of the current release.

TopicEcosystem
ProvenanceLive web scan, matched against the project registry
Scope
Canton Network

Sources & attribution

Published
Aug 28, 2025 · 12:00 AM UTC
Source
dfns.co
Publisher
dfns.co

Full attribution under the Digital Millennium Copyright Act (DMCA), 17 U.S.C. § 512: this article is an original report by Canton Intelligence that summarizes the reporting of the publishers named above, links to their original work, and reproduces no protected expression beyond brief factual reference and in-line attribution (“according to dfns.co”). All rights in the underlying reporting remain with the publishers listed; nothing here implies endorsement by or affiliation with them. Rights holders may request correction, update or removal through the contact address published at infiniti.w3ai.io.