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.
Proposal: This proposal aims to secure an official organization to be in charge of hosting the endpoint providing the correct circulating supply data for Luna Classic. In addition, it aims to get a consensus about the method of calculating the circulating supply. We propose that Allnodes is appointed to the role providing the endpoint through a governance vote. Problem: Luna Classic does not have a named individual or organization to operate as an provider of circulating supply data for the chain. This leaves open the possibility of individuals making changes to the calculation (e.g. removing wallets from the calculation) that could be harmful to the chain, without any discussion with developers, validators, or community members. Solution: We propose that Luna Classic appoint an official source for the circulating supply as voted on by governance. We believe this to be Allnodes. To accomplish this, we would ask that Allnodes updates to the latest FCD version that implements the following calculation of circulating supply: Circulating Supply = Total Supply – unvested Tokens – Community Pool Holdings – Staked and bonded tokens This will mean that any third party website could use Allnodes FCD API as the official information source for Terra Classic circulating supply of LUNC, USTC and other native tokens. The calculation of the circulating supply inside the FCD must not be changed without a governance vote. An approval of an official source via governance ensures that all data comes from an agreed upon and trusted source. It also reduces the risk of individuals changing the reported circulating supply or total supply, without appropriate discussion and input. This proposal identified the official circulating supply source as Allnodes. • Allnodes has agreed to this task, provided they are appointed to the role via a governance vote. • Should this proposal pass, the adjusted FDC for the Luna Classic chain will be run by Allnodes, ensuring the correct circulating supply of LUNC and USTC. Historical situation: For completeness, we want to provide the historical calculation done in the FCD until now. This calculation has handled LUNC different from all other native tokens. Former calculation for LUNC: Circulating Supply = Total Supply – unvested tokens – Community Pool Holdings – configured bank accounts Former calculation for USTC and other native tokens: Circulating Supply = Total Supply – unvested tokens The proposed calculation will deduct staked tokens (bonded only) from the circulating supply as well as unifying the handling of Community Pool funds. If Allnodes want to reject this then I kindly ask them to vote NO on this proposal. I (DNC) believe that this is of a nature that the community would want the proposal put up for vote straight away, again if this is not the case then please vote No. Cast Your Vote: • Yes, I agree • Abstain • No • No With Veto Signed By @Lunanauts @DNCLunc @PinkUnicorn @NuengHandsome
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
12 May 2024, 22:05:13 UTC
Vote closed
19 May 2024, 22:07:42 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: 31256618 · reported
Public requested / response origin: Withheld or unavailable / Withheld or unavailable
Node info response metadata
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
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.TextProposalReported response header height: 31256618 · 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 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
79.55% decisive Yes
Veto
Not available
11.99% of participation
What this message can change—not a prediction of price.