Terra Classic statsLUNC · USTC · ON-CHAIN DATA
Reading the proposal and its separately reported chain context.
Loading the proposal. Its status, vote amounts and original source times will appear when the readings are ready.
Back to governanceWaiting for evidence.
Waiting for evidence.
Waiting for evidence.
Waiting for evidence.
This pending view does not establish a proposal result, current voting power or a successful source read.
The technical details of this can be a bit complex. I will try to simplify some of it at the cost of a little less precision in definitions and numbers. This draft has been up a few weeks ago with more details on block proposer rewards. I removed those parts as proposer rewards will be removed with SDK 0.47+. For those who want to read the old one, you find it here: https://commonwealth.im/terra-classic/discussion/14064-changing-the-reward-share-distribution-of-the-burn-tax Important: This proposal does not change the burn tax rate, nor the amount sent to burn! Problem Definition Currently, Terra Classic has a burn tax, that is set to 0.5%. It is distributed as follows: - 80% to burn - 20% to distribution The distribution in detail is like this: - 80% to burn - 10% to Community Pool - 10% to rewards Until SDK 0.47 there are also block proposer rewards which lower the block rewards part. I leave this out for simplicity (see first paragraph). Changing the distribution I propose to change the burn tax distribution as follows: - 80% burn - 10% Community Pool - 10% Oracle Pool This would have several effects. 1. Block rewards would only include gas fees as it was before the tax distribution. 2. Instead of immediate block rewards, the portion from the tax would go into long-term staking rewards (Oracle) 3. Fairer distribution of the tax (which should not be distributed like gas fees) Regarding the concern that this would reduce the APR (staking rewards gained), by my calculation it would only reduce the APR by about ~0.5%, but this also fluctuates depending on on-chain volume (LUNC/USTC sent, not # of transactions). Gas fees would still be distributed immediately on each block and not sent to the Oracle Pool. Things to note: It is important to mention (for everyone to make informed decisions) that the share of APR that is contributed by block rewards (vs. oracle rewards) fluctuates depending on on-chain volume. On lower volume, the oracle share on rewards is > 90-95%. It is also important that this change needs L1 coding, i.e. can not be done with a parameter change. I would propose to introduce a new "oracle_tax" parameter according to the existing "community_tax" parameter which decides on the percentage from distribution that goes to CommunityPool. Cast your vote Yes: I agree that the distribution method should be changed No: I want to leave the distribution method as is Abstain: I want to go with the majority vote No with Veto: - Discussion thread on Commonwealth: https://commonwealth.im/terra-luna-classic-lunc/discussion/15319-changing-the-reward-share-distribution-of-the-burn-tax
Connect Keplr to read your vote and review a new vote or update while the chain keeps voting open.
PASSED · Voting deadline
Your wallet holds the keys and approves each transaction. A submitted vote can have no voting power; participation weight and final eligibility are determined by the chain.
Submitted
18 Apr 2024, 11:22:19 UTC
Vote closed
25 Apr 2024, 12:33:56 UTC
Delivery proof needed
The vote records approval, but manual deliverables still need independent evidence.
Proposal status, current block and node version are separate responses with their own original clocks.
A reported PASSED status for routed protocol messages is consistent with successful governance handlers in supported SDK versions. The production fork and its version at execution are not independently established here. A text mandate still needs delivery evidence; a requested treasury payment is not a reconciled recipient payout.
Current block response metadata
Reported response header height: 31256620 · reported
Public requested / response origin: Withheld or unavailable / Withheld or unavailable
Node info response metadata
Reported response header height: 31256620 · reported
Public requested / response origin: Withheld or unavailable / Withheld or unavailable
Cached responses keep their original completion clocks. The block header time is a reported chain time, separate from HTTP completion and page assembly. Missing, invalid, future, wrong-chain or legacy source evidence is withheld. The block and node-info reads have no common-height guarantee; reported response metadata does not authenticate chain state.
A current block reaching an upgrade target does not prove software activation or validator adoption. A separately reported current node version does not establish the historical execution version or which proposal caused it. These responses do not independently verify execution receipts, recipient payouts or off-chain delivery.
Current or final voting power, calculated from the on-chain tally.
Historical bonded stake and vote-close parameters are not available here. Turnout and threshold checks are withheld; the recorded proposal status remains authoritative.
Amounts use the separate tally endpoint response.
Selected tally
Current staking pool
Current tallying parameters
Current reported SDK context
The model uses SDK0.53.6/math1.5.3 fixed18-place quotient and half-even rounding on reported integer aggregates. Quorum allows equality; approval and veto require strictly greater shares. Expedited approval uses its separately returned expedited threshold. Missing supported SDK/rule/threshold evidence withholds decisions. Internal fractional voting power and production custom tally logic are not reconstructed or independently established.
Cached inputs keep their original completion clocks. These independently read responses have no common-height guarantee; reported headers do not authenticate chain state. Missing, invalid, future or legacy evidence is withheld. Reported zero votes stay zero; unavailable amounts are not zero votes.
Current stake and thresholds are shown only as current context. They are not used to reconstruct a closed proposal’s turnout or threshold result. This does not establish historical voter eligibility, voting weights or vote-close rules. Amounts are approximate displayed LUNC from reported micro amounts; these reads do not verify execution, payouts or delivery.
Quorum
Not available
Participation unavailable
Approval
Not available
81.60% decisive Yes
Veto
Not available
0.08% of participation
What this message can change—not a prediction of price.
Changes between retained samples near vote close and the 7, 30, and 90 day targets. Sample times and a 36 hour tolerance show how closely each pair matches its target.
Retained outcome assembly available
These retained comparisons have a separate assembly clock. It does not refresh the original proposal, block, node or parameter source clocks.
These times describe optional assembly, separate from retained sample capture times and original upstream response completion. Optional outcome work has a 1.2-second wait budget. Core reads and server load can make the total response take longer. The same admitted work continues after that wait; later requests can reuse its completed result. The original core cache and source clocks remain unchanged. No automatic page polling is added.
Manual success criteria required
This proposal does not map cleanly to a chain-wide metric. Delivery evidence must come from its stated milestones.
/cosmos.gov.v1.MsgExecLegacyContent/cosmos.gov.v1beta1.TextProposal