PROPOSAL: Community Burn - Burning of 228,000,000 CRO #1322
Unanswered
lezzokafka
asked this question in
Ideas
Replies: 1 comment
|
The on-chain proposal is now live as Proposal #36 and is in its voting period.
Details:
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
PROPOSAL: Community Burn - Burning of 228,000,000 CRO
Introduction
Following four successful burns of 50 million CRO each, we propose a fifth burn of 228 million CRO on the Cronos POS Chain. If passed, this will permanently remove another 228 million CRO and bring the total burned to 428 million CRO.
Background
As introduced in the previous proposals, the "Burning Mechanism of CRO" #941 has been implemented and has been continuously allocating a portion of the CRO generated through emissions to the community pool at the Cronos POS Chain protocol level. The accumulated amount is then periodically burned to complete the cycle.
Four burns of 50 Million CRO each have been executed to date, 200 Million in total. This proposal is the fifth, and it is materially larger than those before it: 228 Million in a single step.
The proposed 228 million community burn opens a new page for the ecosystem and follows the successful launch of Ult and Cronos Launch.
Technical Details
To execute the "burn", a "community pool spend" governance proposal with a target address needs to be initiated. In particular, funds from the community pool are proposed to be moved to the "dead" address (i.e.
cro1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqtcgxmv), which no one has control over. The current pending and burned amount, as well as historical burn events, are on the about CRO page.Governance Votes
After discussion and suggestion to this proposal, an on-chain governance proposal will be raised. The following items summarize the voting options and what they mean for this proposal.
The voting period is 14 days. Quorum is 33.4% of bonded CRO, and more than 50% of non-abstain votes must be Yes. If you delegate and do not vote, your stake inherits your validator's vote, and voting directly overrides it.
Nothing burns until a vote passes. On a successful tally the transfer executes automatically at the end of the voting period, with no further action required by any team or individual.
Let us know your thoughts
The importance of active community participation in shaping the future of the Cronos POS chain cannot be overstated. Engage with your delegated validators and participate in proposal discussions on Discord and GitHub. Your input is vital in fostering a vibrant ecosystem that benefits all CRO holders and the wider ecosystem.
Disclaimer: This proposal is provided for informational and governance-discussion purposes only. Nothing in this proposal constitutes, or should be construed as, financial, investment, tax, or legal advice. Governance participants should conduct their own independent evaluation before voting. This proposal contains forward-looking statements, projections, and illustrative examples based on current expectations and assumptions. Actual outcomes may differ materially due to a range of factors, including, without limitation, market conditions, user adoption, regulatory developments, technical considerations, security risks, and governance decisions. Nothing in this proposal constitutes a guarantee, commitment, or promise of future performance, results, or product availability.
All reactions