paritytech/polkadot-sdk polkadot-stable2606-2

Polkadot stable2606-2

on GitHub

This release contains the changes from polkadot-stable2606-1 to polkadot-stable2606-2.

ℹ️ Please note: this is a patch release for the latest stable version stable2606. If your nodes are already running on this stable release, you should upgrade to this patch version to get the latest fixes.

Once published, polkadot-stable2606-2 will also be tagged as polkadot-v1.24.2; the node version for this release is v1.24.2.
The following crates were updated to the corresponding versions:

ℹ️ Due to the decommissioning of the Debian bullseye build, starting from the next stable release (stable2609), all published binaries will be built on the Debian bookworm distribution. More instructions to follow on the forum — please keep an eye out.

📦 The complete changelog with full descriptions is attached to this release as CHANGELOG.md, and in machine-readable form as changelog.json.

💥 Breaking Changes

7 changes are breaking according to Rust SemVer (each bumps the major version of at least one crate). Details in the 💥-marked entries below.

• XCM: #12378 pallet-assets: allow force_create to set an arbitrary asset id when auto-increment is enabled (pallet-assets)
• Staking & Elections: #11979 Scale validator self-stake incentive by era-points performance (pallet-staking-async)
• Coretime: #12750 [pallet-broker] Prevent auto-renewal from renewing another task's workload (pallet-broker)
• Assets: #12245 pallet-psm: multi-instance, permissionless Peg Stability Modules (pallet-psm, asset-hub-westend-runtime)
• Node: #12315 feat(webrtc): add experimental WebRTC transport to litep2p backend (sc-cli, sc-network, sc-network-types)
• Node: #12870 network: Enable WebRTC by default on full nodes (sc-cli, sc-network, sc-network-types)
• FRAME & Runtime: #13153 pallet-accumulate-and-forward: measure the transfer period from the last forward (emulated-integration-tests-common)

Changelog

XCM

🛠️ Runtime Dev

💥 #12378: pallet-assets: allow force_create to set an arbitrary asset id when auto-increment is enabled

force_create no longer requires the asset id to equal NextAssetId: a ForceOrigin may create an asset with any id not currently in use, and the id is then marked as allocated so it can never later collide. Asset id allocation is now configured explicitly via the new Config::AssetIdAllocator (AutoIncAssetId for auto-incrementing ids, () for none), replacing the implicit NextAssetId-is-Some plus AutoIncAssetId callback mechanism. Only the force_create call is relaxed; fungibles::Create::create is not gated on ForceOrigin and still requires the id the allocator dictates. …

Breaking: pallet-assets
_{Other crates: asset-hub-rococo-runtime (minor), asset-hub-westend-runtime (minor), penpal-runtime (patch), pallet-contracts-mock-network (minor), pallet-asset-conversion (none), pallet-asset-conversion-tx-payment (none) and 7 more}

#12832: pallet-xcm: weight asset claiming and precompile XCM input by their real size

Fixes weights and benchmark worst cases for the claim_assets extrinsic, the ClaimAsset and AliasOrigin instructions, and the pallet-revive XCM precompile. Each was benchmarked with an input far cheaper than one a caller can actually supply, so all four under-charged.

What this needs from you: …

_{Crates: pallet-xcm (minor), staging-xcm (minor), staging-xcm-builder (patch), staging-xcm-executor (patch), polkadot-runtime-parachains (patch), pallet-xcm-precompiles (patch) and 13 more}

Smart Contracts (Revive)

🛠️ Runtime Dev

#12281: [pallet-revive] Implement originIsRoot precompile method

We have the callerIsRoot API but this doesn't work with nested calls. originIsRoot fills this gap.

_{Crates: pallet-revive-fixtures (minor), pallet-revive (minor), pallet-revive-uapi (minor), asset-hub-westend-runtime (minor)}

#12726: Probe cargo for -Z json-target-spec support instead of guessing from the version

Both PolkaVM build paths compile against a .json target spec produced by polkavm-linker and have to decide whether to pass cargo -Z json-target-spec: newer cargo requires the flag, older cargo rejects it as unknown.

Both decided by comparing a version against 1.95: the fixture builder against the rustc version, wasm-builder against the cargo version. Neither works. The flag landed partway through the 1.95 cycle, so a nightly from early in that cycle reports 1.95 from both binaries while its cargo does not know the flag yet, and the fixture build fails with error: unknown -Z flag specified: json-target-spec. …

_{Crates: pallet-revive-fixtures (patch), substrate-wasm-builder (patch)}

#13092: Re-export WeightInfo from the assets and vesting precompile crates

pallet-assets-precompiles and pallet-vesting-precompiles now re-export their WeightInfo trait at the crate root like every other pallet, so weight files generated by frame-omni-bencher's default template (<crate>::WeightInfo) compile without hand edits. Asset Hub Westend now uses generated weight files for both.

_{Crates: pallet-assets-precompiles (minor), pallet-vesting-precompiles (minor), asset-hub-westend-runtime (patch)}

Staking & Elections

🛠️ Runtime Dev

💥 #11979: Scale validator self-stake incentive by era-points performance

Validator self-stake incentive payout is now distributed proportionally across elected validators using the weighted-points share share_i = (w_i · ep_i) / Σ_j(w_j · ep_j), where w_j is each validator's per-era incentive weight and ep_j is their era points.

The denominator is maintained incrementally in ErasSumWeightedPoints as session reports credit era points, avoiding a full validator iteration at payout time. Validators with zero era points or no incentive weight receive nothing, and non-zero weighted performers share the era budget subject to normal rounding. …

Breaking: pallet-staking-async
_{Other crates: asset-hub-westend-runtime (patch)}

Coretime

👤 Runtime User

💥 #12750: [pallet-broker] Prevent auto-renewal from renewing another task's workload

enable_auto_renew previously renewed whatever renewable workload was found on the given core index without checking that it belongs to the given task. Since a core index can be assigned a different workload each bulk period, a task could end up paying to renew a completely unrelated task's workload, and the stored auto-renewal record would keep charging it every sale. …

Breaking: pallet-broker
_{Other crates: coretime-westend-runtime (patch)}

Assets

🛠️ Runtime Dev

💥 #12245: pallet-psm: multi-instance, permissionless Peg Stability Modules

Reworks pallet-psm from a single, governance-seeded Peg Stability Module into a multi-instance design where many PSMs coexist, each created permissionlessly and managed by its own admins. …

Breaking: pallet-psm, asset-hub-westend-runtime
_{Other crates: sc-consensus-beefy-rpc (patch)}

#12811: pallet-psm: report the real instance footprint to the creation Consideration

create_psm previously established the creation Consideration with a placeholder footprint of one item and zero bytes, under-reporting what the call actually writes. A new Pallet::psm_creation_footprint helper now reports the Psm and PsmAdmin entries (two items, max-encoded-len sized) and is used by the extrinsic and the benchmarks.

_{Crates: pallet-psm (minor)}

#13059: Add is_sufficient to the fungibles::Inspect trait

Adds an is_sufficient method to the fungibles::Inspect trait, reporting whether an asset is sufficient. The method has a default implementation returning false, so the change is non-breaking; however, implementations which track sufficiency should override it. It is implemented for pallet-assets (reading the asset's is_sufficient flag, and forwarded by the pallet-assets-freezer and pallet-assets-holder wrappers) and forwarded through fungibles::UnionOf and the right branch of fungible::UnionOf. The left (fungible) branch of fungible::UnionOf reports false, as the fungible trait family carries no sufficiency information.

_{Crates: frame-support (minor), pallet-assets (minor), pallet-assets-freezer (minor), pallet-assets-holder (minor)}

#13062: pallet-psm: use recorded decimals when minting

Keeps PSM mint conversions and external-asset registration tied to the decimal snapshots captured when the PSM and external asset are registered, matching redemption behavior. Changes to live asset metadata no longer stop minting or alter the debt conversion rate.

_{Crates: pallet-psm (patch)}

Parachains (protocol)

🛠️ Runtime Dev

#12844: paras: skip undersized parachain heads in sorted_para_heads

Paras::sorted_para_heads() now skips parachain heads shorter than MIN_PARA_HEAD_LEN (64 bytes). Encoded parachain headers are well above this bound, so no real parachain is affected.

_{Crates: polkadot-runtime-parachains (minor)}

Node

🔧 Node Dev

💥 #12315: feat(webrtc): add experimental WebRTC transport to litep2p backend

Description

Add webrtc-direct support to the litep2p backend

• webrtc-direct support gated behind a new --experimental-webrtc CLI flag.
• WebRTC listen_addr entries are skipped with a warning unless enabled.
• Persist the DTLS certificate to <net_config_path>/webrtc_certificate so the node keeps a stable identity across restarts. Fall back to an ephemeral cert otherwise.
• update network type to support WebRTCDirect

Integration

No behavioral change unless --experimental-webrtc is explicitly enabled. …

Breaking: sc-cli, sc-network, sc-network-types

💥 #12870: network: Enable WebRTC by default on full nodes

_{Also for Node Operator}

Accept WebRTC connections on the same UDP --port as used for TCP/WS connections. Enabled by default on full nodes, can be force-enabled on validators & collators with --force-enable-webrtc, or disabled by passing an explicit --listen-addr without WebRTC addresses. Only supported with litep2p network backend. …

Breaking: sc-cli, sc-network, sc-network-types
_{Other crates: sc-service (patch), polkadot-omni-node-lib (patch)}

#12582: collator-protocol-revamp: additional metrics

Improves the observability of the collator protocol revamp by adding/improving some metrics.

_{Crates: polkadot-collator-protocol (minor)}

#12693: sc-network: derive the WebRTC DTLS certificate from the node key

Derive the WebRTC DTLS certificate deterministically from the node's Ed25519 secret key instead of persisting it to a separate file on disk.

_{Crates: sc-network (minor)}

#13098: security: Bump litep2p to 0.15.2 to fix panic in WebRTC

_{Also for Node Operator}

litep2p 0.15.2 fixes a panic in the WebRTC transport that could be triggered remotely by sending oversized UDP datagrams to a WebRTC endpoint.

Only nodes with the WebRTC transport enabled are affected. Operators of such nodes are advised to upgrade.

See the litep2p v0.15.2 release notes for details.

_{Crates: sc-network (patch), sc-network-types (patch)}

🖥️ Node Operator

#12662: sc-hop: add Prometheus metrics

Adds Prometheus metrics to sc-hop: …

_{Crates: sc-hop (minor), polkadot-omni-node-lib (patch)}

#12812: beefy: lower peer reputation for bad responses

Bad BEEFY justifications are refused and also the sending peer penalized.

_{Crates: sc-consensus-beefy (patch)}

#13045: sc-rpc-server: bound the cardinality of the RPC metrics method label

The substrate_rpc_calls_* metrics used the requested method name as the method label without restricting it to registered methods, so the label could take an unbounded number of values. The label is now bounded to the registered method set; any other name is recorded as unknown, keeping the series count finite.

RpcMetrics::with_known_methods sets the allowlist and the RPC server wires it at start; a metrics instance without it keeps the previous behaviour.

_{Crates: sc-rpc-server (minor)}

FRAME & Runtime

🛠️ Runtime Dev

💥 #13153: pallet-accumulate-and-forward: measure the transfer period from the last forward

on_idle only forwarded when the block number of the configured BlockNumberProvider was an exact multiple of TransferPeriod. A chain that does not observe every block of its provider, e.g. a parachain using RelaychainDataProvider, can miss those blocks indefinitely.

The pallet now records the block of the last forwarding attempt in the new LastForwardBlock storage item and forwards once TransferPeriod blocks have elapsed since then, whatever the block cadence. No migration is needed: an empty LastForwardBlock means "never forwarded", so after upgrade the first block with enough funds forwards immediately.

Breaking: emulated-integration-tests-common
_{Other crates: pallet-accumulate-and-forward (minor)}

#12440: Fix for rust-lld regression

Adapts the #[runtime_interface] macro to a rust-lld regression observed since Rust 1.96.0, which requires the Wasm module that external functions are imported from to be specified explicitly. The generated extern "C" blocks now carry #[link(wasm_import_module = "env")] when compiling for wasm32.

_{Crates: sp-runtime-interface-proc-macro (patch)}

Rust compiler versions

The crates and node binaries in this release were built and tested with the following rustc toolchain; other versions may work.

• Rust Stable: 1.93.0

Docker images

The docker images for the binaries of this release can be found on Docker Hub (available a few minutes after the release has been published), all tagged with stable2606-2:

• polkadot
• polkadot-parachain
• polkadot-omni-node
• chain-spec-builder
• eth-rpc

You may also pull them with:

docker pull parity/polkadot:stable2606-2
docker pull parity/polkadot-parachain:stable2606-2
docker pull parity/polkadot-omni-node:stable2606-2
docker pull parity/chain-spec-builder:stable2606-2
docker pull parity/eth-rpc:stable2606-2