A parchment docket backed by separate chain evidence. Missing vote, deposit, pool, parameter, or tally sources remain unavailable rather than becoming empty or zero.
Proposal status
Failed
PROPOSAL_STATUS_FAILED
Tally evidence
Live response
Independent tally endpoint
Vote records
0
Complete next_key scan · records, not unique voters
Deposit records
0
Complete next_key scan
Voting closes
May 12, 2026, 07:28:44 PM UTC
proposal.voting_end_time
Filed summary
Upgrade dungeon-1 to v6. What changes at the upgrade height: 1. x/globalfee minimum gas price set to 0.01udgn (currently 0 — txs are effectively free, which has been exploited by retry-loop bots and adds noise to validators). Non-exempt txs must attach >= 0.01udgn/gas. 2. Fee-exempt addresses (zero-fee txs allowed) — wired in the v6 binary's ante chain: - Admin / treasury: dungeon13x4pynlp86prhcmtns742kgsgu7pjtzj72eycc - BTC relayer: dungeon1dflpa6dnpkn5ft4tyzkpwdhvz6l7wng06qn665 3. Block time tuned to 1500ms (faster UX for casino + DEX swaps). 4. Dead IBC channel JSON config files removed (cosmetic). Validators MUST swap to the v6 binary at height 14897749 or be halted. Target height assumes ~3 day voting period + ~1 day buffer for binary distribution at current ~1.08s/block. Binary release: github.com/Crypto-Dungeon/dungeonchain/releases (will be tagged v6.0.0 once this proposal passes). Build from main HEAD or use the published binary. This upgrade does NOT change SDK or wasmd versions — those are deferred to a future v7 ceremony alongside Alliance module + bulk-memory wasm capability.
Tally source
Yes
99.99%
203.7M DGN
No
0.00%
0 DGN
Abstain
0.00%
1 DGN
No with veto
0.00%
0 DGN
Shares use the exact integer tally total as denominator. Display percentages are truncated to two decimals; threshold decisions use integer cross-multiplication, not floating-point values.
Quorum
51.98% turnout
33.40% required
203.7M / 391.9M DGN
Approval threshold
100.00% yes
>50.00% required
Yes divided by Yes + No + NoWithVeto; abstain is excluded.
Veto threshold
0.00% veto
≤33.40% required to avoid veto
NoWithVeto divided by all tallied voting power.
Proposal timestamps
Submitted
Returned timestampMay 9, 2026, 07:28:44 PM UTC
proposal.submit_time
Deposit period ends
Returned timestampMay 12, 2026, 07:28:44 PM UTC
proposal.deposit_end_time
Voting begins
Returned timestampMay 9, 2026, 07:28:44 PM UTC
proposal.voting_start_time
Voting ends
Returned timestampMay 12, 2026, 07:28:44 PM UTC
proposal.voting_end_time
These are proposal response fields, not independently observed chain events. An unset zero-time remains explicitly not set.
Independent source register
| Evidence | Endpoint | Coverage | State |
|---|---|---|---|
| Live tally | /cosmos/gov/v1/proposals/:id/tally | Exact integer tally fields returned | Available |
| Vote records | /cosmos/gov/v1/proposals/:id/votes | 0 records after following next_key to completion | Available |
| Deposit records | /cosmos/gov/v1/proposals/:id/deposits | 0 records after following next_key to completion | Available |
| Staking pool | /cosmos/staking/v1beta1/pool | bonded_tokens available for turnout denominator | Available |
| Tally parameters | /cosmos/gov/v1/params/tallying | effective regular threshold 0.500000000000000000 · quorum 0.334000000000000000 · veto 0.334000000000000000 | Available |
Wallet action
The voting control is enabled only by its existing wallet and proposal-status rules. The evidence panels above do not sign or broadcast transactions.
Executable payload
{
"@type": "/cosmos.upgrade.v1beta1.MsgSoftwareUpgrade",
"authority": "dungeon10d07y265gmmuvt4z0w9aw880jnsr700j53vrug",
"plan": {
"name": "v6",
"time": "1970-01-01T00:00:00Z",
"height": "14897749",
"info": "Source: github.com/Crypto-Dungeon/dungeonchain (branch upgrade/v6, merged to main). Binary: dungeond v6 — see release notes for sha256.",
"upgraded_client_state": null
}
}Proposal response
Exhaustively paginated response
Valid empty vote scan
The vote helper followed next_key to completion and returned zero current vote records.
0 vote records after following next_key to exhaustion. “Vote records” is used deliberately; this is not relabeled as a unique-voter count.
Exhaustively paginated response
Valid empty deposit response
The deposit endpoint answered with zero rows. This is distinct from the proposal's own total_deposit field above.
0 deposit records after following next_key to exhaustion.