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.
# Genuine Labs's Community Spend Proposal On behalf of Genuine Labs, I'm submitting this proposal for the work we have undertaken over the past four weeks. Our focus has been on implementing end-to-end (E2E) tests, interchain tests, and addressing issues related to the PacketForwardMiddleware (PFM) and IBC hooks. We have maintained transparency throughout the works by providing biweekly reports on our progress. You can find detailed updates work in the following links: - [Biweekly Report 1](https://hackmd.io/@I6jxy3DTTEeZcmtjEz1kLw/SJ-bxebtp) - [Biweekly Report 2](https://hackmd.io/@I6jxy3DTTEeZcmtjEz1kLw/By2vxd756) The cost of these works, as referred to in [11940](https://ping.pub/terra-luna/gov/11940), is $16,000 (to be paid in LUNC from the community pool at the current exchange rate: 160,000,000 LUNC) Current market price of LUNC at the time of this proposal: $0.0001/LUNC *Vote Options:* Vote **Yes** if you are satisfied with our efforts and agree to fund Genuine Labs. Vote **No** if you are not satisfied with our work and disagree with funding us on LUNC. Vote **No With Veto** if you see this proposal as spam or harmful to the chain. Vote **Abstain** if you simply want to contribute to the quorum.
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
30 Jan 2024, 17:14:02 UTC
Vote closed
06 Feb 2024, 17:56:23 UTC
Reported protocol action
The provider reports PASSED with a supported routed message shape. In supported Cosmos SDK governance, PASSED follows successful routed handlers; this is reported protocol context, not an independently verified receipt or proof of external delivery. The actual chain fork and historical execution version remain unverified here.
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: 31256602 · reported
Public requested / response origin: Withheld or unavailable / Withheld or unavailable
Node info response metadata
Reported response header height: 31256602 · 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
99.86% decisive Yes
Veto
Not available
0.01% of participation
What this message can change—not a prediction of price.
160,000,000 LUNC
terra1skahyp7dzcu5uu2jarresqhnsn99mz6pd7r57d
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.
Community pool
Preferred signal: context
7 day target
A valid baseline and endpoint pair is unavailable within the sample tolerance.
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
A valid baseline and endpoint pair is unavailable within the sample tolerance.
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
A valid baseline and endpoint pair is unavailable within the sample tolerance.
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.
/cosmos.gov.v1.MsgExecLegacyContent/cosmos.distribution.v1beta1.CommunityPoolSpendProposal