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 king is naked! We as concerned community members call to repeal the KYC prop because it stifles the growth of Terra Luna Classic. This proposal was made in haste and voted in haste, without sufficient foresight about the consequences it will have in the future. This is clearly evidenced by the number of follow-up props trying to patch up the deficiencies of the initial KYC prop. That is not serious at all. Spilt water cannot be gathered up again! We as LUNC investors have watched from the sidelines enough. It is clear that the negative effects of KYC outgrow the positives ones by far. Not only that, but also many authoritative (!) members of the LUNC community have been very vocal about the negatives of KYC, and consider it a bad direction to go in for a decentralized blockchain. Nobody is going to touch the repeg idea as a KYC’d individual! Now that we have had time to reflect on its effects, we can conclude that the KYC as a mandatory requirement does not hold water. LUNC cannot afford the luxury to be selective about its developers buring the bull-run. We must get and receive all help we can, including from Inonman and others. We believe we are not alone in thinking this, and we are not happy with the direction we are going right now. At the same time, we understand the initial YES vote was made with good intentions in mind, however, as we all know, the road to hell is paved with good intentions. Therefore, we propose to repeal the Proposal #12033 and let any and all developers work on the chain! Any developers can still KYC if they wish to do so – the community will be more than happy to welcome such developers onboard – however, that should not be a mandatory requirement at all. By voting ‘YES’, you agree to repeal the KYC proposal #12033 as well as the Certik proposal #12058. By voting NO, you do not agree to repeal the KYC proposal #12033. -Lunc Community
Connect Keplr to read your vote and review a new vote or update while the chain keeps voting open.
REJECTED · 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
16 Mar 2024, 08:30:58 UTC
Vote closed
28 Mar 2024, 17:15:56 UTC
Not approved
The proposal did not produce an approved governance action.
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: 30753007 · 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: 30753007 · 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
30.13% decisive Yes
Veto
Not available
2.38% of participation
What this message can change—not a prediction of price.