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 #12008
REJECTED
Last saved data
Community funding

L1TF Terra Classic core security upgrade package

This core security upgrade package aims at addressing the security risks, lack of new features originated from legacy components of Terra Classic. Successfully updating these core components will provide up - to - date security and stability, as well as enabling the infrastructure needed for TFL support. This proposal marks the JL1TF's initial request for $25,500 upfront, representing half of the total budget requested. This amount is intended to cover our initial setup costs and serves as a retainer fee, helping JL1TF's long - term commitment to the overall security and stability of the chain. Current market price of lunc at the time of this proposal: $0.000093/lunc Please see the additional details, milestones, and structure here: https://commonwealth.im/terra-luna-classic-lunc/discussion/14878-terra-classic-core-security-upgrade-package

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

Vote on proposal #12008

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

REJECTED · Voting deadline 2024-01-31 04:55:07 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

24 Jan 2024, 04:50:55 UTC

Vote closed

31 Jan 2024, 04:55:07 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
31256599
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:44:55.232Z
Public proposal requested origin
Withheld or unavailable
Original current block response completion (UTC)
2026-11-12T14:44:55.256Z
Reported block header time (UTC)
2026-11-12T14:44:43.115093568Z
Original node-info response completion (UTC)
2026-11-12T14:44:55.254Z

Current block response metadata

Reported response header height: 31256599 · reported

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

Node info response metadata

Reported response header height: 31256599 · 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:44:55.241Z
Reported response header height
31256599 · reported
Public requested origin
Withheld or unavailable
Public response origin
Withheld or unavailable

Current staking pool

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

Current tallying parameters

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

Current reported SDK context

Original response completion (UTC)
2026-11-12T14:44:55.254Z
Reported response header height
31256599 · 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
231356562413606969
No reported micro voting power
363288738550990536
Abstain reported micro voting power
141281623687536575
No with veto reported micro voting power
370691369354070

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.

Yes231,356,562,413.61 LUNC · 31.42%
No363,288,738,550.99 LUNC · 49.34%
No with veto370,691,369.35 LUNC · 0.05%
Abstain141,281,623,687.54 LUNC · 19.19%

Quorum

Not available

Participation unavailable

Approval

Not available

38.88% decisive Yes

Veto

Not available

0.05% of participation

Expected impact

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

Community Pool
Treasury delivery
Recipient accountability
  • Transfers community-controlled funds to the proposal recipient when execution succeeds.
  • Payment proves disbursement, not completion of the promised off-chain work.
Funding message

274,193,548 LUNC

terra1h9jscrxcc0rpkw7h860x87d9rswfdkg4lytqup

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:44:55.256Z
Optional work completed (UTC)
2026-11-12T14:44:55.453Z

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.

Community pool

Preferred signal: context

7 day target

Not applicable

This comparison applies to passed proposals.

Retained samples & scope (7 days)
Reported vote close (UTC)
2024-01-31T04:55:07.948Z
Target date (UTC)
2024-02-07T04:55:07.948Z
Retained baseline capture (UTC)
Unavailable
Unavailable; Unavailable
Retained endpoint capture (UTC)
Unavailable
Unavailable; Unavailable
Comparison evaluated (UTC)
2026-11-12T14:44:55.257Z
Selected sample span / maximum distance from each target
Unavailable / 36 hours
Returned retained samples / accepted unique sample clocks
13528 / 13528
Rejected samples / conflicting sample clocks
0 / 0

Sample times are retained capture timestamps, not original upstream read times or verified chain heights. The nearest supported sample within 36 hours of each target is used; equally close samples prefer the earlier capture. Identical duplicates are merged and conflicting values at the same clock are withheld.

This is a change between two retained numeric samples, not complete coverage of the intervening period. Timing and metric changes do not prove the proposal caused an effect, executed a protocol action, paid a recipient or delivered a promised result.

30 day target

Not applicable

This comparison applies to passed proposals.

Retained samples & scope (30 days)
Reported vote close (UTC)
2024-01-31T04:55:07.948Z
Target date (UTC)
2024-03-01T04:55:07.948Z
Retained baseline capture (UTC)
Unavailable
Unavailable; Unavailable
Retained endpoint capture (UTC)
Unavailable
Unavailable; Unavailable
Comparison evaluated (UTC)
2026-11-12T14:44:55.257Z
Selected sample span / maximum distance from each target
Unavailable / 36 hours
Returned retained samples / accepted unique sample clocks
13528 / 13528
Rejected samples / conflicting sample clocks
0 / 0

Sample times are retained capture timestamps, not original upstream read times or verified chain heights. The nearest supported sample within 36 hours of each target is used; equally close samples prefer the earlier capture. Identical duplicates are merged and conflicting values at the same clock are withheld.

This is a change between two retained numeric samples, not complete coverage of the intervening period. Timing and metric changes do not prove the proposal caused an effect, executed a protocol action, paid a recipient or delivered a promised result.

90 day target

Not applicable

This comparison applies to passed proposals.

Retained samples & scope (90 days)
Reported vote close (UTC)
2024-01-31T04:55:07.948Z
Target date (UTC)
2024-04-30T04:55:07.948Z
Retained baseline capture (UTC)
Unavailable
Unavailable; Unavailable
Retained endpoint capture (UTC)
Unavailable
Unavailable; Unavailable
Comparison evaluated (UTC)
2026-11-12T14:44:55.257Z
Selected sample span / maximum distance from each target
Unavailable / 36 hours
Returned retained samples / accepted unique sample clocks
13528 / 13528
Rejected samples / conflicting sample clocks
0 / 0

Sample times are retained capture timestamps, not original upstream read times or verified chain heights. The nearest supported sample within 36 hours of each target is used; equally close samples prefer the earlier capture. Identical duplicates are merged and conflicting values at the same clock are withheld.

This is a change between two retained numeric samples, not complete coverage of the intervening period. Timing and metric changes do not prove the proposal caused an effect, executed a protocol action, paid a recipient or delivered a promised result.

On-chain message evidence

/cosmos.gov.v1.MsgExecLegacyContent/cosmos.distribution.v1beta1.CommunityPoolSpendProposal