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.
COMMONWEALTH THREAD https://commonwealth.im/terra-classic/discussion/13298-six-samurai-senior-engineering-team-q4-l1-l2-ustc-repeg SUMMARY This is our Q4 spend proposal for the senior engineering full-stack LUNC team (aka the "Six Samurai"), jointly co-led by Bilbo Baggins and Solid Snake. We've assembled this dev team from experienced industry veterans, with the aim of bringing value to the Terra Classic blockchain so that we can help push this chain where it deserves to go. The team is lean, experienced, and agile. The overall spend is now broken into 3 monthly payouts, in order to demonstrate ongoing excellence of work by the team, as well as to reassure the LUNC community we'll deliver on what we promise. If this proposal passes, our team will implement the roadmap outlined below, while at the same time coordinating and collaborating to the best of our ability with Vinh & Superman & Gevik. ROADMAP (L1) Migrate from Columbus-5 to Columbus-6. Update to Cosmos SDK v0.47.x. Establish USTC Testnet. Implement Alliance Module. Implement FeeShare Module. Implement Sane Tombstoning Protection for Validators. ROADMAP (Protocol Level Decentralization) Establish community subpools for better budgeting and cashflow management. Establish decentralized grants program. Establish decentralized bounty program. Explore implementation of Warp protocol for enabling on-chain job automations. Decentralize Station Infrastructure via establishment of validator CDN (Content Delivery Network) ROADMAP (Outstanding Items from Previous Quarters) Pursue Terra Classic listing on Keplr Web Interface and Mintscan Post "Parity Upgrade" impact analysis. Increase validator participation in testnets. Improve documentation for L1, L2, and validators. ROADMAP (USTC & Repeg Work) Spin up a dedicated USTC testnet. Work on the Terra Classic Revival Whitepaper & Repeg Plan. Continue CEX liaisoning and partner outreach. ROADMAP (Classic Portal) In addition to all of the tasks outlined above, we have received requests from many people in the community throughout Q2 & Q3 to build a "Classic website" that the community would be able to use as a central point of information, education, and ecosystem discovery. SIX SAMURAI TEAM The team is co-led by Bilbo Baggins (senior software engineer / architect) and Solid Snake (senior engineer / systems architect), both of whom will also serve as community liaisons and will deliver regular status updates at no extra cost to the community. Joining the two co-leads are: NotJoshC (senior software engineer & security specialist) MangoChutney (senior software engineer, distributed systems) ChopstickSensei (senior software engineer, distributed systems) Mycetism (senior software engineer & frontend / web developer) PROPOSAL Vote "YES" if you agree with this Q4 spend prop for a Six Samurai senior engineering team. Vote "NO" if you disagree with this Q4 spend prop for a Six Samurai senior engineering team. Vote "ABSTAIN" if you neither agree nor disagree, but would still like to help the prop reach quorum. Vote "NO WITH VETO" if you vehemently disagree with funding this team and its work on LUNC. Thank you for your time! Sincerely, The Terra Allies Development Group P.S. Many thanks to all our wonderful and based frens in the community! P.P.S. And an additional thanks to everyone at Lunc Academy, we love you all!
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
02 Oct 2023, 23:23:57 UTC
Vote closed
10 Oct 2023, 00:30:46 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: 31256569 · reported
Public requested / response origin: Withheld or unavailable / Withheld or unavailable
Node info response metadata
Reported response header height: 31256569 · 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
8.02% decisive Yes
Veto
Not available
15.99% of participation
What this message can change—not a prediction of price.
750,000,000 LUNC
terra1m3vzu5s85r9nlep3jjqd4d9ldrskkt7pw70vk4
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
This comparison applies to passed proposals.
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
This comparison applies to passed proposals.
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
This comparison applies to passed proposals.
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