Referendum #32 · whitelisted caller · fact-checked

Failed late replay of the runtime-1500 upgrade proposal

Original title: [Whitelisted Caller] Referendum #32: Runtime Upgrade v1500

Governance: Executed · Dispatch failed

Submitted 2024-08-22T13:56:45.000Z · 2026-01-31T15:32:42.000Z

Verification date in this record: 2026-10-14. This is not a live chain status check.

What this referendum means

What was proposed?

This referendum reused the exact proposal hash from the successful runtime-1500 upgrade, but its much later dispatch failed and made no runtime change.

Why it mattered

It is a sharp example of why proposal identity and lifecycle status must be read alongside dispatch results and chronology.

An Aye vote meant…

An Aye vote supported attempting to dispatch the reused runtime-1500 proposal.

A Nay vote meant…

A Nay vote opposed that dispatch.

What happened or is happening

Its proposal hash is identical to #33, which successfully changed specVersion 1421 to 1500 on August 28, 2024. The archive does not infer the later failure's named error from its numeric module code.

The referendum reached the Executed lifecycle state on January 31, 2026, but returned module error 21/0x03000000. No runtime transition occurred.

Attempt to dispatch the same whitelisted runtime-upgrade proposal that referendum #33 had successfully used for spec version 1500.

No runtime deployment occurred through this referendum.

Observable on-chain result

Dispatch returned an error.

{"module":{"index":21,"error":"0x03000000"}}

Promised outcomes

  • Dispatch the reused runtime-1500 upgrade proposal.

Verified outcomes

  • The dispatch failed and did not change the runtime.
  • The same proposal hash had already succeeded as #33 in 2024.

Follow-up: contradicted

  • Outcome is tied to the dispatch result and verified runtime state, not the lifecycle label alone.

Still unknown

  • The module error has not yet been mapped to a verified human-readable error name.
Further explanation and reporting

No additional reporting has been published for this referendum.

Details and evidence

Participation

Participation

Calculation status: complete. Address-level figures are not counts of distinct people or organizations.

  • Individual vote rows reconcile to the aggregate capital total. Concentration treats delegated capital as controlled by the account casting the direct vote.
Direct addresses34
Delegating addresses0
Raw capital (VARA)1931531524
Weighted Aye power (VARA)193153214.5
Weighted Nay power (VARA)0
Approval (%)100
Raw capital / captured electorate (%)19.31531577
Support capital (VARA)1931531524
Top-one share (%)7.97523
Top-three share (%)23.92569
HHI (0–10,000)494.98424
Gini (0–1)0.42983034
Proposal history

Proposal history

ReferendumGovernanceExecutionDirect addresses
#33 Upgrade the Vara runtime from spec 1421 to 1500

This referendum upgraded the live Vara runtime from specification version 1421 to 1500.

ExecutedDispatch succeeded40
Timeline

Timeline

  1. Submitted · 2024-08-22T13:56:45.000Z · block 14897369
  2. DecisionDepositPlaced · 2024-08-22T13:56:57.000Z · block 14897373
  3. DecisionStarted · 2024-08-22T14:26:45.000Z · block 14897969
  4. ConfirmStarted · 2024-08-26T12:55:36.001Z · block 15011344
  5. Confirmed · 2024-08-26T13:05:36.000Z · block 15011544
  6. Executed · 2026-01-31T15:32:42.000Z · block 30022144
Technical call tree

Technical call tree

Its proposal hash is identical to #33, which successfully changed specVersion 1421 to 1500 on August 28, 2024. The archive does not infer the later failure's named error from its numeric module code.

{
  "call": {
    "callIndex": "0x1503",
    "section": "whitelist",
    "method": "dispatchWhitelistedCallWithPreimage"
  },
  "nestedCalls": [
    {
      "depth": 0,
      "callIndex": "0x1503",
      "section": "whitelist",
      "method": "dispatchWhitelistedCallWithPreimage"
    }
  ],
  "limitations": []
}
Historical track parameters

Historical track parameters

{
  "maxDeciding": 100,
  "preparePeriodBlocks": 600,
  "decisionPeriodBlocks": 403200,
  "confirmationPeriodBlocks": 200,
  "minimumEnactmentBlocks": 200,
  "decisionDeposit": {
    "planck": "100000000000000000",
    "vara": "100000"
  },
  "approvalCurve": {
    "reciprocal": {
      "factor": 270899180,
      "xOffset": 389830523,
      "yOffset": 305084738
    }
  },
  "supportCurve": {
    "reciprocal": {
      "factor": 8650766,
      "xOffset": 18867926,
      "yOffset": 41509433
    }
  }
}
Deposits

Deposits

Governance deposits are not proposal spending.

{
  "submission": {
    "depositor": "kGgQqLXhVVMv85XDy1v5AE6HVBG1tkAwURrdmq1ewbmGMCaGH",
    "amount": {
      "planck": "100000000000000",
      "vara": "100"
    }
  },
  "decision": {
    "depositor": "kGhAjUA3Uke6UmWwMRRwFHuxisCgm7dab61sL1tKqA15NXQVX",
    "amount": {
      "planck": "100000000000000000",
      "vara": "100000"
    }
  },
  "outcome": "unknown"
}
Sources

Sources

  • subsquare · retrieved 2026-10-14T00:46:33.897Z · block 14897369

    Public server-rendered page data captured before editorial translation.

  • subsquare · retrieved 2026-10-14T00:56:36.175Z

    Public final vote rows used for voter counts, conviction values, delegation aggregates, and concentration calculations.

Corrections

Corrections

No corrections recorded.

Learn the terms

OpenGov · Referendum · Proposal · Preimage · Proposal hash · Runtime call