← CIP-0096 · citation graph
CITATIONS / CIP-0096
Removing Liveness Rewards from Validator Rewards Pool · status: Approved
Every place across CCPEDIA's corpus that references CIP-0096 — 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 · 3
CIPs that declare a requires: dependency on CIP-0096, or reference it in their content.
Forum posts · 1
Individual posts on forum.canton.network that mention CIP-0096. Showing 1 most recent of 1.
Hi Alex, liveness rewards have been removed as per CIP 96 . Moving forward, validators will need to actively participate in the network and provide utility to earn rewards, rather than relying on live
Mailing-list messages · 19 · across 7 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.
… iefer, Simon Meier Status: Draft Type: Tokenomics Created: 2026-05-22 License: CC0-1.0 ## Abstract [CIP-0096](https://github.com/canton-foundation/cips/blob/main/cip-0096/cip-0096.md) removed validator livene …
Hi all, New votes have been created in Devnet, Testnet and Mainnet for Vote 4 of CIP-0096. DevNet Vote ID: 00d040eacd02c0c693277db7d5897888b3f5c1d7792cf3537930d3873ee2f6e49eca12122080252516 …
Hi all, New votes have been created in Devnet, Testnet and Mainnet for Vote 3 of CIP-0096. DevNet Vote ID: 0060d85de8d319a90b7781447d949bc1a02707fab54779ae881886d5863f3bee61ca121220ababe27b …
… ve initiated a vote proposal on TestNet to implement the minting delegation logic from CIP-0073 and CIP-0096, by adopting the Daml package `wallet` 0.1.16, which was introduced in Splice 0.5.9. Proposal Contr …
… Daml model version associated with the minting delegation implementation specified in CIP-0073 and CIP-0096. ContractID: 006a1e32db63e3f3e58389707323be79a33d2cc3b80e0a3f47b1ebdf2a9f35e3a9ca121220b5d939a43cbe …
Hi All, New votes have been created in Devnet, Testnet and Mainnet for Vote 2 of CIP-0096. Vote proposal has been created DevNet Vote ID: 008ece8cf56e9ca61f229d601e8bc22fc1bc1d9857a96db9646 …
Hello, Canton Improvement Proposal CIP-0096: Removing Liveness Rewards from Validator Rewards Pool The vote reached a passing quorum on Decembe …
Thank you for the work on this Andrew. Proof Group would like to formally endorse this for a vote. Chris Matturri chris@... ProofGroup.xyz toggle quoted message Show quoted text
Thank you Luke and Demo for your feedback on the impact of the Liveness winddown timeline. We’d like to propose a new schedule based on your feedback: No more than 5 days business from CIP Approval: L
I agree with Demo and think his proposed more gradual step-down is a better solution here. To preface, I’ll reiterate that we’re not opposed to a wind-down of liveness rewards, but believe that doing
Thank you for sharing the comments Demo and the updated proposal Andrew & Cumberland team. I believe the recommended 90 day timeline does a nice job of reflecting the feedback we heard last week on ex
I would like to propose an alternative to the Liveness Rewards Liveness Rewards Proposal: I’ve been thinking more about the Liveness Rewards discussion and wanted to share a refined proposal for the c
Hi All, Thank you for all the feedback on this CIP. Cumberland has made several edits based on feedback we’ve received and would like to share an updated draft. A summary of the changes: Extending the
The algorithm for Validator Rewards is (roughly) as follows: 1. Calculate all Activity Rewards first 2. If there is any remainder, split pro-rata across the Validators online as Liveness This proposal
Hi Eric, thanks for the answers! I am (mostly) aware of everything, but maybe im misunderstanding what you are trying to do here. You wrote "If this CIP passes, the full Validator Reward pool can stil
Thank you Sam and Luka for submitting comments on this proposal. A few added bits of context for those looking at the proposal. Canton Validators do not provide validation for the network _generically
Hello! This proposal does not seem well thought to me. First of all, Canton is (supposedly) built upon network participation - that includes validators as well. Running a validator does require infra
What will be the remaining incentives for validators to run the infra and maintain it if the liveness rewards go to zero? I'm concerned removing this completely gives no incentive for passive validato
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
GitHub items · 6
Issues, PRs, and dev-fund proposals across all indexed Canton repositories that mention CIP-0096.
## Summary - Validator liveness rewards were discontinued by [CIP-0096](https://github.com/canton-foundation/cips/blob/main/cip-0096/cip-0096.md), phased down to a $0 cap …
… wards," which is no longer accurate per cip 96: https://github.com/canton-foundation/cips/blob/main/cip-0096/cip-0096.md
… still presented **validator liveness rewards** as active income with a per-round dollar cap. Per **CIP-0096**, the validator liveness reward cap was phased down to **$0 effective 2026-04-30**, leaving activi …
… e **validator liveness rewards** as a live income mechanism with a per-round dollar cap. However, **CIP-0096 ("Removing Liveness Rewards from Validator Rewards Pool", Status: Approved)** sets the **Validator …
The specification section was incorrectly stating that Vote 1 should set the liveness cap to 2.5 instead of 3.33 as specified in the abstract. This has been fixed in this pull request.
Blog posts · 1
Third-party coverage and ecosystem blog posts. Each links to the original publisher; CCPEDIA only indexes, doesn't republish.
Canton Network has ended liveness rewards for validators, moving its incentive model away from passive node operation and toward usage, application demand, and long-term alignment.
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/0096/citations— JSON shape mirroring this page.- The legacy
/api/v1/cips/0096/mentionsstays for backward compat — it returns topic / thread counts; this new endpoint returns per-post / per-message granularity plus GitHub and YouTube coverage.
