Releases: paritytech/polkadot-sdk
Polkadot polkadot-stable2506-2
This release contains the changes from polkadot-stable2506-1 to polkadot-stable2506-2.
ℹ️ Please note:
This is a patch release for the latest stable version: stable2506. If your nodes are already running on this version, you can consider upgrading to it to have the latest fixes.
The tag corresponding to the current patch release polkadot-stable2506-2 and matching the old pattern will be available under polkadot-v1.19.2.
The following crates were updated to the corresponding versions:
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
Changelog
Changelog for Runtime Dev
ℹ️ These changes are relevant to: All of those who rely on the runtime. A parachain team that is using a pallet. A DApp that is using a pallet. These are people who care about the protocol (WASM, not the meta-protocol (client).)
[#9516]: Fix for promote_fast benchmark
Fixed benchmark generation/compilation for promote_fast MaxRank change from u32 to u16.
[#9451]: Call SingleBlockMigrations from frame_system::Config on try_on_runtime_upgrade.
Fixes a small bug in try-runtime code, where SingleBlockMigrations from frame_system::Config was not called in try_on_runtime_upgrade.
[#9544]: Disable reserve_transfer_assets for DOT|KSM|WND|PAS
The reserve_transfer_assets extrinsic on pallet-xcm is also affected by the same issue as transfer_assets.
These extrinsics have been updated to return an error when dealing with DOT|KSM|WND|PAS, effectively disabling them.
We can't afford these extrinsics to be enabled after the Asset Hub Migration (AHM) and risk trapping assets due to chain misconfigurations.
All chains need to update and coordinate with their dapps to move to the alternatives, like transfer_assets_using_type_and_then
or execute.
[#9564]: Fix disabled validator filtering in the parachains runtime
Correctly map group indices to vote indices when filtering backing statements.
[#9514]: Paras: Clean up AuthorizedCodeHash when offboarding
This PR updates the Paras pallet to clear entries in AuthorizedCodeHash as part of the offboarding process.
Changelog for Node Operator
ℹ️ These changes are relevant to: Those who don't write any code and only run code.
[#9581]: fix: parachain informant
The parachain informant was logging information for all parachains, not just ours. This PR fixes that by filtering the events by parachain ID.
Changelog for Runtime User
ℹ️ These changes are relevant to: Anyone using the runtime. This can be a token holder or a dev writing a front end for a chain.
[#9544]: Disable reserve_transfer_assets for DOT|KSM|WND|PAS
The reserve_transfer_assets extrinsic on pallet-xcm is also affected by the same issue as transfer_assets.
These extrinsics have been updated to return an error when dealing with DOT|KSM|WND|PAS, effectively disabling them.
We can't afford these extrinsics to be enabled after the Asset Hub Migration (AHM) and risk trapping assets due to chain misconfigurations.
All apps should switch to transfer_assets_using_type_and_then or execute.
Rust compiler versions
This release was built and tested against the following versions of rustc.
Other versions may work.
- Rust Stable:
1.84.1
Docker images
The docker images for the polkadot node binary and the polkadot-parachain binary can be found at Docker hub (will be available a few minutes after the release has been published):
You may also pull it with:
docker pull parity/polkadot:stable2506-2
or
docker pull parity/polkadot-parachain:stable2506-2
Polkadot stable2503-9
This release contains the changes from polkadot-stable2503-8 to polkadot-stable2503-9.
ℹ️ Please note:
stable2503 and contains only patches and fixes to the crates (list below). No binary or docker images will be provided for this release.
The tag corresponding to the current patch release polkadot-stable2503-9 and matching the old pattern will be available under polkadot-v1.18.9.
The following crates were updated to the corresponding versions:
Changelog
Changelog for Node Dev
ℹ️ These changes are relevant to: Those who build around the client side code. Alternative client builders, SMOLDOT, those who consume RPCs. These are people who are oblivious to the runtime changes. They only care about the meta-protocol, not the protocol itself.
Changelog for Runtime Dev
ℹ️ These changes are relevant to: All of those who rely on the runtime. A parachain team that is using a pallet. A DApp that is using a pallet. These are people who care about the protocol (WASM, not the meta-protocol (client).)
[#9445]: pallet-xcm: fix authorized_alias benchmarks
Depending on runtime configuration of ED and storage deposits, the old benchmark code did not set up enough funds to cover authorized aliases storage deposits. Fix it by adding more funds as part of benchmark setup.
[#9564]: Fix disabled validator filtering in the parachains runtime
Correctly map group indices to vote indices when filtering backing statements.
Rust compiler versions
This release was built and tested against the following versions of rustc.
Other versions may work.
- Rust Stable:
1.84.1
Polkadot stable2412-9
This release contains the changes from polkadot-stable2412-8 to polkadot-stable2412-9.
ℹ️ Please note:
stable2412 and contains only patches and fixes to the crates (list below). No binary or docker images will be provided for this release.
The tag corresponding to the current patch release polkadot-stable2412-9 and matching the old pattern will be available under polkadot-v1.17.9.
The following crates were updated to the corresponding versions:
Changelog
Changelog for Node Dev
ℹ️ These changes are relevant to: Those who build around the client side code. Alternative client builders, SMOLDOT, those who consume RPCs. These are people who are oblivious to the runtime changes. They only care about the meta-protocol, not the protocol itself.
[#9355]: substrate-prometheus-endpoint: directly require the feature "tokio/net"
The crate substrate-prometheus-endpoint use tokio items given by the feature "net" but it doesn't explictly requires it in the Cargo.toml. It compiles on master because hyper-util enables the feature "tokio/net". But upgrading hyper-util break this indirect enabling.
This fix the issue by directly setting "net" feature as required, as it is used.
We should also backport this ideally. It is not a breaking change given the code doesn't compile without the feature and only compiles if indirectly enabled by another crate.
Changelog for Runtime Dev
ℹ️ These changes are relevant to: All of those who rely on the runtime. A parachain team that is using a pallet. A DApp that is using a pallet. These are people who care about the protocol (WASM, not the meta-protocol (client).)
[#9354]: Remove whitespaces added by macros due to token re-parsing
Normalize result of stringify in scenarios when used inside nested macros to stringify token streams for benchmarking framework
[#9195]: XCMv5 asset exchange test scenarios
Emulated test scenarios added to cover asset exchanging via Transact or ExchangeAsset instruction using XCMv5 capabilities
Rust compiler versions
This release was built and tested against the following versions of rustc.
Other versions may work.
- Rust Stable:
1.81.0
Polkadot polkadot-stable2506-1
This release contains the changes from polkadot-stable2506 to polkadot-stable2506-1.
ℹ️ Please note:
This is a patch release for the latest stable version: stable2506. If your nodes are already running on this version, you can consider upgrading to it to have the latest fixes.
The tag corresponding to the current patch release polkadot-stable2506-1 and matching the old pattern will be available under polkadot-v1.19.1.
Changelog
Changelog for Node Dev
ℹ️ These changes are relevant to: Those who build around the client side code. Alternative client builders, SMOLDOT, those who consume RPCs. These are people who are oblivious to the runtime changes. They only care about the meta-protocol, not the protocol itself.
[#9338]: fatxpool: instant seal support
This PR introduces creation of view for known best block during instantiation of fatxpool. This is intended to fix an instant-seal nodes, where block building is triggered via transaction import.
[#9355]: substrate-prometheus-endpoint: directly require the feature "tokio/net"
The crate substrate-prometheus-endpoint use tokio items given by the feature "net" but it doesn't explictly requires it in the Cargo.toml. It compiles on master because hyper-util enables the feature "tokio/net". But upgrading hyper-util break this indirect enabling.
This fix the issue by directly setting "net" feature as required, as it is used.
We should also backport this ideally. It is not a breaking change given the code doesn't compile without the feature and only compiles if indirectly enabled by another crate.
[#9189]: fatxpool: avoid premature revalidation of transactions
After this PR transactions will be revalidated in mempool on finalized blocks only if height of finalized block is greater then the height of the block at which transactions was originally submitted.
[#9281]: litep2p/discovery: Ensure non-global addresses are not reported as external
This PR ensures that external addresses discovered by the identify protocol are not propagated to the litep2p backend if they are not global. This leads to a healthier DHT over time, since nodes will not advertise loopback / non-global addresses.
We have seen various cases were loopback addresses were reported as external:
2025-07-16 16:18:39.765 TRACE tokio-runtime-worker sub-libp2p::discovery: verify new external address: /ip4/127.0.0.1/tcp/30310/p2p/12D3KooWNw19ScMjzNGLnYYLQxWcM9EK9VYPbCq241araUGgbdLM
2025-07-16 16:18:39.765 INFO tokio-runtime-worker sub-libp2p: 🔍 Discovered new external address for our node: /ip4/127.0.0.1/tcp/30310/p2p/12D3KooWNw19ScMjzNGLnYYLQxWcM9EK9VYPbCq241araUGgbdLM
This PR takes into account the network config for allow_non_global_addresses.
Closes: #9261
Changelog for Runtime Dev
ℹ️ These changes are relevant to: All of those who rely on the runtime. A parachain team that is using a pallet. A DApp that is using a pallet. These are people who care about the protocol (WASM, not the meta-protocol (client).)
[#9354]: Remove whitespaces added by macros due to token re-parsing
Normalize result of stringify in scenarios when used inside nested macros to stringify token streams for benchmarking framework
[#9489]: Remove free balance check in prepare_unlock
The free balance check during unlocking is unnecessary since a lock can cover both free and reserved balances. Removing it allows locks to be cleared even if part of the locked funds is reserved or already slashed.
[#9179]: Fix subsume_assets incorrectly merging two AssetsInHolding
Fix subsume_assets incorrectly merging two AssetsInHolding instances under certain conditions, which caused asset values to be overridden rather than summed.
[#8857]: [FRAME] Custom log level for the runtime benchmarks
Changes:
- Add
--runtime-logoption to omni-bencher CLI - Read env var
RUNTIME_LOGas fallback to the--runtime-logoption - Set custom log level for runtime benchmarks that can be different form CLI level
- Fix issue where old runtimes have a space in the pallet or instance name from breaking change in
quotemacro
[#9445]: pallet-xcm: fix authorized_alias benchmarks
Depending on runtime configuration of ED and storage deposits, the old benchmark code did not set up enough funds to cover authorized aliases storage deposits. Fix it by adding more funds as part of benchmark setup.
[#9250]: implement InspectMessageQueues for UnpaidRemoteExporter
Add missing implementation of InspectMessageQueues for UnpaidRemoteExporter
[#9195]: XCMv5 asset exchange test scenarios
Emulated test scenarios added to cover asset exchanging via Transact or ExchangeAsset instruction using XCMv5 capabilities
Changelog for Node Operator
ℹ️ These changes are relevant to: Those who don't write any code and only run code.
[#8838]: fatxpool: fork aware transaction pool is now default
This PR changes the default transaction pool to the fork aware implementation. The old implementation can be still used with --pool-type=single-state command line argument.
Changelog for Runtime User
ℹ️ These changes are relevant to: Anyone using the runtime. This can be a token holder or a dev writing a front end for a chain.
Rust compiler versions
This release was built and tested against the following versions of rustc.
Other versions may work.
- Rust Stable:
1.84.1
Docker images
The docker images for the polkadot node binary and the polkadot-parachain binary can be found at Docker hub (will be available a few minutes after the release has been published):
You may also pull it with:
docker pull parity/polkadot:stable2506-1
or
docker pull parity/polkadot-parachain:stable2506-1
Polkadot stable2409-11
7f3e151
EgorPopelyaev
Egor_P
This release contains the changes from polkadot-stable2409-10 to polkadot-stable2409-11.
ℹ️ Please note:
stable2409 and contains only patches and fixes to the crates (list below). No binary or docker images will be provided for this release.
The tag corresponding to the current patch release polkadot-stable2409-11 and matching the old pattern will be available under polkadot-v1.16.11.
The following crates were updated to the corresponding versions:
Changelog
Changelog for Node Dev
ℹ️ These changes are relevant to: Those who build around the client side code. Alternative client builders, SMOLDOT, those who consume RPCs. These are people who are oblivious to the runtime changes. They only care about the meta-protocol, not the protocol itself.
[#9355]: substrate-prometheus-endpoint: directly require the feature "tokio/net"
The crate substrate-prometheus-endpoint use tokio items given by the feature "net" but it doesn't explictly requires it in the Cargo.toml. It compiles on master because hyper-util enables the feature "tokio/net". But upgrading hyper-util break this indirect enabling.
This fix the issue by directly setting "net" feature as required, as it is used.
We should also backport this ideally. It is not a breaking change given the code doesn't compile without the feature and only compiles if indirectly enabled by another crate.
Changelog for Runtime Dev
ℹ️ These changes are relevant to: All of those who rely on the runtime. A parachain team that is using a pallet. A DApp that is using a pallet. These are people who care about the protocol (WASM, not the meta-protocol (client).)
[#9179]: Fix subsume_assets incorrectly merging two AssetsInHolding
Fix subsume_assets incorrectly merging two AssetsInHolding instances under certain conditions,
which caused asset values to be overridden rather than summed.
[#9354]: Remove whitespaces added by macros due to token re-parsing
Normalize result of stringify in scenarios when used inside nested macros to stringify token streams for benchmarking framework
Rust compiler versions
This release was built and tested against the following versions of rustc.
Other versions may work.
- Rust Stable:
"1.81.0"
Polkadot stable2503-8
This release contains the changes from polkadot-stable2503-7 to polkadot-stable2503-8.
ℹ️ Please note:
stable2503 and contains only patches and fixes to the crates (list below). No binary or docker images will be provided for this release.
The tag corresponding to the current patch release polkadot-stable2503-8 and matching the old pattern will be available under polkadot-v1.18.8.
The following crates were updated to the corresponding versions:
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
Changelog
Changelog for Node Dev
ℹ️ These changes are relevant to: Those who build around the client side code. Alternative client builders, SMOLDOT, those who consume RPCs. These are people who are oblivious to the runtime changes. They only care about the meta-protocol, not the protocol itself.
[#9355]: substrate-prometheus-endpoint: directly require the feature "tokio/net"
The crate substrate-prometheus-endpoint use tokio items given by the feature "net" but it doesn't explictly requires it in the Cargo.toml. It compiles on master because hyper-util enables the feature "tokio/net". But upgrading hyper-util break this indirect enabling.
This fix the issue by directly setting "net" feature as required, as it is used.
We should also backport this ideally. It is not a breaking change given the code doesn't compile without the feature and only compiles if indirectly enabled by another crate.
[#9281]: litep2p/discovery: Ensure non-global addresses are not reported as external
This PR ensures that external addresses discovered by the identify protocol are not propagated to the litep2p backend if they are not global. This leads to a healthier DHT over time, since nodes will not advertise loopback / non-global addresses.
We have seen various cases were loopback addresses were reported as external:
2025-07-16 16:18:39.765 TRACE tokio-runtime-worker sub-libp2p::discovery: verify new external address: /ip4/127.0.0.1/tcp/30310/p2p/12D3KooWNw19ScMjzNGLnYYLQxWcM9EK9VYPbCq241araUGgbdLM
2025-07-16 16:18:39.765 INFO tokio-runtime-worker sub-libp2p: 🔍 Discovered new external address for our node: /ip4/127.0.0.1/tcp/30310/p2p/12D3KooWNw19ScMjzNGLnYYLQxWcM9EK9VYPbCq241araUGgbdLM
This PR takes into account the network config for allow_non_global_addresses.
Closes: #9261
cc @paritytech/networking
[#9094]: bitfield_distribution: fix subsystem clogged at begining of a session
handle_peer_view_change gets called on NewGossipTopology with the existing view of the peer to cover for the case when the topology might arrive late, but in that case in the view will contain old blocks from previous session, so since the X/Y neighbour change because of the topology change you end up sending a lot of messages for blocks before the session changed.
Fix it by checking the send message only for relay chains that are in the same session as the current topology.
[#9264]: gossip-support: make low connectivity message an error
All is not well when a validator is not properly connected, e.g: of things that might happen:
- Finality might be slightly delay because validator will be no-show because they can't retrieve PoVs to validate approval work: #8915.
- When they author blocks they won't back things because gossiping of backing statements happen using the grid topology:, e.g blocks authored by validators with a low number of peers:
https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc-polkadot.helixstreet.io#/explorer/query/26931262
https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc-polkadot.helixstreet.io#/explorer/query/26931260
https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fpolkadot.api.onfinality.io%2Fpublic-ws#/explorer/query/26931334
https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fpolkadot-public-rpc.blockops.network%2Fws#/explorer/query/26931314
https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fpolkadot-public-rpc.blockops.network%2Fws#/explorer/query/26931292
https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fpolkadot-public-rpc.blockops.network%2Fws#/explorer/query/26931447
The problem is seen in polkadot_parachain_peer_count metrics, but it seems people are not monitoring that well enough, so let's make it more visible nodes with low connectivity are not working in good conditions.
I also reduced the threshold to 85%, so that we don't trigger this error to eagerly.
Changelog for Runtime Dev
ℹ️ These changes are relevant to: All of those who rely on the runtime. A parachain team that is using a pallet. A DApp that is using a pallet. These are people who care about the protocol (WASM, not the meta-protocol (client).)
[#9354]: Remove whitespaces added by macros due to token re-parsing
Normalize result of stringify in scenarios when used inside nested macros to stringify token streams for benchmarking framework
[#9195]: XCMv5 asset exchange test scenarios
Emulated test scenarios added to cover asset exchanging via Transact or ExchangeAsset instruction using XCMv5 capabilities
[#9179]: Fix subsume_assets incorrectly merging two AssetsInHolding
Fix subsume_assets incorrectly merging two AssetsInHolding instances under certain conditions,
which caused asset values to be overridden rather than summed.
[#9137]: Pallet XCM - transfer_assets pre-ahm patch
Pallet XCM's transfer_assets extrinsic now returns an error when it determines that a reserve transfer of DOT|KSM|WND|PAS has to be done.
This is a safeguard in preparation for the Asset Hub Migration (AHM), where the reserve of DOT|KSM|WND|PAS will change from the Relay Chain to Asset Hub.
After the migration, another patch will remove this error case and use the correct reserve.
The pallet uses the UniversalLocation configuration to figure out the correct asset being transferred. It's very important to have that configuration correct.
[#9325]: Fix pallet-im-online benchmarking for runtimes with MaxKeys < 1000
Fixes benchmarking for pallet-im-online when runtime configuration has MaxKeys < 1000.
Previously, the benchmark code used a hardcoded constant MAX_KEYS = 1000 which would cause benchmark failures for runtimes configured with fewer maximum keys. This change updates the benchmark to dynamically use the MaxKeys value from the pallet's Config trait.
[#9139]: Expose more constants for pallet-xcm
Exposes more constants (UniversalLocation, MaxLockers, MaxRemoteLockConsumers), similar as AdvertisedXcmVersion.
Changelog for Node Operator
ℹ️ These changes are relevant to: Those who don't write any code and only run code.
Changelog for Runtime User
ℹ️ These changes are relevant to: Anyone using the runtime. This can be a token holder or a dev writing a front end for a chain.
[#9137]: Pallet XCM - transfer_assets pre-ahm patch
Pallet XCM's transfer_assets extrinsic now returns an error when it determines that a reserve transfer of DOT|KSM|WND|PAS has to be done.
This is a safeguard in preparation for the Asset Hub Migration (AHM), where the reserve of DOT|KSM|WND|PAS will change from the Relay Chain to Asset Hub.
After the migration, another patch will remove this error case and use the correct reserve.
limited_reserve_transfer_assets, transfer_assets_using_type_and_then or execute should be used instead, since they provide the ability to specify the reserve you want to use.
[#9139]: Expose more constants for pallet-xcm
Exposes more constants (UniversalLocation, MaxLockers, MaxRemoteLockConsumers), similar as AdvertisedXcmVersion.
Rust compiler versions
This release was built and tested against the following versions of rustc.
Other versions may work.
- Rust Stable:
1.84.1
Polkadot stable2412-8
This release contains the changes from polkadot-stable2412-7 to polkadot-stable2412-8.
ℹ️ Please note:
stable2412 and contains only patches and fixes to the crates (list below). No binary or docker images will be provided for this release.
The tag corresponding to the current patch release polkadot-stable2412-8 and matching the old pattern will be available under polkadot-v1.17.8.
The following crates were updated to the corresponding versions:
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
Changelog
Changelog for Node Dev
ℹ️ These changes are relevant to: Those who build around the client side code. Alternative client builders, SMOLDOT, those who consume RPCs. These are people who are oblivious to the runtime changes. They only care about the meta-protocol, not the protocol itself.
[#8973]: Add polkadot_parachain_peer_connectivity metric
Adds polkadot_parachain_peer_connectivity histogram metric to better understand connectivity patterns.
Changelog for Runtime Dev
ℹ️ These changes are relevant to: All of those who rely on the runtime. A parachain team that is using a pallet. A DApp that is using a pallet. These are people who care about the protocol (WASM, not the meta-protocol (client).)
[#9325]: Fix pallet-im-online benchmarking for runtimes with MaxKeys < 1000
Fixes benchmarking for pallet-im-online when runtime configuration has MaxKeys < 1000.
Previously, the benchmark code used a hardcoded constant MAX_KEYS = 1000 which would cause benchmark failures for runtimes configured with fewer maximum keys. This change updates the benchmark to dynamically use the MaxKeys value from the pallet's Config trait.
[#9139]: Expose more constants for pallet-xcm
Exposes more constants (UniversalLocation, MaxLockers, MaxRemoteLockConsumers), similar as AdvertisedXcmVersion.
[#9137]: Pallet XCM - transfer_assets pre-ahm patch
Pallet XCM's transfer_assets extrinsic now returns an error when it determines that a reserve transfer of DOT|KSM|WND|PAS has to be done.
This is a safeguard in preparation for the Asset Hub Migration (AHM), where the reserve of DOT|KSM|WND|PAS will change from the Relay Chain to Asset Hub.
After the migration, another patch will remove this error case and use the correct reserve.
The pallet uses the UniversalLocation configuration to figure out the correct asset being transferred. It's very important to have that configuration correct.
[#9179]: Fix subsume_assets incorrectly merging two AssetsInHolding
Fix subsume_assets incorrectly merging two AssetsInHolding instances under certain conditions,
which caused asset values to be overridden rather than summed.
[#8694]: Fix pallet_migrations benchmark when FailedMigrationHandler emits events
When FailedMigrationHandler emits events, the UpgradeFailed event is not the last one, so assert_last_event fails. Fixed by checking that the UpgradeFailed event is emitted, even if it is not the last one.
[#8179]: Do not make pallet-identity benchmarks signature-dependent
- Includes a
benchmark_helperconfiguration function inpallet-identityto handle signing operations. - Abstracts away the explicit link with SR25519 schema in the benchmarks, allowing chains with a different one to be able to run them and calculate the weights.
- Adds a default implementation that leaves the code equivalent.
- The requirement is for the
AccountIdtype of the runtime to implement theDecodetrait
Changelog for Runtime User
ℹ️ These changes are relevant to: Anyone using the runtime. This can be a token holder or a dev writing a front end for a chain.
[#9139]: Expose more constants for pallet-xcm
Exposes more constants (UniversalLocation, MaxLockers, MaxRemoteLockConsumers), similar as AdvertisedXcmVersion.
[#9137]: Pallet XCM - transfer_assets pre-ahm patch
Pallet XCM's transfer_assets extrinsic now returns an error when it determines that a reserve transfer of DOT|KSM|WND|PAS has to be done.
This is a safeguard in preparation for the Asset Hub Migration (AHM), where the reserve of DOT|KSM|WND|PAS will change from the Relay Chain to Asset Hub.
After the migration, another patch will remove this error case and use the correct reserve.
limited_reserve_transfer_assets, transfer_assets_using_type_and_then or execute should be used instead, since they provide the ability to specify the reserve you want to use.
Rust compiler versions
This release was built and tested against the following versions of rustc.
Other versions may work.
- Rust Stable:
1.81.0
Polkadot stable2506
This release contains the changes from polkadot-stable2503 to polkadot-stable2506.
ℹ️ Please note:
The tag corresponding to the current stable release polkadot-stable2506 and matching the old pattern will be available under polkadot-v1.19.0.
Changelog
Changelog for Node Dev
ℹ️ These changes are relevant to: Those who build around the client side code. Alternative client builders, SMOLDOT, those who consume RPCs. These are people who are oblivious to the runtime changes. They only care about the meta-protocol, not the protocol itself.
[#8533]: fatxpool: add fallback for ready at light
Add fallback for ready_at_light for the case of not finding a best view that can be used to return a set of ready transactions. Optimised as well how the best view is searched.
[#8948]: make sure dispute_coordinator/approval-voting parallel can receive priority messages
#8834, changed relay_chain_selection to send priority messages, but did not configured the subsystems to tell they can receive priority messages, with can_receive_priority_messages flag.
If can_receive_priority_messages is not specified orchestra falls back when sending a priority message to the normal queue,
so this resulted in the messages not being processed ahead of the others in the queue.
Fix this configuration mistake and add a test to make sure priority messages are consumed ahead of normal ones by the subsystems.
[#7867]: benchmark/storage Make read/write benchmarks more accurate
Improve the benchmark accuracy of read/write costs by making sure for both reads and write we compute the amortized cost of a single key operation, by adding a batch functionality to make sure the cost of common operations like root computation is spread across multiple keys. Additionally, also add a pov-recorder flag, so that we are able to replicate the same environment as parachains do.
[#8973]: Add polkadot_parachain_peer_connectivity metric
Adds polkadot_parachain_peer_connectivity histogram metric to better understand connectivity patterns.
[#8443]: Stabilize V16 metadata
Metadata V16 is stabilized. V16 metadata exposes information about Pallet View Functions and V5 transactions,
and can be obtained, where applicable, by using the Runtime APIs Metadata_metadata_at_version(16).
[#8923]: fatxpool: fix: remove invalid txs from the dropped stream controller
While testing mortal transaction I encountered exactly the same problem as in #8490.
This PR should fix the problem.
fixes: #8490
[#8072]: RFC-0008: Store parachain bootnodes in the relay chain DHT
Implement RFC-0008 "DHT bootnodes".
With this mechanism, every parachain node is eligible to act as a bootnode. If its peer ID is close to the parachain key for the current relay chain epoch, it becomes discoverable by other parachain nodes via the relay chain DHT. This removes the need to specify bootnodes in the parachain chainspec, eliminating a single point of failure and simplifying things for parachain operators.
The mechanism is enabled by default. The embedded DHT bootnode can be disabled using the --no-dht-bootnode flag, and discovery of such nodes can be disabled with the --no-dht-bootnode-discovery flag.
[#8606]: Use hashbrown hashmap/hashset in validation context
Discovered while profiling #6131 (comment) with the benchmark #8069 that when running in validation a big chunk of the time is spent inserting and retrieving data from the BTreeMap/BTreeSet.
By switching to hashbrown HashMap/HashSet in validation TrieCache and TrieRecorder and the memory-db paritytech/trie#221 read costs improve with around ~40% and write with about ~20%
[#9050]: dispute-coordinator: handle race with offchain disabling
Fixes a potential race with off-chain disabling when we learned about disablement after importing a dispute from that validator.
[#8594]: omni-node: fix benchmark pallet to work with --runtime
polkadot-omni-node benchmark pallet can use one of --runtime or --chain now, like frame-omni-bencher does.
[#7955]: Add ApprovedPeer UMP signal
Add a new ApprovedPeer UMP signal variant for specifying a peerid that should be credited for authoring and supplying the candidate.
Will be used by the new collator protocol implementation for promoting the reputation of collators. Candidates should still not emit any UMP signals until the CandidateReceiptV2 node feature is enabled.
[#8370]: fix unneeded collator connection issue
This PR fixes an issue where collators continued attempting to connect to validators even after their core assignment was removed, leading to unnecessary connections and log spam An unneeded collator connected.
The fix ensures collators only connect to validators if there are cores assigned to the parachain.
[#8314]: Add RPCs in the statement store to get the statements and not just the statement data.
In statement-store, statements can contain a proof with the signature of the statement, this proof is useful to assert that the statement comes from the expected account. This proof also signs for all the statements fields, those can also be useful information for the receiver.
This PR adds broadcasts_stmt, posted_stmt, and posted_clear_stmt RPCs to get the full statements from the statement store.
[#8688]: bound trusted local cache to shared limits sizes
Since there is no point in letting local cache grow past the shared cache limits, bound it to those limits.
[#7556]: Add trie cache warmup
Warm up the Trie cache based on a CLI flag to enhance the performance of smart contracts on AssetHub by reducing storage access time.
[#8837]: Cache locally controlled validator indices in dispute-coordinator
dispute-coordinator uses keystore.key_pair() to obtain the set of locally controlled validator IDs. This operation happens on each import and is expensive because it involves key generation from a seed phrase. This patch lazily determines the set of locally controlled validator IDs and caches the result for each session.
[#8833]: Check artifact integrity before execution
In case of a corrupted artifact, we can find it out before execution and re-prepare the artifact.
[#9102]: polkadot-omni-node: pass timestamp inherent data for block import
This should allow aura runtimes to check timestamp inherent data when syncing/importing blocks
that include timestamp inherent data.
Runtime developers can check timestamp inherent data while using polkadot-omni-node-lib/polkadot-omni-node/polkadot-parachain binaries.
This change is backwards compatible and doesn't require runtimes to check the timestamp inherent, but they are able to do it now if needed.
[#8134]: separate validation and collation protocols
This PR completes the removal of validation protocol versions 1 and 2 by separating validation from collation. Previously, a shared Versioned enum prevented full removal.
With this change, outdated validation messages are now eliminated.
[#8831]: dispute-coordinator: increase lru_observed_blocks_capacity
Under increase load with finality lagging behind there is a risk for blocks to arrive late or out of sequence in that case we will end up scrapping from the received block un till last finalized block and then process all the dispute in-between.
This couple with other inefficiencies like #8823 will increase unnecessarily the load on dispute-coordinator.
Decided to make this super large to err on the cautious side, the Hash size is only 32 bytes, so this will make the LRU grow up to 65k, which I don't think is a significant increase.
[#9094]: bitfield_distribution: fix subsystem clogged at begining of a session
handle_peer_view_change gets called on NewGossipTopology with the existing view of the peer to cover for the case when the topology might arrive late, but in that case in the view will contain old blocks from previous session, so since the X/Y neighbour change because of the topology change you end up sending a lot of messages for blocks before the session changed.
Fix it by checking the send message only for relay chains that are in the same session as the current topology.
[#8332]: parachain informant
Adds a new cumulus-relay-chain-streams crate to make it easier to reuse relay chain streams.
[#8839]: net/discovery: File persistence for AddrCache
Persisting the AddrCache periodically (every 10 minutes) and on worker shutdown. Read AddrCache from file upon launch of worker.
AddrCache is saved as authority_discovery_addr_cache.json in the
folder configured by net_config_path of NetworkConfiguration.
This reduces the time it takes for a node to reconnect to peers after restart.
[#9264]: gossip-support: make low connectivity message an error
All is not well when a validator is not properly connected, e.g: of things that might happen:
- Finality might be slightly delay because validator will be no-show because they can't retrieve PoVs to validate approval work: #8915.
- When they author blocks they won't back things because gossiping of backing statements happen using the grid topology:, e.g blocks authored by validators with a low number of peers:
https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc-polkadot.helixstreet.io#/explorer/query/26931262
https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc-polkadot.helixstreet....
Polkadot stable2409-10
3a7b924
EgorPopelyaev
Egor_P
This release contains the changes from polkadot-stable2409-9 to polkadot-stable2409-10.
ℹ️ Please note:
stable2409-10 and contains only patches and fixes to the crates (list below). No binary or docker images will be provided for this release.
The tag corresponding to the current patch release polkadot-stable2409-10 and matching the old pattern will be available under polkadot-v1.16.10.
The following crates were updated to the corresponding versions:
Changelog
Changelog for Node Dev
ℹ️ These changes are relevant to: Those who build around the client side code. Alternative client builders, SMOLDOT, those who consume RPCs. These are people who are oblivious to the runtime changes. They only care about the meta-protocol, not the protocol itself.
[#8973]: Add polkadot_parachain_peer_connectivity metric
Adds polkadot_parachain_peer_connectivity histogram metric to better understand connectivity patterns.
Changelog for Runtime Dev
ℹ️ These changes are relevant to: All of those who rely on the runtime. A parachain team that is using a pallet. A DApp that is using a pallet. These are people who care about the protocol (WASM, not the meta-protocol (client).)
[#8694]: Fix pallet_migrations benchmark when FailedMigrationHandler emits events
When FailedMigrationHandler emits events, the UpgradeFailed event is not the last one, so assert_last_event fails. Fixed by checking that the UpgradeFailed event is emitted, even if it is not the last one.
[#9139]: Expose more constants for pallet-xcm
Exposes more constants (UniversalLocation, MaxLockers, MaxRemoteLockConsumers), similar as AdvertisedXcmVersion.
[#9137]: Pallet XCM - transfer_assets pre-ahm patch
Pallet XCM's transfer_assets extrinsic now returns an error when it determines that a reserve transfer of DOT|KSM|WND|PAS has to be done.
This is a safeguard in preparation for the Asset Hub Migration (AHM), where the reserve of DOT|KSM|WND|PAS will change from the Relay Chain to Asset Hub.
After the migration, another patch will remove this error case and use the correct reserve.
The pallet uses the UniversalLocation configuration to figure out the correct asset being transferred. It's very important to have that configuration correct.
Changelog for Runtime User
ℹ️ These changes are relevant to: Anyone using the runtime. This can be a token holder or a dev writing a front end for a chain.
[#9139]: Expose more constants for pallet-xcm
Exposes more constants (UniversalLocation, MaxLockers, MaxRemoteLockConsumers), similar as AdvertisedXcmVersion.
[#9137]: Pallet XCM - transfer_assets pre-ahm patch
Pallet XCM's transfer_assets extrinsic now returns an error when it determines that a reserve transfer of DOT|KSM|WND|PAS has to be done.
This is a safeguard in preparation for the Asset Hub Migration (AHM), where the reserve of DOT|KSM|WND|PAS will change from the Relay Chain to Asset Hub.
After the migration, another patch will remove this error case and use the correct reserve.
limited_reserve_transfer_assets, transfer_assets_using_type_and_then or execute should be used instead, since they provide the ability to specify the reserve you want to use.
Rust compiler versions
This release was built and tested against the following versions of rustc.
Other versions may work.
- Rust Stable:
"1.81.0"
Polkadot stable2503-7
This release contains the changes from polkadot-stable2503-6 to polkadot-stable2503-7.
This is a patch release for the latest stable version: stable2503. You can consider upgrading to it to have the latest fixes for this version.
The tag corresponding to the current patch release polkadot-stable2503-7 and matching the old pattern will be available under polkadot-v1.18.7.
sc-network and sc-network-types crates all the dependant crates had to be major bumped in this release.
Changelog
Changelog for Node Dev
ℹ️ These changes are relevant to: Those who build around the client side code. Alternative client builders, SMOLDOT, those who consume RPCs. These are people who are oblivious to the runtime changes. They only care about the meta-protocol, not the protocol itself.
[#9102]: polkadot-omni-node: pass timestamp inherent data for block import
This should allow aura runtimes to check timestamp inherent data when syncing/importing blocks that include timestamp inherent data.
Runtime developers can check timestamp inherent data while using polkadot-omni-node-lib/polkadot-omni-node/polkadot-parachain binaries.
This change is backwards compatible and doesn't require runtimes to check the timestamp inherent, but they are able to do it now if needed.
[#9050]: dispute-coordinator: handle race with offchain disabling
Fixes a potential race with off-chain disabling when we learned about disablement after importing a dispute from that validator.
[#8837]: Cache locally controlled validator indices in dispute-coordinator
dispute-coordinator uses keystore.key_pair() to obtain the set of locally controlled validator IDs. This operation happens on each import and is expensive because it involves key generation from a seed phrase. This patch lazily determines the set of locally controlled
validator IDs and caches the result for each session.
[#8948]: make sure dispute_coordinator/approval-voting parallel can receive priority messages
#8834, changed relay_chain_selection to send priority messages, but did not configured
the subsystems to tell they can receive priority messages, with can_receive_priority_messages flag.
If can_receive_priority_messages is not specified orchestra falls back when sending a priority message to the normal queue,
so this resulted in the messages not being processed ahead of the others in the queue.
Fix this configuration mistake and add a test to make sure priority messages are consumed ahead of normal ones by the subsystems.
[#8832]: increase session index cache
A 10 session index cache is not enough when you run under intense pressure and finality is lagg since you will end requesting the session index for blocks older than that. So let's make this cache larger to achieve its purpose even under intense load when it actually matters more to be faster.
The session_index_cache keeps a Hash and a u32, so that's about 36 bytes per entry, with this increase it can grow up to 65k which is not that big in my book.
[#8973]: Add polkadot_parachain_peer_connectivity metric
Adds polkadot_parachain_peer_connectivity histogram metric to better understand connectivity patterns.
[#8834]: extend overseer to send priority messages
Extend overseer to send priority messages, the new functionality is used for sending messages on the grandpa call path when we call dispute-coordinator and approval-voting in finality_target_with_longest_chain to make sure we don't block unnecessarily.
[#8831]: dispute-coordinator: increase lru_observed_blocks_capacity
Under increase load with finality lagging behind there is a risk for blocks to arrive late or out of sequence, in that case we will end up scrapping from the received block un till last finalized block and then process all the dispute in-between.
This couple with other inefficiencies like #8823 will increase unnecessarily the load on dispute-coordinator.
Decided to make this super large to err on the cautious side, the Hash size is only 32 bytes, so this will make the LRU grow up to 65k, which I don't think is a significant increase.
Changelog for Runtime Dev
ℹ️ These changes are relevant to: All of those who rely on the runtime. A parachain team that is using a pallet. A DApp that is using a pallet. These are people who care about the protocol (WASM, not the meta-protocol (client).)
[#9102]: polkadot-omni-node: pass timestamp inherent data for block import
This should allow aura runtimes to check timestamp inherent data when syncing/importing blocks that include timestamp inherent data.
Runtime developers can check timestamp inherent data while using polkadot-omni-node-lib/polkadot-omni-node/polkadot-parachain binaries.
This change is backwards compatible and doesn't require runtimes to check the timestamp inherent, but they are able to do it now if needed.
[#8725]: Snowbridge: register polkadot native asset with fee
To enforce a fee for PNA registration.
[#6827]: Introduction of Approval Slashes
Introduces a more aggressive slashing scheme.
Lazy or spammy validators will from now on be slashable in disputes.
Even if your validator is not a backer but it approves an invalid block it will be slashed 2%.
If your validator raises or supports fake alarms (disputes against valid blocks) you will be slashed (0%) and disabled for the remainder
of the era, which will potentially reduce era point gains.
[#8980]: Fix revive-fixtures build script
Fix compilation issue with pallet-revive-fixtures build.rs script.
[#8787]: Westend governance authorize_upgrade integration tests
Integration tests covering authorize_upgrade with whitelisting via Collectives for Westend network
[#8932]: pallet-balances: Do not create account in benchmarking
This particular benchmark is about benchmarking the account creation, so we should not create it before :)
Closes: #8927
[#9130]: Modified ToParachainDeliveryHelper utilize WithdrawAsset based worst-case fee estimation instead of ClearOrigin
This PR contains modified ToParachainDeliveryHelper to utilize WithdrawAsset based worst-case fee estimation instead of ClearOrigin.
[#8694]: Fix pallet_migrations benchmark when FailedMigrationHandler emits events
When FailedMigrationHandler emits events, the UpgradeFailed event is not the last one, so assert_last_event fails. Fixed by checking that the UpgradeFailed event is emitted, even if it is not the last one.
Changelog for Node Operator
ℹ️ These changes are relevant to: Those who don't write any code and only run code.
[#8345]: tx/metrics: Add metrics for the RPC v2 transactionWatch_v1_submitAndWatch
This PR adds metrics for the following RPC subscription: transactionWatch_v1_submitAndWatch
Metrics are exposed in two ways:
- simple counters of how many events we've seen globally
- a histogram vector of execution times, which is labelled by
initial event->final event- This helps us identify how long it takes the transaction pool to advance the state of the events, and further debug issues
Part of: #8336
[#6827]: Introduction of Approval Slashes
Introduces a more aggressive slashing scheme.
Lazy or spammy validators will from now on be slashable in disputes.
Even if your validator is not a backer, but it approves an invalid block it will be slashed 2%.
If your validator raises or supports fake alarms (disputes against valid blocks) you will be slashed (0%) and disabled for the remainder
of the era, which will potentially reduce era point gains.
Rust compiler versions
This release was built and tested against the following versions of rustc.
Other versions may work.
- Rust Stable:
1.84.1
Docker images
The docker images for the polkadot node binary and the polkadot-parachain binary can be found at Docker hub (will be available a few minutes after the release has been published):
You may also pull it with:
docker pull parity/polkadot:stable2503-7
or
docker pull parity/polkadot-parachain:stable2503-7