Skip to content

← CIP-0010 · citation graph

CITATIONS / CIP-0010

LCV have met all their requirements to be a T1 Super Validator · status: Final

Every place across CCPEDIA's corpus that references CIP-0010 — 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.

56 total referencesSibling CIPs 4Forum posts 3Mailing messages 8GitHub items 39Blog posts 1YouTube videos 1JSONMCP: get_cip_citations

Sibling CIPs · 4

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

Forum posts · 3 · across 1 topic

Individual posts on forum.canton.network that mention CIP-0010. Showing 3 most recent of 3.

  • CIP-104 is planned to go live by the end of July. The change has a few implications for wallets, so I’d recommend reading the CIP directly for the full details. At a high level, CIP-104 may change the

  • CIP-107 went into production yesterday. If you use the token standard APIs and treat the prepared transaction/choice context as opaque, this should mostly be transparent for you. You may need to adjus

  • App rewards · #5@Jatin_Pandya_cf · 2mo ago

    Hey @karlo Jatin This side, DevRel Manager, Canton Foundation. Appreciate you understanding based on the numbers and forumla as this is exactly the kind of analysis that helps surface real gaps in how

Mailing-list messages · 8

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.

  • Hi all it's a pleasure to inform you that t raffic-Based App Rewards (CIP-104) is live on DevNet as you can see from the screenshot of the DSO info on DevNet below. If you are an app developer and wou

  • MainNet: Enable traffic-based app rewards in dry-run mode[supervalidator-announce] · @Itai Segall · 21d ago

    I created a vote proposal on MainNet to enable traffic-based app rewards in dry-run mode per CIP-104. Threshold deadline: 07/07 09:00 US eastern Effectivity: 07/07 10:00 US eastern Contract ID: 00c046

  • TestNet: vote to enable TBAR dry-run[supervalidator-announce] · @Itai Segall · 28d ago

    Per CIP-104, I have created a vote on TestNet to enable traffic-based app rewards (TBAR) in dry-run mode. Threshold deadline in 7 days, effectivity an hour later. Contract ID: 00296e8d76bb79aee0cd12b2

  • TestNet: vote to adopt Daml models from Splice 0.6.7[supervalidator-announce] · @Itai Segall · 1mo ago

    I created a vote proposal on TestNet to adopt the Daml models from Splice 0.6.7, which are required for TBAR (traffic-based app rewards) per CIP-104 Contract ID: 00b59ff9921d1ab888176a5af4f4749b8ff24a

  • CIP-0105: Super Validator (SV) Staking[cip-discuss] · @Luke Farrell · 2mo ago

    Building on Andrew's definitions above, attached (and below) is a document with proposed detailed Supplier Substitution workflows during manual Phase1, for discussion on May 6th (tomorrow) Tokenomics

  • CIP-0116: Featured App Staking[cip-discuss] · @Anthony Merriman · 2mo ago

    Hi Eric (and everyone!) We think the new staking quantities for phase 2 and phase 3 with the 120 day roll-out plan are both reasonable and relatively easy to implement. We also believe the introductio

  • Stay Updated on Canton Development Fund Grants[globalSyncForum] · @Amanda Martin · 4mo ago

    Hello everyone, As we continue to roll out and operationalize the Canton Development Fund, we’ve set up two mailing lists to help the community stay informed and engaged in the grants process. grants-

  • According to cip-0010 LCV is an approved Tier 1 SuperValidator with a weight of 10 0000. Since MPCH operates a dedicated …

GitHub items · 39

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

  • OpenZeppelin Canton Ecosystem Stack #262 - Milestone 1: Token Foundation and dApp Frameworkcanton-foundation/canton-dev-fund#564 · issue · open · @pedrodneves · 5d ago

    ## Milestone 1: Token Foundation and dApp Framework | Field | Value | | :---- | :---- | | **Estimated Delivery** | Quarter 1: May to July 2026 | | **Focus** | Foundational library components and Refer

  • docs: restructure dApp SDK documentationcanton-network/wallet#2154 · pr · closed · @joel-da · 5d ago

    ### Description: This PR rewrites and reorganises the dApp SDK documentation under [dapp-sdk](vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electr

  • SV UI: CIP-104 Support UpdateFeatureAppRight Votecanton-network/splice#6441 · pr · open · @JYC11 · 5d ago

    fixes: https://github.com/canton-network/splice/issues/6236

  • Decentralization manager phase 2 proposalcanton-foundation/canton-dev-fund#530 · pr · open · @gabitu7 · 7d ago

    ## Development Fund Proposal Submission **Proposal file:** [proposals/decentralization-manager-phase-2.md](https://github.com/gabitu7/canton-dev-fund/blob/decentralization-manager-phase-2-proposal/pro

  • [Acceptance] WG (M3)canton-network/wallet#2132 · issue · open · @mjuchli-da · 8d ago

    - [ ] **Browser-Extension-Compatible Gateway Engine:** Delivery of the core Wallet Gateway components packaged as a localized, browser-compatible library (e.g., NPM package). This involves migrating e

  • [Acceptance] dApp (M3)canton-network/wallet#2130 · issue · open · @mjuchli-da · 8d ago

    - [ ] **External Code Audit:** Secure external, third-party validation by commissioning a full-scope security audit. This is a critical step for building market credibility, fostering trust, and estab

  • Tracking: featured app weights for TBARcanton-network/splice#6176 · issue · open · @meiersi-da · 21d ago

    ### Motivation Implement the amendment for CIP-104: - CIP change: https://github.com/canton-foundation/cips/pull/238 - context: https://lists.sync.global/g/cip-discuss/message/796 ### Work Breakdown -

  • Use more descriptive names for reward configcanton-network/splice#5986 · issue · open · @meiersi-da · 1mo ago

    ### Status Quo It was unclear to @isegall-da what values to use when creating the vote for DevNet. ### Target State Textual description allows the reader to understand: - the valid values - the effect

  • Proposal: Wallet Gateway Signer (Institutional Driver)canton-foundation/canton-dev-fund#409 · pr · open · @Binxx35 · 1mo ago

    ## Development Fund Proposal Submission **Proposal file:** [/proposals/canton-gateway-driver](https://github.com/Binxx35/canton-gateway-driver/blob/main/driver-proposal) --- ## Summary While the dApp

  • dapp-sdk top-level @walletconnect/sign-client import forces all consumers to bundle WalletConnectcanton-network/wallet#1883 · issue · open · @rleonid · 1mo ago

    ## Issue @canton-network/dapp-sdk@1.1.0 declares @walletconnect/sign-client and @walletconnect/types as optional peer dependencies, signalling that consumers who don't use WalletConnectAdapter shouldn

  • Wallet Gateway Reference Implementation #109 Milestone 3: Browser Extension Deployment Capabilitycanton-foundation/canton-dev-fund#362 · issue · open · @pedrodneves · 2mo ago

    ### **Milestone 3: Browser Extension Deployment Capability** Repurpose the Gateway’s core routing logic and CIP-103 API server to run entirely locally within a browser context, serving as the foundati

  • DappSyncProvider drops all CIP-103 push events (txChanged, accountsChanged, statusChanged, connected)canton-network/wallet#1815 · issue · closed · @alleneubank · 2mo ago

    ## Summary `DappSyncProvider` + `WindowTransport` (the postMessage path used by any CIP-103 browser-extension wallet via `ExtensionAdapter`) silently drops every push event. The dApp-side `provider.on

  • feat: deliver CIP-103 push events through DappSyncProvidercanton-network/wallet#1814 · pr · closed · @alleneubank · 2mo ago

    ## Summary CIP-103 requires wallets to deliver `txChanged` / `accountsChanged` / `statusChanged` / `connected` through `provider.on(event, listener)`. On the sync (postMessage) path used by `Extension

  • DRAFT: CIP-104 Dry-run support feature branchcanton-network/splice#5590 · pr · closed · @dfordivam · 2mo ago

    Opening for CI run ### Pull Request Checklist #### Cluster Testing - [ ] If a cluster test is required, comment `/cluster_test` on this PR to request it, and ping someone with access to the DA-interna

  • GrowStreams — Privacy-Native Payment Streaming for Cantoncanton-foundation/canton-dev-fund#344 · pr · closed · @BlockXAI · 2mo ago

    ## Development Fund Proposal Submission **Proposal file:** https://github.com/BlockXAI/canton-dev-fund/blob/canton-streams/proposals/canton_streams.md --- ## Summary GrowStreams is an open-source paym

  • Add GrowStreams proposal for Canton networkcanton-foundation/canton-dev-fund#342 · pr · closed · @BlockXAI · 2mo ago

    ## Development Fund Proposal Submission **Proposal file:** https://github.com/BlockXAI/canton-dev-fund/blob/canton-streams/proposals/canton_streams.md --- ## Summary GrowStreams is an open-source paym

  • [Acceptance] dApp (M1)canton-network/wallet#1760 · issue · closed · @mjuchli-da · 2mo ago

    Acceptance Criteria - [x] dApps can implement a single component that will give them interop with all CIP-103 compliant wallets. - [x] CI/CD reporting confirms >80% Unit Test Coverage. - [x] Public re

  • Wallet Provider Compliance Test Suitecanton-network/wallet#1759 · issue · open · @mjuchli-da · 2mo ago

    Implement a transparent, objective verification mechanism (Test and Integration Suite) to validate Wallet Provider adherence to the dApp standard (CIP-103). This initiative is critical for maintaining

  • Update cip-0077.mdcanton-foundation/cips#207 · pr · open · @ClementineDrouot · 2mo ago

    ### PR: CIP-0077 Adoption Bonus timing / milestone recognition This Pull Request (PR) proposes an adjustment to the Adoption Bonus timing/milestone recognition criteria under CIP-0077 to better reflec

  • Evidence Documentation for Milestonecanton-network/splice#5455 · issue · open · @guillaumedejenlis-da · 2mo ago

    Milestone 4: Protocol-Conformant Free Confirmation Responses | Months after grant approval -- | -- Estimated Delivery | Month 6 Focus | Canton protocol changes Deliverables: Canton: protocol changes s

  • SV Governance dApp #223 Milestone 2: External Signing Proof of Conceptcanton-foundation/canton-dev-fund#287 · issue · open · @pedrodneves · 2mo ago

    ### Milestone 2: External Signing Proof of Concept - **Estimated Delivery:** Month 3-4 - **Focus:** Prove wallet-based external signing for governance votes - **Deliverables / Value Metrics:** - Initi

  • Canton Network dApp SDK and Tooling #69 Milestone 3: Security & DXcanton-foundation/canton-dev-fund#277 · issue · open · @pedrodneves · 2mo ago

    ### **Milestone 3: Security & DX** * **External Code Audit:** Secure external, third-party validation by commissioning a full-scope security audit. This is a critical step for building market credibil

  • Canton Network dApp SDK and Tooling #69 Milestone 2: Compliance & Abstractioncanton-foundation/canton-dev-fund#276 · issue · open · @pedrodneves · 2mo ago

    ### **Milestone 2: Compliance & Abstraction** * **Achieve interoperability with Wallet SDK:** Architect a provider layer that abstracts ledger connectivity, ensuring compatibility with the widely-adop

  • Canton Network dApp SDK and Tooling #69 Milestone 1: SDK v1 & Wallet Discoverycanton-foundation/canton-dev-fund#275 · issue · closed · @pedrodneves · 2mo ago

    ### **Milestone 1: SDK v1 & Wallet Discovery** * **Standardized Wallet Discovery Library:** Deliver an Open Source, turn-key, reusable library that enables dApps to achieve instant interoperability wi

  • Traffic-Based App Rewards 107 Milestone 4: Protocol-Conformant Free Confirmation Responsescanton-foundation/canton-dev-fund#242 · issue · open · @pedrodneves · 2mo ago

    ## Milestone 4: Protocol-Conformant Free Confirmation Responses | | Months after grant approval | | :---- | :---- | | **Estimated Delivery** | Month 6 | | **Focus** | Canton protocol changes | Deliver

Blog posts · 1

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-0010. Snippets come from the transcript.

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