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.
This is a text proposal under the Pay Per Job structure (Proposal 11889). This vote moves no funds and sets no LUNC amount. Prepared by Terra Classic Core (Bumeo Capital and LunaClassicDAO). Proposers: Puya (Bumeo Capital) and Classic DAO (LunaClassicDAO) Renzo (LunaClassicDAO) and Till / Frag (Bumeo Capital). Auditor: SolidProof (FutureVisions Deutschland UG), https://solidproof.io/ Agreement: Security Audit Agreement dated 28 October 2026, fixed fee USD 85,200 for 568 engineer-hours. Agreement SHA-256: 69d3b88f874465951ff8e5c9694f1dc895d5232be6a01bcf38ef4078155d39f0 Discussion: https://agora.terra-classic.io/t/591 Proposal PDF: https://drive.google.com/file/d/1HNECUlombOiCYXIrH3dxv-mZSsCT-Rj2/view Agreement PDF: https://drive.google.com/file/d/1h2PSVeAQ5WlNVMgeBXJ6TsIUncXeF-77/view SUMMARY Approve one job: an independent SolidProof security audit of the Terra Classic core chain, covering the whole codebase at the frozen commit, which contains Terra Classic Core v4.1.1 now live on mainnet (Proposal 12233), and the pre-deployment additions on the ustc_staking branch (Market Module 2.0, the new x/ustcstaking module, the tax-redirect mechanism and the v15 upgrade handler). The fee is fixed at USD 85,200 for 568 engineer-hours, including a full re-audit after remediation. Renzo and Till (Frag) fix all findings free of charge. The community pays only SolidProof's audit fee and the conversion cost. The job is funded in two later community-pool spend proposals, after this text passes: 40% upfront (USD 34,080), paid before SolidProof starts; and 60% on delivery of findings (USD 51,120), including the re-audit, which is not charged separately. Each spend is sized backward from the USDC due so SolidProof receives the full contracted amount after fees (up to about 7% all-in; see Amount and Payment). No buffer is added. Any leftover LUNC or USDC is returned to the community pool. RATIONALE The post-SDK53 core (Cosmos SDK 0.53, ibc-go v10, upstream wasmd 0.61) is live on mainnet and has not been independently audited. Market Module 2.0 and USTC staking, in preparation on ustc_staking for v15, move funds and re-activate swap economics, so they should be reviewed before deployment. Pay Per Job requires a text vote first; money moves only through later spend proposals tied to the work. SCOPE OF WORK Per the SolidProof Security Audit Agreement dated 28 October 2026 (SHA-256 above): - Repository: https://github.com/classic-terra/core - Branch: ustc_staking - Frozen commit: 35d68fe1b3eb811c27e8bf3f398d5cc197897229 (15 October 2026) - Base: f54cdec2ed8aa04a83d904fe21d5d2a63d35ff93 (v4.0.1-patch.3, live on mainnet) plus 52 commits [agreement wording; on GitHub, tag v4.0.1-patch.3 is 8d9d136; mainnet now runs v4.1.1, which the frozen commit contains] - Size at freeze: 30,329 raw lines / 23,203 nSLOC of non-test, non-generated Go, plus 31 .proto definitions in scope Contracted workstreams: - Core protocol audit: 288 hours, USD 43,200 - Framework migration and state integrity review: 88 hours, USD 13,200 - Adversarial simulation and economic review: 64 hours, USD 9,600 - Market Module 2.0, USTC staking module and v15 upgrade: 96 hours, USD 14,400 - Full re-audit after remediation: 32 hours, USD 4,800 - Total contracted effort and fee: 568 hours, USD 85,200 Agreement §1 includes: "Examination of the pre-deployment additions on the ustc_staking branch frozen under §1.1: the Market Module 2.0 re-implementation and its re-activated swap economics; the new x/ustcstaking module and its staking and reward logic; the tax-redirect mechanism and market accumulator account in the fee and burn-tax path; the oracle TWAP and freshness hooks; and the v15 upgrade handler." Out of scope: as set out in Appendix A §5 (Explicit Exclusions) and Appendix B §3 (Out of scope) of the agreement. Deliverables: Threat Model and Architecture Note; Hardened Continuous Integration Configuration (pull request); Interim Findings Report (Critical and High); Audit Findings and Draft Audit Report (triggers the 60% payment); Public Audit Status Note (at the 40% spend and again on delivery of findings); Final Audit Report after re-audit; Recommendation Summary (consensus-breaking vs non-breaking); Fix Verification Statement (per finding, with the re-audit). SolidProof reports Critical findings within 24 hours and High findings within three business days. Unfixed Critical and High findings stay under embargo "until a patch has been released and validator adoption confirmed, or for 90 days from the report, whichever occurs earlier" (§6.2). AMOUNT AND PAYMENT Rate: USD 150 per engineer-hour. Fixed total: USD 85,200 for 568 hours, paid in USDC. No LUNC amount is set in this vote. - 40% upfront, before SolidProof starts, own spend proposal: USD 34,080 - 60% on delivery of findings, including the re-audit, own spend proposal: USD 51,120 - Fixing all findings (Renzo and Till (Frag)) and development: USD 0 Both payments are made only if their community-pool spend proposals pass. Each spend is sized at the LUNC rate when it is submitted; the rate source, date and resulting LUNC and uluna amount will be posted with that spend. No buffer of any kind. No prepaid fix budget. The fee is remitted in USDC to SolidProof's USDC address, stated in each spend proposal; SolidProof bears no LUNC price, conversion or slippage risk. Funds flow: community pool to Client receiving multisig to off-chain SimpleSwap (about 2-3.5% on recent quotes at each 40%/60% tranche) to SolidProof in USDC. On-chain LUNC transfers also incur about 1.5% in Terra Classic fees on each taxed transfer (up to two transfers: community pool to receiving multisig to SimpleSwap). That is up to about 7% all-in (about USD 91,000 for both spends at the worst case). Each spend is sized so SolidProof still receives the contracted USD amount after those costs. Any leftover LUNC or USDC after SolidProof is paid is returned to the community pool, and the transaction is posted in the Agora thread. Receiving multisig, four signers: Renzo (LunaClassicDAO), Frag (Bumeo Capital), Puya (Bumeo Capital) and Classic DAO (LunaClassicDAO). The multisig address and signing threshold will be stated in each spend proposal. SolidProof's USDC payment address will be stated in each spend proposal. DIFFERENCES FROM THE AGREEMENT Agreement §4.3 states a conversion cost of about one per cent and returns leftovers to Terra Classic Core; §11 returns any unearned upfront payment to Terra Classic Core. This proposal budgets the live fees above (up to about 7% all-in), and all leftovers and refunds return to the community pool. SolidProof's written acknowledgement of these differences will be posted on Agora before the first spend proposal. The hashed PDF contains Appendices A and B; Appendix D addresses are stated in each spend proposal. TIMELINE After this text passes, the first spend (40%, USD 34,080) is submitted and voted. After that spend passes and payment is received: three-week lead time (subject to team availability), then SolidProof starts. End of week 1 from start: Threat Model and Architecture Note; hardened CI pull request. End of week 5: Interim Findings Report. End of week 8 (report within three business days): Audit Findings and Draft Audit Report (triggers the 60% spend). After delivery of findings, the second spend (60%, USD 51,120) is submitted and voted. Client remediation window: up to four weeks; Renzo and Till (Frag) fix findings at no cost. Within one week of written remediation complete: re-audit and Fix Verification Statement. Within five business days of the re-audit: Final Audit Report. Completion: report and fix status posted on Agora; leftovers returned to the community pool. WHAT THIS PROPOSAL DOES NOT DO It does not move funds or set a LUNC amount, fund any development or prepaid fix budget, change any chain parameters, or approve any software upgrade. It does not deploy Market Module 2.0, x/ustcstaking or v15; those remain pre-deployment until a separate upgrade process. HOW THIS DIFFERS FROM PROPOSAL 12228 Unlike Proposal 12228 (rejected: US$70,800 audit for 472 hours paid upfront in one spend with a 20% buffer, US$84,960; OrbitLabs fixes US$20,000 paid after completion; LUNC amount set on-chain; earlier freeze f54cdec on main, nearest tag v4.0.1-patch.3, 9 September 2026; total US$90,800), this is a text vote first under Pay Per Job, with 40/60 through two later spends, no buffer, no paid fix budget (Renzo and Till (Frag) at US$0), no LUNC amount in this vote, leftovers returned to the community pool, and the later freeze 35d68fe on ustc_staking (15 October 2026: post-SDK53 core plus Market Module 2.0, USTC staking and v15; 568 hours). Cost is the USD 85,200 audit fee plus fees as set out above (up to about 7% all-in, about USD 91,000 worst case). TEAM Puya (Bumeo Capital and Juris Protocol); Classic DAO (LunaClassicDAO and WESO); Frag / Till (Bumeo Capital and LuncGoblins); and Renzo (LunaClassicDAO). Frag and Renzo are Layer 1 developers and Dynamic List Management members (Proposal 12205). Authorised representatives under the agreement: Puya and Classic DAO. VOTING OPTIONS YES: You approve this SolidProof audit (frozen commit 35d68fe) at the fixed fee of USD 85,200, paid in USDC, 40% (USD 34,080) upfront and 60% (USD 51,120) on delivery of findings, through two later community-pool spend proposals (up to about 7% all-in, about USD 91,000 worst case). No buffer. Findings fixed by Renzo and Till (Frag) at no cost. Leftovers return to the community pool. This vote moves no funds. NO: You do not approve this job. No audit is engaged under this proposal, and no spend proposals under this job are authorized. NO WITH VETO: You consider this proposal spam or an abuse of governance. If the veto threshold is reached, the deposit is burned. ABSTAIN: You do not wish to vote for or against, but want your vote counted toward quorum. REFERENCES - Pay Per Job: Proposal 11889 - Proposal 12228 discussion: https://agora.terra-classic.io/t/536 - Frozen audit commit: https://github.com/classic-terra/core/commit/35d68fe1b3eb811c27e8bf3f398d5cc197897229
Connect Keplr to read your vote and review a new vote or update while the chain keeps voting open.
VOTING PERIOD · 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 Nov 2026, 15:01:09 UTC
Voting now
23 Nov 2026, 15:01:09 UTC
Live vote
Vote totals are still changing; no implementation claim is possible yet.
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: 31315304 · 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.
Live turnout and threshold checks use current bonded stake and current governance parameters; observations may be from different blocks.
Amounts use the separate tally endpoint response.
Live threshold checks model independently read reported inputs. They do not predict the recorded proposal result. Supported current SDK context is reported.
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.
Bonded LUNC
Preferred signal: up
Reported response header height: 31315304 · 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.
Live turnout and threshold checks require the separately returned current tally, current bonded stake and current parameters with their original evidence. 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 reached
0.34% participating
Approval
Passing
100.00% decisive Yes
Veto
Below threshold
0.00% of participation
What this message can change—not a prediction of price.
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.
Staking ratio
Preferred signal: up
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.
Top-10 voting power
Preferred signal: down
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.