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

7 total referencesSibling CIPs 2Forum posts 0Mailing messages 3GitHub items 2Blog posts 0YouTube videos 0JSONMCP: get_cip_citations

Sibling CIPs · 2

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

CIP-0061Final
Add Chainlink as a Super Validator of Weight 7.5
mentions →
CIP-0096Approved
Removing Liveness Rewards from Validator Rewards Pool
mentions →

Mailing-list messages · 3

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-0096: Remove Liveness Rewards from Validator Rewards Pool[cip-discuss] · @Andrew Bryan · 6mo ago

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

  • CIP-0096: Remove Liveness Rewards from Validator Rewards Pool[cip-discuss] · @Andrew Bryan · 7mo ago

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

  • CIP-0096: Remove Liveness Rewards from Validator Rewards Pool[cip-discuss] · @Eric Saraniecki · 7mo ago

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

GitHub items · 2

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

  • Move unchanging parameters out of the issuance curvecanton-network/splice#827 · issue · open · @canton-network-da · 1y ago

    [ 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: ```

  • chore: CIP-35 add five north weight to gsf svcanton-foundation/configs#5 · pr · closed · @tkatrichenko · 1y ago

    https://lists.sync.global/g/supervalidator-announce/topic/vote_proposal_to_add_five/110900321

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