← CIP-0003 · citation graph
CITATIONS / CIP-0003
Consensus layer, as it focuses on validator participation, rewards, and network stability, with some overlap in Peer Services due to the operational aspects of nodes · status: Final
Every place across CCPEDIA's corpus that references CIP-0003: 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 · 2
CIPs that declare a requires: dependency on CIP-0003, or reference it in their content.
Mailing-list messages · 7 · 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.
… llowing a party to create a MintingDelegation contract will not be impacted by this CIP. Motivation CIP-0003 was initially raised to provide incentives to operate necessary infrastructure to interact with the …
… llowing a party to create a MintingDelegation contract will not be impacted by this CIP. Motivation CIP-0003 was initially raised to provide incentives to operate necessary infrastructure to interact with the …
… Validators were always designed to earn their rewards from Activity Rewards. Liveness was added in CIP-0003 as a solution to a bootstrapping problem. In order to have enough CC to transact in the Network and …
Hi All, Per discussion in last week’s Foundation Tokenomics Committee working group, please see below a draft CIP from Cumberland to remove liveness rewards from the validator rewards pool (also attac
Hi All, Please see below a draft CIP that Cumberland has been working on to adjust the Validator Reward caps. We welcome any feedback. Canton Improvement Proposal: Adjust Validator Reward Caps Abstrac
Hi Chris and Chris, Could you elaborate and what the rationale for making the distinction below would be? We were debating if we should note those tx are with featured apps or not. On a different note
All - We have been working with Proof Group to formalize the CIP on this topic. We are ready to present it to the group for discussion. Please see the below, we would like to discuss it during tomorro
GitHub items · 1
Issues, PRs, and dev-fund proposals across all indexed Canton repositories that mention CIP-0003.
[ This issue was auto-migrated from DA's internal repo (DACH-NY/canton-network-node#9350). Original author: @meiersi-da ] The following params are constant over all changes in the issuance curve: ```
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/0003/citationsReturns a JSON shape mirroring this page.- The legacy
/api/v1/cips/0003/mentionsstays for backward compat. It returns topic / thread counts; this new endpoint returns per-post / per-message granularity plus GitHub and YouTube coverage.