← CIP-0112 · citation graph
Citations / CIP-0112
Canton Network Token Standard V2 - Improvements for Privacy, Performance and Traditional Accounting · status: Approved
Every place across CCPEDIA's corpus that references CIP-0112: 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.
Sibling CIPs · 5
CIPs that declare a requires: dependency on CIP-0112, or reference it in their content.
Forum posts · 10 · across 10 topics
Individual posts on forum.canton.network that mention CIP-0112. Showing 10 most recent of 10.
… ir own rules. See CIP-0056’s Ethereum comparison . Current documentation also covers V2, defined by CIP-0112 . Use the version supported by your token registry. Version references . 5. Are there sample projec …
… y that forwards to a fixed destination while preserving who it was addressed to. Related questions: CIP-0112 Accounts (“ owner + provider + id ”) seem to be the standard’s answer, but the account “ id ” is a …
… se on Canton. Composability is exactly what the chain is supposed to add and omnibus gives it back. CIP-0112 supports modelling custody chains on the ledger - If on-ledger sub-custody is the intended pattern …
The Token Standard doesn’t cover burn and mint operations, only transfers. Burn and mint are currently app-specific. The DA Registry offers a composition point to (Daml) apps with custom mint and burn
Hi Canton Network Team & Ecosystem Builders, We are exploring adding Trezor hardware support to the Canton Network. In ecosystems like EVM, Solana, or any other chain, hardware integration does not re
And if you need a token that implements CIP-56 then use the Amulet token from your LocalNet, which BTW also implements CIP-112 in case you need to test TSv2 workflows.
Hi Canton community, The first repos of OpenZeppelin’s open-source Daml development stack for Canton are now public, and we’re looking for your feedback. Test it, read the designs, and let us know how
CIP-0112 / Token Standard V2 addresses this use case. It allows an Allocation to be created without specifyi …
… tors until the settlement deadline. You can think of it as “escrow-style” use cases, except that in CIP-0112 the ownership doesn’t actually change. If you want an allocation that cannot be unilaterally cancel …
Hi, is this the right place to ask a CIP-112 v2 design/semantics question? If there is a better venue, happy to move it there. I’m looking for clarification on committed allocations. My current unders
Mailing-list messages · 33 · across 11 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.
https://github.com/canton-foundation/cips/pull/276
… a specific position in an asset . So we’ve been working on a draft CIP for an NFT profile built on CIP-0112 Token Standard V2 . The idea is pretty straightforward: define how a unique item can live on Canton …
… rk - **CIP-0056** — the mechanism this builds on. This CIP adds keys; it changes nothing in it. - **CIP-0112** — authorization within an account or custody structure. This is the nature of the principal invok …
… uld not run a ledger, simulate a wallet, inject faults, manage LocalNet, replay ledger state, cover CIP-0112/V2, define a new error taxonomy, or issue a conformance score, badge, or certification. It would re …
… nton Coin (CC) that is burned to purchase traffic, not based on individual transactions. Taking the CIP-0112 Settlement example transaction from the document where the transaction size = 400 bytes. There's no …
… entives optimize for 2-of-3 hosting of up to three parties (or equivalently nine nodes) per view. A CIP-0112 Settlement A realistic scenario is the decentralization of wallets and admin parties in a CIP-0112 …
… entives optimize for 2-of-3 hosting of up to three parties (or equivalently nine nodes) per view. A CIP-0112 Settlement A realistic scenario is the decentralization of wallets and admin parties in a CIP-0112 …
I have created a MainNet vote proposal to adopt the daml models from Splice 0.6.11, which enables token standard v2 support, per CIP 112. contract id: 00ab62c91e8b46b21f782d921c2abb72340859a5c97a380fc
I created a vote on TestNet to enable the Daml models from Splice 0.6.11, which implement CIP 112 (token standard v2) Contract ID: 0031669933e23a6b0b8b2b0cc2ba85af7d7a4baeed39922b4c9f91b36346c9ba48ca1
Splice 0.6.11 adds support for Token Standard v2, per CIP 112. I have created to adopt its Daml models on DevNet, threshold in 7 days, effectivity in 8. Contract ID: 00bee6a73bceb52aa0be74a69784c1ae06
Hi all, now that CIP-0112 has been accepted, several people have asked when the final API specs are ready and when their Amul …
… llo, Canton Improvement Proposal has been approved by a vote of the Super Validator Node Operators: CIP-0112: Canton Network Token Standard V2 - Improvements for Privacy, Performance and Traditional Accountin …
Cumberland DRW in favor Thanks Chris
… a lists.sync.global Skickat: Friday, 12 June 2026 06:03:47 Till: cip-vote@... Ämne: Re: [cip-votes] CIP-0112: Canton Network Token Standard V2 Five North in favor. On Fri, Jun 12, 2026 at 02:49 Luca Toscani v …
SBI votes in favor.
Five North in favor.
… via lists.sync.global Date: Tuesday, June 9, 2026 at 5:55 AM To: cip-vote@... Subject: [cip-votes] CIP-0112: Canton Network Token Standard V2 Hello Super Validator Node Owners, Please find ready for vote: CI …
Hello Super Validator Node Owners, Please find ready for vote: CIP-0112: Canton Network Token Standard V2 The CIP text as merged in GitHub at the Proposed state 0f638f0995 …
Tradeweb would be happy to endorse CIP-0112. Best, Justin
Thanks Bernhard. That would explain how to construct the choice args without hitting the Registry/Scan APIs –thank you! Although since you guys made improvements to the registry api, we no longer have
Hi Simon, thanks for your response. Indeed, I see expired amulet allocations are getting automatically archived by the AmuletAllocation_DsoExpire choice. Is there something similar for DvpLegAllocatio
Hi John, Simon gave a good answer how to deal with expiry, but I think your input may be on the other side: How do you get the Holding create arguments to populate choice context. If so, our approach
Hi John, thanks for the thoughtful feedback. As for your request wrt expiry handling: The only thing I still see missing, is for the executor to gain visibility on the underlying locked assets. We hav
… lances. Behavior of token-standard operations attempted against Locked CC, and any interaction with CIP-0112 (Token Standard V2), is implementation-defined and should be specified by the selected reference im …
Hello, this is John Antoniou, CTO of Temple Digital Group. I wanted to share our thoughts regarding Token Standard V2. This update to the token standard makes the whole flow much better. We are curren
GitHub items · 42
Issues, PRs, and dev-fund proposals across all indexed Canton repositories that mention CIP-0112.
… efault token (`token-disclosure-default`):** A complete fungible asset implementing CIP-0056 V1 and CIP-0112 V2 interfaces without additional argument-map keys. Issuers can deploy it as provided or use it as …
… 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 instrument …
Draft Standards Track CIP from Fairmint: an NFT profile on Token Standard V2. A conforming NFT is a CIP-0112 `Holding` with `amount = 1.0`, one instrument per item, whose template also implements a thin `Nft` …
… terface 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-exchange tooling; a …
### Milestone 3: Token Standard (CIP-56 V1 + CIP-0112 V2), External Signing, PQS Client, Conformance & Security Review • Delivery schedule: To be agreed …
… 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 application. It is …
Editorial pass over CIP-0112. No change to the specified interfaces. ### Changes - Clarify uniqueness requirement for transfer l …
## Summary In the Splice Portfolio **Settings → Pre-approved Assets** table, rows for token-standard (DA Registry) instruments never resolve. They cycle between `Checking...` and `Status unavailable /
… 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 settlement application. It is deliberately wallet-neutral and …
… + 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 Participant Qu …
Fix links on token standard page. * Fix one malformed link (CIP-0112 reference) **Transfer Instruction V2 API** * Old: /reference/splice-transfer-instruction-api/post-r …
This pull request fixes the malformed CIP-0112 link and updates three Token Standard V2 OpenAPI links to their current generated routes. Closes #1 …
… degen; the total request is unchanged). - **Deliverables:** - `canton-token` covering CIP-56 V1 and CIP-0112 V2: holdings, transfer instruction, allocations, choice-context, disclosed-contract / `createdEvent …
… work breakdown for Splice - create PR to adjust https://github.com/canton-foundation/cips/blob/main/cip-0112/cip-0112.md to specify the compatibility mode - this ensures that people can understand the `cip-11 …
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
… 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, provenance, …
… 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, provenance, …
hello again Wallet Team 🥳 i have taken a stab at implementing CIP-112 AKA token standard V2 all the way throughout you stack, using me lessons from last time and any standard that you are adopting in
### Type of submission - [x] New wallet application ### Summary Adds Send (https://cantonwallet.com) to the Wallet Directory with self-attested feature support: CC transfers/holding, CC pre-approvals,
… andard/proposals/2026-07-Brickken-regulated-token-standard.md) --- ## Summary This proposal extends CIP-0112 with standardized compliance controls for regulated assets. It delivers an open-source specificatio …
Milestone 3a: Token Standard (CIP-56 V1 + CIP-0112 V2), External Signing, PQS Client & Conformance • Issue: [#556](https://github.com/canton-foundatio …
… ing. - **`cip-0056.mdx`**: Added notes on CIP-0107 (24h submission window, approved March 2026) and CIP-0112 (Token Standard V2, approved June 2026). - **`cip-index.mdx` and 26 other files**: Replaced all `gl …
… older ticket for implementing the guidance from https://github.com/canton-foundation/cips/blob/main/cip-0112/cip-0112.md#423-traders-accept-allocation-requests-and-create-allocations ### Context Daml code imp …
Blog posts · 3
Third-party coverage and ecosystem blog posts. Each links to the original publisher; CCPEDIA only indexes, doesn't republish.
DA Registry App v0.14 is live! This release introduces support for Canton Token Standard V2 (CIP-112), enabling Registry-issued assets to participate in the latest token standard workflows on Canton. Token Standard V2 (CIP-112) Registry-issued assets can now participate in Token
OpenZeppelin has made early Daml components and reference architectures for Canton public, including CIP-112 token and settlement tooling. The materials invite developer testing, feedback and further implementation work.
Canton’s week brought movement across institutional markets, protocol upgrades, wallets, DeFi, Featured App economics and consumer-facing applications. The biggest updates covered onchain repo, new token standards, $CC lockups, embedded swaps, bridge activity and growing institutional interest.
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/0112/citationsReturns a JSON shape mirroring this page.- The legacy
/api/v1/cips/0112/mentionsstays for backward compat. It returns topic / thread counts; this new endpoint returns per-post / per-message granularity plus GitHub and YouTube coverage.