Skip to content

← 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.

155 total referencesSibling CIPs 4Forum posts 2Mailing messages 25GitHub items 22Blog posts 102YouTube videos 0JSONMCP: get_cip_citations

Sibling CIPs · 4

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

Forum posts · 2 · across 1 topic

Individual posts on forum.canton.network that mention CIP-0112. Showing 2 most recent of 2.

Mailing-list messages · 25 · across 3 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-0112: Token Standard V2[cip-discuss] · cip_id match · @Simon Meier · 1mo ago

    Hi all, now that CIP-0112 has been accepted, several people have asked when the final API specs are ready and when their Amul …

  • CIP-0112: Canton Network Token Standard V2[cip-announce] · cip_id match · @Improvements for Privacy, Performance and Traditional Accounting · 1mo ago

    … 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 …

  • CIP-0112: Canton Network Token Standard V2[cip-vote] · cip_id match · @Chris Zuehlke · 1mo ago

    Cumberland DRW in favor Thanks Chris

  • CIP-0112: Canton Network Token Standard V2[cip-vote] · cip_id match · @Veronica Augustsson · 1mo ago

    … ...> Skickat: Friday, 12 June 2026 06:03:47 Till: cip-vote@... <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 …

  • CIP-0112: Canton Network Token Standard V2[cip-vote] · cip_id match · @Aman Goyal · 1mo ago

    SBI votes in favor.

  • CIP-0112: Canton Network Token Standard V2[cip-vote] · cip_id match · @Yiannis Varelas · 1mo ago

    Five North in favor.

  • CIP-0112: Canton Network Token Standard V2[cip-vote] · cip_id match · @Luca Toscani · 1mo ago

    … 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 …

  • CIP-0112: Canton Network Token Standard V2[cip-vote] · cip_id match · @Amanda Martin · 1mo ago

    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 …

  • CIP-0112: Token Standard V2[cip-discuss] · cip_id match · @Justin Peterson · 1mo ago

    Tradeweb would be happy to endorse CIP-0112. Best, Justin

  • CIP-0112: Token Standard V2[cip-discuss] · cip_id match · @john@templedigitalgroup.com · 1mo ago

    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

  • CIP-0112: Token Standard V2[cip-discuss] · cip_id match · @john@templedigitalgroup.com · 1mo ago

    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

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

    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

  • CIP-0112: Token Standard V2[cip-discuss] · cip_id match · @Simon Meier · 1mo ago

    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

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

    … 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 …

  • CIP-0112: Token Standard V2[cip-discuss] · cip_id match · @john@templedigitalgroup.com · 2mo ago

    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

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

    … ding cross-version, to a degree where they are comfortable that the Token Standard V2 as defined in CIP-0112 is ready to go into the Splice code base. The token standard V2 related code is on branch https://g …

  • Hi Simon, hi Sergei, Thank you both for the valuable technical feedback. I really appreciate it. Simon — your point about CC / Amulet fully implementing the CIP-56 APIs is especially important. In the

  • Thanks Murat, for sharing this detailed and thoughtful write-up. It is a technically accurate and valuable guide for other wallet builders. Here are a few points that I've noticed while reading the qu

  • CIP-0112: Token Standard V2[cip-discuss] · cip_id match · @Simon Meier · 2mo ago

    Update: all four PRs have now been merged and will be deployed on TokenStdDevNet next week. toggle quoted message Show quoted text -- Dr. Simon Meier Principal Architect simon@... Creators of Canton N

  • CIP-0112: Token Standard V2[cip-discuss] · cip_id match · @Simon Meier · 2mo ago

    Note that the last four changes are still being merged into the main token standard branch. You can find the corresponding PRs using this query: https://github.com/canton-network/splice/pulls?q=is%3Ao

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

    … exible authorization models. Functional extensions to the standard These are proposed extensions to CIP-0112, which will get new top-level sections in the CIP-0112 text. The Token Standard V2 Transaction Hist …

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

    … own, with all but the top-most sections targeted at those that are knees-deep in coding against the CIP-0112 draft standard. As you can see there’s a lot going on, and I want to thank all those that engaged i …

  • CIP-0112: Token Standard V2[cip-discuss] · cip_id match · @Wayne Collier · 3mo ago

    CIP-0112 is now in the CIP repository in Draft state. https://github.com/canton-foundation/cips/blob/main/ci …

  • CIP-0112: Token Standard V2[cip-discuss] · cip_id match · @Simon Meier · 3mo ago

    AFAIS, the initial message does not mention the PR with the proposed CIP against the repository. For the sake of completeness, here it is: https://github.com/canton-foundation/cips/pull/187 toggle quo

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

    … in shaping an iteration that makes incremental but material improvements to the standard. CIP Text: CIP-0112: Token Standard V2 Abstract This proposal outlines a set of improvements to the CIP-0056 Canton Net …

GitHub items · 22

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

Blog posts · 102

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

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/citations — JSON shape mirroring this page.
  • The legacy /api/v1/cips/0112/mentions stays for backward compat — it returns topic / thread counts; this new endpoint returns per-post / per-message granularity plus GitHub and YouTube coverage.