Polkadot’s 2609‑RC2 pre‑release has been published, bringing a significant number of breaking changes—85 in total—across the ecosystem’s bridges and XCM modules. The update is flagged as a pre‑release, meaning it is intended for testing and may exhibit errors or unexpected behavior.
The most prominent alterations involve bridge functionality. Pull requests #11147, #12159, and #12585 address memory tracking for nested XCM messages, block origin‑spoofing in Snowbridge’s outbound queue, and the removal of legacy Polkadot Bulletin bridge code. Additionally, the trie‑db dependency has been bumped to 0.32.0, which may affect storage handling for certain runtime modules.
XCM‑related changes focus on deprecating obsolete types and traits. Several aliases such as `ConvertedConcreteAssetId`, `FilterAssetLocation`, and `ForeignChainAliasAccount` have been removed, as have the `CurrencyAdapter` and `UnpaidLocalExporter` from the staging‑xcm‑builder. The pallet‑asset‑conversion now supports per‑pair swap fees, falling back to a global LPFee if none is specified.
These modifications are driven by the need to keep the Polkadot SDK aligned with evolving security and interoperability standards. While the changes promise tighter security and clearer API usage, they also require developers to review and adjust their codebases to maintain compatibility.
Because the release is pre‑stable, the developers caution that it should be used only for testing. The official stable version is expected soon, and users are encouraged to delay production deployments until that release is available.
In summary, Polkadot’s 2609‑RC2 pre‑release marks a substantial evolution of the SDK, tightening bridge security, modernizing XCM interfaces, and preparing the ecosystem for future upgrades. Stakeholders should monitor the changelog, test thoroughly, and await the final stable release before integrating the new components into live networks.