Skip to main content
Terra Classic statsLUNC · USTC · ON-CHAIN DATA
StatsBin logo

StatsBin.

Terra Classic Stats

Burn AdsSearchWallet
HomeNetworkBridgesSupplyStakingBurnsValidatorsWalletsProposalsNewsGamesTools

StatsBin.

The Terra Classic observatory

Independent LUNC and USTC data, from supply and burns to validators, wallets and governance.

Explore

LUNC dashboardIndexed chain historyLUNC stakingLUNC supplyBurn intelligenceValidatorsGovernanceLUNC newsLUNC Games

Connect

Data methodologyMachine access · LUNCAgentStatsBin LUNC Validator Follow on X Contact
© 2026 StatsBin · Independent Terra Classic intelligence
PrivacyTermsCookiesAccessibility

Loading proposal evidence

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 governance

Proposal and lifecycle

Waiting for evidence.

Vote math and sources

Waiting for evidence.

Executable messages

Waiting for evidence.

Reality Check evidence

Waiting for evidence.

This pending view does not establish a proposal result, current voting power or a successful source read.

All proposalsRaw proposal
Proposal #12059
REJECTED
Last saved data
Text mandate

Contributions without KYC

Following the approval of Proposal 12033: Individuals/teams to be granted permission to contribute code through a party that has completed KYC with one of the approved providers, on the condition that after the KYC party has reviewed and upon merging the code, the KYC party accepts liability for the code to be transferred to them. This is to address concerns for small code/bug fixes and those who work on a voluntary basis. Many community members have also stated that contributions would be offered to cover the full cost of KYC for volunteer developers. Please reach out on X should this be required.

Not approved
high confidence · manual executionVote or view your voteRecorded validator choices

Vote on proposal #12059

Connect Keplr to read your vote and review a new vote or update while the chain keeps voting open.

REJECTED · Voting deadline 2024-02-18 11:02:27 UTC

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.

Get Keplr
Choose your vote

Submitted

10 Feb 2024, 12:23:45 UTC

Vote closed

18 Feb 2024, 11:02:27 UTC

Not approved

The proposal did not produce an approved governance action.

Reported governance context

Proposal status, current block and node version are separate responses with their own original clocks.

Reported proposal status
REJECTED
Reported current block
31256605
Reported app / SDK version
4.1.1 / v0.53.6

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.

Governance sources & scope
Original proposal response completion (UTC)
2026-11-12T14:45:24.830Z
Public proposal requested origin
Withheld or unavailable
Original current block response completion (UTC)
2026-11-12T14:45:24.842Z
Reported block header time (UTC)
2026-11-12T14:45:18.709854846Z
Original node-info response completion (UTC)
2026-11-12T14:45:24.843Z

Current block response metadata

Reported response header height: 31256604 · reported

Public requested / response origin: Withheld or unavailable / Withheld or unavailable

Node info response metadata

Reported response header height: 31256604 · 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.

Vote math

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.

Vote math sources & scope

Selected tally

Original response completion (UTC)
2026-11-12T14:45:24.836Z
Reported response header height
31256604 · reported
Public requested origin
Withheld or unavailable
Public response origin
Withheld or unavailable

Current staking pool

Original response completion (UTC)
2026-11-12T14:45:24.835Z
Reported response header height
31256604 · reported
Public requested origin
Withheld or unavailable
Public response origin
Withheld or unavailable

Current tallying parameters

Original response completion (UTC)
2026-11-12T14:45:24.836Z
Reported response header height
31256604 · reported
Public requested origin
Withheld or unavailable
Public response origin
Withheld or unavailable

Current reported SDK context

Original response completion (UTC)
2026-11-12T14:45:24.843Z
Reported response header height
31256604 · reported
Public requested origin
Withheld or unavailable
Public response origin
Withheld or unavailable
Reported proposal approval rule
Ordinary
Supported current SDK model context
v0.53.6
Selected approval threshold
50.00%
Reported raw tally inputs
Yes reported micro voting power
133741850650474519
No reported micro voting power
147468032831165272
Abstain reported micro voting power
271630658264653781
No with veto reported micro voting power
81137541203214855

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.

Separately reported current bonded stake
897,160,665,251.97 LUNC
Current quorum / approval / veto thresholds
40.00% / 50.00% / 33.40%

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.

Yes133,741,850,650.47 LUNC · 21.10%
No147,468,032,831.17 LUNC · 23.26%
No with veto81,137,541,203.21 LUNC · 12.80%
Abstain271,630,658,264.65 LUNC · 42.85%

Quorum

Not available

Participation unavailable

Approval

Not available

36.91% decisive Yes

Veto

Not available

12.80% of participation

Expected impact

What this message can change—not a prediction of price.

Community mandate
Manual delivery
  • Records community intent but does not itself change chain state.
  • Delivery requires external evidence such as code, releases, transactions, or milestone reports.

Outcome scoreboard

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.

Outcome assembly & scope
Optional work started (UTC)
2026-11-12T14:45:24.843Z
Optional work completed (UTC)
2026-11-12T14:45:24.843Z

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.

On-chain message evidence

/cosmos.gov.v1.MsgExecLegacyContent/cosmos.gov.v1beta1.TextProposal