Runtime Upgrade 1300

Altair Governance Proposals
, ,
1

Dear Altair Technical Committee,

The time has come to whitelist the first call on Altair using OpenGov! This will lead to the first OpenGov referendum using the Whitelisted Caller track as well!

Proposal

Whitelist RU v0.13.0 on Altair (currently at v0.12.0) to fix the metadata hash check which blocks Talisman and Ledger App users to sign transactions right now. This will sync Altair and Centrifuge chain to the same versions.

✨ Your Substrate WASM Runtime is ready! ✨
Summary generated with srtool:1.77.0-0.15.0:
 Package     : altair-runtime v0.13.0
 GIT commit  : 3e02647
 GIT tag     : v0.13.0
 GIT branch  : release-v0.13.0
 Rustc       : 1.77.0 (aedd173a2 2024-03-17)
 Time        : 2024-07-05T14:23:52Z

== Compressed
🏋️  Runtime size:             2.122 MB (2,225,017 bytes) ⚠️ HEAVY
🗜  Compressed:               Yes, 79.31%
✨ Reserved meta:            OK - [6D, 65, 74, 61]
🎁 Metadata version:         V14
🔥 Core version:             altair-1300 (altair-1.tx2.au1)
🗳️  Blake2-256 hash:          0x177e577c2315ce48c0efecaadf3969d30aece4a36b55f6d080d707c057bf1765
🗳️  authorizeUpgrade hash:   0xa8459a1869c47769fe10e56cab253b5c1c0312ef73cbd0acb328884b6de80dee
📦 IPFS:                     https://www.ipfs.io/ipfs/QmVcVpz63o2pYCQmr9gB2pPYX3CT8CKZVcpP4TspRYUbUo

Call to action

Members of the Technical Committee (@jeroen, @cdamian @mustermeiszer), please vote on the TC Proposal with id 0 here. This proposal whitelists the call system.authorizeUpgrade(0x177e577c2315ce48c0efecaadf3969d30aece4a36b55f6d080d707c057bf1765) , which is represented by the call hash 0xa8459a1869c47769fe10e56cab253b5c1c0312ef73cbd0acb328884b6de80dee , see image below or release notes or the corresponding preimage as proof for the correct call hash.

image
image1498×632 63.9 KB

What happens afterwards?

Assuming the referendum will be approved in time (deadline Saturday 10:50am CET), we will create a whitelisted caller track referendum to execute the whitelisted call hash 0xa8459a1869c47769fe10e56cab253b5c1c0312ef73cbd0acb328884b6de80dee.

If the referendum is successful, the RU is authorized and can be enacted via system.authorizeUpgrade.

Why not go through the Root track?

Whitelisting has lower thresholds and is faster. We need to unblock Talisman and Ledger App users. Moreover, we verify that whitelisting works as intended with our configuration on a live chain.

cc. @WilliamFreude

2

The proposal was approved/whitelisted by the Technical Committee and has now been submitted via the Whitelisted Caller track (please ignore the two other referenda that were submitted via the Root track).

Referendum 2 is now live for all AIR token holders to vote on.

The total duration of the Decision Period is 3½ days.

:ballot_box: Please vote here: Runtime Upgrade 1300

3

Referendum 2 for Runtime Upgrade 1300 was approved but it didn’t get authorized. The issue was that the WhitelistedCaller origin can only execute calls from the whitelist pallet which is a wrapper for the desired call.

A new referendum was launched again on the Whitelisted Caller track as Referendum 3. This referendum was also approved but did not execute either.

The issue with the last one was that there are two calls for authorizing RUs. The TC whitelisted option 1 while the referendum was voting on option 2. In the end, both have the same outcome but the chain does not know that, it can only compare hashes of calls which differ if they include different methods independent of the result.

Referendum 4 has now been submitted (via Whitelisted Caller track again) to authorize Runtime Upgrade 1300 on Altair - please vote on the referendum again folks.

:ballot_box: Vote on Referendum 4 in the portal here here: Runtime Upgrade 1300

or

:ballot_box: Vote on Referendum 4 on SubSquare: Runtime Upgrade 1300

4

The referendum has passed ( SubSquare | governance platform ) and will be enacted manually.
Thanks, everyone.