This release contains the changes from polkadot-stable2409-3 to polkadot-stable2409-4.
ℹ️ Please note:
⚠️ This is a patch release for the previous stable version: 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-4 and matching the old pattern will be available under polkadot-v1.16.4.
The following crates were updated to the corresponding versions:
- sc-network@0.45.5
- pallet-bounties@37.0.2
- polkadot-runtime-parachains@17.0.2
- snowbridge-pallet-inbound-queue-fixtures@0.18.1
- snowbridge-router-primitives@0.16.1
- rococo-runtime@18.0.1
- westend-runtime@18.0.2
- polkadot-node-core-approval-voting@18.3.0
- polkadot-service@19.0.1
- cumulus-client-consensus-aura@0.18.1
- staging-xcm-executor@17.0.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.
[#7050]: Avoid incomplete block import pipeline with full verifying import queue
When warp syncing a node using the equivocation checking verifier, we now properly set the fork_choice rule.
Affected are mostly nodes that are derived from the parachain template. Omni-node is not affected.
The prevents the error ClientImport("Incomplete block import pipeline.") after state sync.
[#6971]: Make importing of duplicate assignment idempotent
Normally, approval-voting wouldn't receive duplicate assignments because approval-distribution makes
sure of it, however in the situation where we restart we might receive the same assignment again and
since approval-voting already persisted it we will end up inserting it twice in ApprovalEntry.tranches.assignments
because that's an array. Fix this by inserting only assignments that are not duplicate.
[#6973]: approval-voting fix sending of assignments after restart
There is a problem on restart where nodes will not trigger their needed assignment if
they were offline and the time of the assignment passed, so after restart always
schedule a wakeup so that nodes a have the opportunity of triggering their assignments
if they are still needed.
[#6807]: Retry approval on availability failure if the check is still needed
Recovering the POV can fail in situation where the node just restart and the DHT topology
wasn't fully discovered yet, so the current node can't connect to most of its Peers.
This is bad because for gossiping the assignment you need to be connected to just a few
peers, so because we can't approve the candidate other nodes will see this as a no show.
Fix it by retrying to approve a candidate for a fixed number of atttempts if the block is
still needed.
[#7116]: Increase the number of pvf execution workers from 2 to 4
Increase the number of pvf execution workers from 2 to 4.
[#7158]: Reject litep2p inbound requests from banned peers
This PR rejects inbound requests from banned peers (reputation is below the banned threshold).
This mirrors the request-response implementation from the libp2p side.
While at it, have registered a new inbound failure metric to have visibility into this.
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).)
[#7201]: xcm: avoid subtracting delivery fees twice
Avoid subtracting delivery fees twice in DepositReserveAsset call when jit mode is enabled.
[#7013]: pallet-bounties: Fix benchmarks for 0 ED
Closes: #7009
[#5526]: Fix enact_candidate weight generation
This PR works around an issue in multivariate linear regression of weight generation.
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.
[#7089]: [stable2409] Backport Snowbridge - Support bridging native ETH
Support Native ETH as an asset type instead of only supporting WETH. WETH is still supported, but adds
support for ETH in the inbound and outbound routers.
Rust compiler versions
This release was built and tested against the following versions of rustc.
Other versions may work.
- Rust Stable:
"1.81.0"