#93·Runtime upgrade to 2601: Polkadot SDK stable2603 uplift

30mins ago
0 Comments
Voting

This motion authorizes the enactment of runtime-2601 on Astar mainnet. Astar moves from spec version 2500 to 2601.

It brings the runtime onto the Polkadot SDK and Frontier stable2603 release line, first shipped as runtime-2600; runtime-2601 is a follow-up release on the same line. Runtime-2600 is already live on Shibuya and Shiden.

Preimage: 0xc31cb5b9fc5821076d15808d58ee2638b6367137f537e5fee7fa577aa220f6ea

Full changelog: runtime-2600 release notes and runtime-2601 release notes

Required client version: Astar binary v5.51.2, for collators and archive/RPC nodes

What changes

  • Polkadot SDK and Frontier uplift to stable2603 (#1701). The substance of the release.
  • Session keys require an ownership proof. session.setKeys now needs a valid proof, generated with author_rotateKeysWithOwner (client v5.51.0 and later) using the collator's account as owner. Keys already registered stay valid; this applies to new candidates and key rotations.
  • XCM asset traps cleared. Assets trapped by XCM before the upgrade are deleted and can no longer be claimed.
  • Foreign-asset execution fees go to the treasury instead of being burned and re-minted, so total supply is unchanged.
  • Native WithdrawAsset emits Balances::Withdraw instead of Balances::Burned.
  • EVM fixes and repricing. EXTCODESIZE and EXTCODEHASH return correct values again for contracts without a code-metadata entry (about 72k contracts on Astar and Shiden, returning 0 since runtime-2000). The Ed25519 precompile (0x…0403) now costs a flat 6,000 gas. EIP-7702 delegation writes count toward storage-growth gas. Each EVM execution records 76 more bytes of proof size.
  • Multi-block migration pallets removed (#1693), no longer needed after the runtime-2500 contracts cleanup.

Impact

  • Node operators: collator and archive/RPC nodes must run client v5.51.2 when this runtime is enacted. Older binaries stay consensus-compatible for a short period but cannot generate the session key proofs this runtime requires. v5.51.2 also patches an upstream sync stall. Recommended sidecar: polkadot-rest-api v0.3.3.
  • Anyone with XCM-trapped assets on Astar: claim them with polkadotXcm.claimAssets before enactment; they are deleted afterwards.
  • Indexers: update handlers that rely on Balances::Burned for native WithdrawAsset.
  • User funds in user wallets are unaffected. No action is required from stakers, dApp Staking participants, or holders.

Runtime artifacts (Astar)

  • Spec version 2601, metadata v14, 1678483 bytes
  • Blake2-256: 0x107730659f406f2f6214b8ac4d8a6e61f1a5f18b73b36fcacf66fea4f136eabf
  • SHA256: 0xddf0a2764d89b919e198ac17930c556eb1df7e63f455614ac3483fa0fe4d7303
  • IPFS: QmWRUrEYucUwZgD3fjQh4motQdfHhYq7WVL59NbPmU5pz9

Action requested

Approve enactment of runtime-2601 on Astar mainnet.

Edited
Reply
Up
Share
Only council members can vote, no account found from the council. Still vote
Call
Metadata
Timeline3
Comments