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.
*This is a proposal solely to fulfill prop #11784 - "STOP MINTING AND REMINTING OF USTC"* The only minting of USTC currently happening on chain is through the market module, which allows burning a coin to mint another. This mechanism was disabled for LUNC<->Stable by raising the spread to 100% during the crash, effectively disabling swapping from and to LUNC through the market module. For swapping Stable<->Stable instead of the spread a Tobin tax is used. Setting the Tobin tax to 100% effectively disables swapping the corresponding asset. To fulfill proposal 11784, Vinh from the L1TF already implemented a code change to introduce a new governance parameter that specifically allows setting a Tobin tax for swaps to USTC (the only action that mints USTC). As there is no real exit-route from stables other than USTC anyway, it was discussed to simply raise all Tobin taxes for all stables to 100% instead of a code change. This has the side-effect of disabling market swaps between all stables instead of just swaps *to* USTC. This proposal aims to do as mentioned and raise the Tobin for all stables to 100%, effectively disabling all market swapping and such minting of coins on Terra Classic. Potential pros: No code change / software upgrade needed, USTC minting disabled Potential cons: Swapping between stables (e.g. USTC->EUTC) is also disabled, USTC burning through swaps disabled Important: This does only affect the market swap. It does not affect swapping coins through DEXes like Terraswap. This continues to be possible for existing pairs. If this proposal fails to pass, the route of a software change should be followed to specifically disable swapping TO USTC without touching other stable swaps. Swapping any stable assets to USTC would be disabled with every other solution anyway, as there is no way to prevent minting USTC without disabling the swap to it. What your vote means: Yes: Raise Tobin tax to 100% for all stables on Terra Classic No: Fall back to the prepared code-change solution Abstain: Do what the majority decides No with veto: - Disclaimer: The idea of choosing the "simple route" using Tobin tax to disable swaps originates from a discord chat around how to fulfill passed proposal 11784. This solution exceeds the scope of the original proposal which didn't mention any other assets than USTC. When voting you should be aware and discuss about the potential pros and cons of this solution. There was a test conducted on rebel-2 testnet to ensure that this solution does not result in a loss of funds when someone would try to make a swap with 100% Tobin tax. The chain returned an error about zero swap coins during these tests, so the tx failed and no funds were consumed.
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
03 Nov 2023, 07:51:33 UTC
Vote closed
10 Nov 2023, 22:27:49 UTC
Parameter comparison unavailable
0 of 1 displayed proposed fields match returned module responses; 1 displayed checks are unavailable. 0 further checks are outside the display limit. The recorded proposal status remains reported protocol context, not proof from these current comparisons.
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: 30753132 · 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.
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
Each proposed field is compared only with the returned response from its own module.
Displaying 1 of 1 proposed parameter fields; 0 outside the 24-field display limit. 0 matched, 0 different, 1 unavailable among displayed checks.
Oracle Whitelist
[ { "name": "ukrw", "tobin_tax": "1.000000000000000000" }, { "name": "usdr", "tobin_tax": "1.000000000000000000" }, { "name": "uusd", "tobin_tax": "1.000000000000000000" }, { "name": "umnt", "tobin_tax": "1.000000000000000000" }, { "name": "ueur", "tobin_tax": "1.000000000000000000" }, { "name": "ucny", "tobin_tax": "1.000000000000000000" }, { "name": "ujpy", "tobin_tax": "1.000000000000000000" }, { "name": "ugbp", "tobin_tax": "1.000000000000000000" }, { "name": "uinr", "tobin_tax": "1.000000000000000000" }, { "name": "ucad", "tobin_tax": "1.000000000000000000" }, { "name": "uchf", "tobin_tax": "1.000000000000000000" }, { "name": "uhkd", "tobin_tax": "1.000000000000000000" }, { "name": "usgd", "tobin_tax": "1.000000000000000000" }, { "name": "uaud", "tobin_tax": "1.000000000000000000" }, { "name": "uthb", "tobin_tax": "1.000000000000000000" }, { "name": "usek", "tobin_tax": "1.000000000000000000" }, { "name": "udkk", "tobin_tax": "1.000000000000000000" }, { "name": "unok", "tobin_tax": "1.000000000000000000" }, { "name": "uidr", "tobin_tax": "1.000000000000000000" }, { "name": "uphp", "tobin_tax": "1.000000000000000000" }, { "name": "umyr", "tobin_tax": "1.000000000000000000" }, { "name": "utwd", "tobin_tax": "1.000000000000000000" } ]
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.
Average block time
Preferred signal: context
/cosmos.gov.v1.MsgExecLegacyContent/cosmos.params.v1beta1.ParameterChangeProposalReported response header height: 30753132 · 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.
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.72% decisive Yes
Veto
Not available
0.01% of participation
What this message can change—not a prediction of price.
Original module response evidence unavailable.
Each clock belongs to that module response, before later requests and page assembly. Cached data keeps its original completion time. Missing, invalid, future or ambiguous source evidence withholds the current comparison; unavailable does not mean unchanged.
Matching compares the displayed serialized field values. A current match or difference does not establish historical causation, which proposal last changed a value, an independently verified execution receipt, a paid recipient or delivery. Separately read modules have no common-height guarantee; provider-reported headers do not authenticate the chain state. Truncated or unavailable checks cannot establish a complete proposal-wide parameter match.
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.
Staking ratio
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.