Skip to content
CCPEDIAby Unity Nodes

← CIP-0056 · citation graph

Citations / CIP-0056

Canton Network Token Standard · status: Final

Every place across CCPEDIA's corpus that references CIP-0056: sibling CIPs, forum threads, the cip-* / grants-* mailing lists, GitHub issues + PRs across all indexed Canton repos, third-party blog coverage, and YouTube transcripts. Each section samples the most recent N; counts above the sample are the totals.

231 total referencesSibling CIPs 13Forum posts 38Mailing messages 64GitHub items 92Blog posts 23YouTube videos 1JSONMCP: get_cip_citations

Sibling CIPs · 13

CIPs that declare a requires: dependency on CIP-0056, or reference it in their content.

Forum posts · 38 · across 32 topics

Individual posts on forum.canton.network that mention CIP-0056. Showing 20 most recent of 38.

Mailing-list messages · 64 · across 35 threads

Messages on cip-vote, cip-discuss, grants-discuss, and other validator-announce lists. Items with cip_id_match badge come from CCPEDIA-parsed mailing_messages.cip_id: only-here join.

  • CIP-0056 Revision: Request for Sponsorship and Endorsement[cip-discuss] · cip_id match · @Yiannis Varelas · 11d ago

    Happy to sponsor.

  • CIP-0056 Revision: Request for Sponsorship and Endorsement[cip-discuss] · cip_id match · @Amanda Martin · 11d ago

    Hello everyone, Please review the proposed revision to CIP-0056: Canton Network Token Standard in PR #255 . The revision makes the following updates: Replaces outd …

  • … size is a real measurement on any participant. I had been discarding it. Comparing two independent CIP-0056 registries executing the same standard transfer minimal reference registry, direct completion 11,73 …

  • CIP-TBD: authority metadata for non-human parties (five optional CIP-0056 keys)[cip-discuss] · cip_id match · @NodeAxis AI · 1mo ago

    … ds to know has to ask off ledger. The proposal. Five optional metadata keys, carried in the records CIP-0056 already provides. Two at party level (how a party is operated; who is accountable for it) and three …

  • … nicalizer, redaction validator, and six to ten synthetic fixtures for the observable handoff of one CIP-0056 V1 transfer-instruction failure through the synchronous CIP-0103 provider path. It would record onl …

  • Validator Approval Congratulations on having your validator approved! We're very excited to have you spin up your validator node and join us online. Please find the next steps below. Feel free to reac

  • … is is useful to anyone. Benchmarking OpenZeppelin's Canton token template Measured through the real CIP-0056 interface choice `TransferFactory_Transfer`: - ~15 transfers/second, p50 ~400 ms, p99 ~1.2 s - Stop …

  • Feedback - two Dev Fund proposals from NODEJUMPER[grants-discuss] · @two Dev Fund proposals from NODEJUMPER · 4mo ago

    Hi, We're a NODEJUMPER team, and we've submitted two Dev Fund proposals. We'd really value feedback from this list, and for the second one we're also looking for a champion. 1. ISO 20022 ↔ Canton Sett

  • Abstract[cip-discuss] · @Amanda Martin · 4mo ago

    Onboard Alchemy to Canton, Outcome-Linked SV Weight (Max 3) Number CIP XXXX Layer Governance / Ecosystem Title Onboard Alchemy to Canton, Outcome-Linked SV Weight (Max 3) Author(s) Jacob McCrum, Surag

  • Rewards Locking Module[cip-discuss] · @Luke Farrell · 4mo ago

    … atibility This CIP defines locking governance state that lives alongside, but is distinct from, the CIP-0056 Canton Network Token Standard. Token-standard operations on Amulet are expected to continue to work …

  • Abstract[cip-discuss] · @vignesh.iyer · 5mo ago

    The RedStone Oracle team would like to formally propose Canton Access and Privacy Standard (CAPS) a push oracle architecture redesigned from first principles for Canton’s privacy model. CIP-TBD: Canto

  • Hi all, Posting per Dr. Amanda Martin's suggestion that proposals seeking a Tech & Ops champion engage this list first. I'm Curtis Guider (independent builder, no prior Daml — production Cloudflare /

  • … ll/293 - Ships an open-source dispute and refund-authorization primitive for Canton — composes with CIP-0056 / CIP-0103, no CIP changes proposed - Ask: 3,000,000 CC over 5 months, 3 milestones - SIG label: fi …

  • Hi all, I'm Utku from the Jubilee team. We've just submitted a Draft proposal to the Canton Development Fund: an NFT-focused CIP-56 reference implementation paired with a privacy-native marketplace, f

  • Follow-up (Canton issuer validation request)[grants-discuss] · @Maranda Harris · 5mo ago

    … n Canton, given the network’s privacy-first and multi-party execution model. For teams working with CIP-0056 tokens, stablecoin issuance, or DvP / settlement workflows on Canton: Would enforcing compliance di …

  • What’s live (repo below)[grants-discuss] · cip_id match · @Maranda Harris · 6mo ago

    Thanks Wayne - appreciate you taking a look Happy to provide anything useful for the internal discussion. Also, glad to jump on a call if helpful. Thanks, Maranda

  • What’s live (repo below)[grants-discuss] · cip_id match · @Wayne Collier · 6mo ago

    I'm interested in learning more, and will discuss internally at DA to see how we think this might fit with known needs. .

  • What’s live (repo below)[grants-discuss] · cip_id match · @Maranda Harris · 6mo ago

    … m sharing TokenProof, an open-source compliance primitive for Canton designed to be reusable across CIP-0056 token implementations and DvP settlement workflows. This is not a concept — the PoC is implemented …

  • CIP-0112: Token Standard V2[cip-discuss] · @Bernhard Elsner · 6mo ago

    … s side-effect free non-consuming choices, similar to ERC-20 events. The rationale for this is this: CIP-0056 tx history parsing relies on events from the TransactionFactory and AllocationFactory interfaces wi …

  • CIP-0112: Token Standard V2[cip-discuss] · @Bernhard Elsner · 6mo ago

    Dear Community, The CIP-0056 token standard just celebrated its first birthday and has become an integral part of the network in …

  • Askardex[tokenomics-announce] · @Pedro Neves · 6mo ago

    … centralized over-the-counter marketplace built on the Canton Network and the Splice Token Standard (CIP-0056). It enables users to securely exchange tokenized assets in a trust-minimized environment using Dam …

  • Abstract[cip-discuss] · @Amanda Martin · 7mo ago

    … nt of Canton Coin burned, up to +1.5 max Regulated Settlement & Fiat On-Ramp (Pave Bank) Successful CIP-0056 asset mint/redeem; live fiat connectivity. 12 months +0.5 (Infra) +0.5 per $200M of CIP-0056 assets …

  • Abstract[cip-discuss] · @Amanda Martin · 7mo ago

    … ading. 6 months +0.5 (Infra) +1.5 (Burn) Regulated Settlement & Fiat On-Ramp (Pave Bank) Successful CIP-0056 asset mint/redeem; live fiat connectivity. 12 months +0.5 (Infra) +1.5 (Volume) Sovereign Asset Ori …

  • … actions directly must either update their parsing methods to the new transfer workflows, or move to CIP-0056 token standard transfers. All developers whose apps directly depend on splice-amulet models older t …

  • Abstract[cip-discuss] · @Yiannis Varelas · 7mo ago

    … ment and fiat on-ramp layer for Canton. Acceptance Criteria: Successful minting and redemption of a CIP-0056-compliant asset Live fiat connectivity enabling independent customer on-ramping Aggregate settlemen …

GitHub items · 92

Issues, PRs, and dev-fund proposals across all indexed Canton repositories that mention CIP-0056.

  • Add MahaWalletcanton-foundation/wallets#22 · pr · open · @afifsyaifullah1512 · 21h ago

    … tor hosted. - Supported with on-mainnet evidence: CC support, two-step CC transfers, pre-approvals, CIP-0056 token transfer, memo tags, integrated swaps (Cantex). - Self-attested, no proof link: CIP-0103 dApp …

  • Draft: Open token standardcanton-foundation/cips#277 · pr · open · @pixelplex · 11d ago

    … ure Standard (Draft) Draft CIP from PixelPlex that standardizes how an instrument admin publishes a CIP-0056 token so other nodes can install and integrate it without manual coordination. ## What it defines - …

  • CIP-56/ERC-20 Middleware #453 - Milestones 1-5: delivery claim (M5 delivery portion only)canton-foundation/canton-dev-fund#887 · issue · open · @Eunoia-cym · 12d ago

    ## Milestones 1 to 5: delivery claim **Proposal:** https://github.com/canton-foundation/canton-dev-fund/pull/453 (`proposals/2026-06-Eunoia-cip56-erc20-middleware.md`) **Applicant:** Eunoia CYM Limite

  • Propsal: Add regulated token standardcanton-foundation/canton-dev-fund#881 · pr · open · @thamerdridi · 13d ago

    … months **Maximum Amount:** N/A **Maximum Duration:** N/A --- ### Summary Canton's token standards (CIP-0056, CIP-0112) cover transfer and settlement, but they don't specify the compliance controls regulated …

  • Proposal: From EVM to Daml with behavioural paritycanton-foundation/canton-dev-fund#880 · pr · open · @mcalejo · 14d ago

    … behaves like the original. We will release an open-source tool (Apache-2.0) that writes idiomatic, CIP-0056-conformant Daml from a verified Solidity contract and produces parity evidence. That evidence is th …

  • Dev proposal Token Data Disclosure Standardcanton-foundation/canton-dev-fund#878 · pr · open · @pixelplex · 15d ago

    … oken` Daml interface with its registration-verification choice; an audited default token supporting CIP-0056 and CIP-0112; an interface-based token test kit; reference publication, deployment and peer-exchang …

  • feat(core-traffic-purchase): add the paymaster's off-ledger API and read its termscanton-network/wallet#2588 · pr · open · @jarekr-da · 19d ago

    Part 3a: Registry for TrafficPurchase introduced URL under which users can get disclosed contracts of Paymaset and ConversionRates see openapi files It is created similar to CIP-56 off-ledger URLs Aft

  • ### Milestone 3: Token Standard (CIP-56 V1 + CIP-0112 V2), External Signing, PQS Client, Conformance & Security Review • Delivery schedule: To be agreed with the selected auditor and the Tech & Ops se

  • Re-add CIP-56 lessons learned to token-standard deep-divecanton-network/cf-docs#1769 · pr · open · @8bitpal · 22d ago

    **Re-submits #1654 for review** (reverted in #1701 because it merged without the right level of review). Fixes #611. Adds two sections to `appdev/deep-dives/token-standard.mdx`: - **Unresolved registr

  • Proposal: Payvol, Open Payment Intent, Lifecycle and Reconciliation Infrastructure for Canton (RFP 13)canton-foundation/canton-dev-fund#859 · pr · open · @cayvox · 25d ago

    … proposal is scoped as shared ecosystem infrastructure built directly on the Canton Token Standard (CIP-0056, CIP-0112) and the dApp standard (CIP-0103), not as a wallet, a custodian, or a settlement applicat …

  • Proposal: PagFinance Fiat Connector for Cantoncanton-foundation/canton-dev-fund#851 · pr · closed · @straucoin · 29d ago

    … one, starts from zero. This proposal delivers an open-source, rail-agnostic fiat connector built on CIP-0056: Daml escrow templates, an off-ledger connector with a documented rail-adapter interface, and an in …

  • RedStone CAPS #497- M4 - Complex Data Processing & Bridge Verification - Developer Milestonecanton-foundation/canton-dev-fund#832 · issue · open · @pedrodneves · 29d ago

    ## Milestones and Deliverables The following schedule outlines the objective milestones, timelines, deliverables, acceptance criteria, and payment terms for the Canton Access and Privacy Standard (CAP

  • Canton Index #319 - Milestone 1: Filter Specification & Authoring Tools**canton-foundation/canton-dev-fund#817 · issue · open · @pedrodneves · 29d ago

    … .AmuletRules:AmuletRules_BuyMemberTraffic`), reward collection, CC transfers, ANS operations, and a CIP-0056 token transfer. - **Design review checkpoint:** filter format and example filters shared with DA en …

  • Revert "Adds CIP-56 lessons learned"canton-network/cf-docs#1701 · pr · closed · @8bitpal · 1mo ago

    ## Summary - Reverts #1654, which added a "Common pitfall: unresolved registry token packages" section and a "Detecting transfer preapproval from choice-context" section to `token-standard.mdx`.

  • Adds CIP-56 lessons learnedcanton-network/cf-docs#1654 · pr · closed · @8bitpal · 1mo ago

    ## Summary - Fixes #611 - Reviewed the referenced "Using CIP-56 Tokens in Canton Applications" post. Its central technical lesson (fetch `choiceContextData`/`disclosedContracts` from the registry befo

  • CIP-0112: editorial revisioncanton-foundation/cips#258 · pr · open · @0xNeshi · 1mo ago

    … ing in 4.1.5, 4.2.4, and 4.3.8.2. - Add the Copyright and Changelog sections. ### Open points - The CIP-0056 transaction parsing link in 4.1.5 is broken, see https://github.com/canton-foundation/cips/pull/258 …

  • ## Summary The validator's token-standard scan proxy (`/api/validator/v0/scan-proxy/registry/...`) does not forward the CIP-56 **v2** `allocation-instruction` and `transfer-instruction` routes, even t

  • CIP-0056: Fix references and limitation countcanton-foundation/cips#255 · pr · open · @0xNeshi · 1mo ago

    Updated references to the Implementation section and corrected limitation count in the Canton Coin specification.

  • Proposal: Payvol, Open Payment Intent, Lifecycle and Reconciliation Infrastructure for Cantoncanton-foundation/canton-dev-fund#760 · pr · open · @cayvox · 1mo ago

    … proposal is scoped as shared ecosystem infrastructure built directly on the Canton Token Standard (CIP-0056) and the dApp and wallet standards (CIP-0103, CIP-0112), not as a wallet, a custodian, or a settlem …

  • Proposal: Canton C++ SDKcanton-foundation/canton-dev-fund#751 · pr · open · @olliten · 1mo ago

    … The Canton C++ SDK** gives C++ applications typed access to commands, ledger state, update streams, CIP-0056 and CIP-0112 token workflows, interactive submission with a pluggable signer interface, and typed P …

  • PR #688 — Milestone 3: Token Standard (CIP-56 V1 + CIP-0112 V2), External Signing, PQS Client, Conformance & Security Reviewcanton-foundation/canton-dev-fund#721 · issue · open · @github-actions[bot] · 1mo ago

    Parent: #718 PR: https://github.com/canton-foundation/canton-dev-fund/pull/688 - **Estimated delivery:** Month 4.5 · **Hard deadline:** 6 months from grant approval. - **Estimated effort:** ~70 person

  • docs: Add proposal for Canton DeFi composability standardscanton-foundation/canton-dev-fund#664 · pr · closed · @arno-burnuk-talwex · 1mo ago

    This pull request adds a comprehensive development fund proposal for establishing core DeFi composability standards on the Canton platform. The proposal outlines the design, specification, and referen

  • Proposal: Canton NFT Standardcanton-foundation/canton-dev-fund#634 · pr · open · @bbznyc · 2mo ago

    … posal funds a DAML NFT standard for Canton: a new CIP defining an NFT profile on Token Standard V2 (CIP-0056 / CIP-0112). The profile adds stable per-item identity, collection uniqueness, per-item metadata, p …

  • Proposal: Canton NFT Standardcanton-foundation/canton-dev-fund#633 · pr · closed · @bbznyc · 2mo ago

    … posal funds a DAML NFT standard for Canton: a new CIP defining an NFT profile on Token Standard V2 (CIP-0056 / CIP-0112). The profile adds stable per-item identity, collection uniqueness, per-item metadata, p …

  • Proposal: Compliance Middleware SDK for EVM Developers on Zenithcanton-foundation/canton-dev-fund#621 · pr · open · @Noosphere-314 · 2mo ago

    ## Development Fund Proposal Submission **Proposal file:** [rfps/financial-markets-standards-verification/2026-08-Woof-compliance-middleware-sdk.md](https://github.com/woof-software/canton-dev-fund/bl

Blog posts · 23

Third-party coverage and ecosystem blog posts. Each links to the original publisher; CCPEDIA only indexes, doesn't republish.

YouTube videos · 1

Recorded talks and tutorials whose title, description, or transcript references CIP-0056. Snippets come from the transcript.

  • Hey everybody, Satenda side de team at Canon Foundation and in this part of the CF developer series video, we will be demoing how to use the Canon Foundation MCP and the newly released Canon Foundatio

For AI agents

Same citation graph through programmatic surfaces:

  • get_cip_citations: MCP tool. Input: {cip_id}. Output: counts plus sample items per source. Use when an agent needs "everything that references CIP-X across CCPEDIA's corpus" in one round-trip.
  • GET /api/v1/cips/0056/citations Returns a JSON shape mirroring this page.
  • The legacy /api/v1/cips/0056/mentions stays for backward compat. It returns topic / thread counts; this new endpoint returns per-post / per-message granularity plus GitHub and YouTube coverage.