…itytech#5892)

Resolves polkadot-fellows/runtimes#459

Tested with rococo/westend/kusama/polkadot runtimes

---------

Co-authored-by: DavidK <[email protected]>
Co-authored-by: Muharem <[email protected]>
Co-authored-by: Shawn Tabrizi <[email protected]>
Co-authored-by: Dónal Murray <[email protected]>

`AccountData` should be set to `()` and not to `AccountInfo`.

Closes: paritytech#5922

---------

Co-authored-by: Shawn Tabrizi <[email protected]>

Related to
paritytech#5924 (comment)

improve prdoc arguments validation & help:
- convert audiences options to snake_case. Fixes
paritytech#5927
  - support more than one audiences
  - define allowed bump options
- infer --pr from the actual PR (now it's optional, can still be
overwritten)


![image](https://github.com/user-attachments/assets/24e18fe2-2f67-4ce0-90e4-34f6c2f860c9)

Test evidence:
paritytech-stg@6dd274e

- moved the omni-node lib from
  `cumulus/polkadot-parachain/polkadot-parachain-lib` to
  `cumulus/polkadot-omni-node/lib`
- renamed `polkadot-parachain-lib` to `polkadot-omni-node-lib`
- added `polkadot-omni-node` binary

Related to paritytech#5566

Changes:
- Add `--exclude-pallets` to exclude some pallets from runtimes where we
dont have genesis presets yet
- Make `--genesis-builder-policy=none` work with `--runtime`
- CI: Run the frame-omni-bencher for all runtimes

---------

Signed-off-by: Oliver Tale-Yazdi <[email protected]>
Co-authored-by: ggwpez <[email protected]>
Co-authored-by: Bastian Köcher <[email protected]>
Co-authored-by: Branislav Kontur <[email protected]>
Co-authored-by: alvicsam <[email protected]>
Co-authored-by: Maksym H <[email protected]>
Co-authored-by: Alexander Samusev <[email protected]>
Co-authored-by: Maksym H <[email protected]>

Bump zombienet version, including fixes for `ci` and set _resources
requests_ for the runner.

Thx!

Co-authored-by: Bastian Köcher <[email protected]>

This bumps `ethbloom`, `ethereum-types`, `primitive-types` and `rlp` to
their latest version.

Fixes: paritytech#5870

---------

Co-authored-by: command-bot <>
Co-authored-by: ggwpez <[email protected]>
Co-authored-by: Oliver Tale-Yazdi <[email protected]>
Co-authored-by: Shawn Tabrizi <[email protected]>
Co-authored-by: Dónal Murray <[email protected]>

Disable flaky tests reported in:
paritytech#5972 
paritytech#5973 
paritytech#5974

PR removes short-benchmarks from GitLab, adds condition for
cargo-check-rutimes

…binaries and deb package (paritytech#5963)

This PR introduces a GitHub flow, that should replace a semi manual part
of the release process to build rc binaries for `polkadot` and
`polkadot-parachain` + the `polkadot` deb package.

Right now, this part of the release is done on the `cleanroom` machine
by the release engineers via triggering bash scripts directly on the
server. These GitHub flows should replace it and move everything to the
CI.

The whole flow is meant to be run in the new
[paritytech-release](https://github.com/paritytech-release) where the
automated release is going to be moved.

The flow includes the following steps:
- Build `polkadot`, `polakdot-prepare-worker`, `polkadot-execute-worker`
and `polkadopt-parachain` binaries
- Sign those artefacts using `gpg` and generate a sha256 checksum
- Build deb package for `polakdot`
- Make a GitHub attestation
- Upload artefacts to the S3 buckets

Closes: paritytech/release-engineering#223

---------

Co-authored-by: Oliver Tale-Yazdi <[email protected]>

# Description

We previously set the PoV request timeout to 1.2s based on synchronous
backing, which allowed for 5 PoVs per relay block. With asynchronous
backing, we no longer have a time budget and can increase the value to
2s.

Fixes paritytech#5885

## Integration

This PR shouldn't affect downstream projects.

## Review Notes

This PR can be followed by experiments with Gluttons on Kusama to
confirm that the timeout is sufficient.

PR moves `test-linux-stable-no-try-runtime` from gitlab to github.
I disabled two tests because our current runners don't have necessary
syscalls enabled. Will continue working on it in
paritytech/ci_cd#1056
Also PR remove `gh cli` installation since it's installed in the
`ci-unified` image.

close paritytech/ci_cd#1023

paritytech#5886 (comment)

---------

Co-authored-by: Bastian Köcher <[email protected]>
Co-authored-by: Bastian Köcher <[email protected]>

Here are MD docs for V2 @acatangiu @franciscoaguirre . Let me know what
you think.

---------

Co-authored-by: Adrian Catangiu <[email protected]>
Co-authored-by: Francisco Aguirre <[email protected]>
Co-authored-by: Alistair Singh <[email protected]>

Resolves paritytech#4632

The new logic optimizes the distribution of execution jobs for disputes,
approvals, and backings. Testing shows improved finality lag and
candidate checking times, especially under heavy network load.

### Approach

This update adds prioritization to the PVF execution queue. The logic
partially implements the suggestions from
paritytech#4632 (comment).

We use thresholds to determine how much a current priority can "steal"
from lower ones:
-  Disputes: 70%
-  Approvals: 80%
-  Backing System Parachains: 100%
-  Backing: 100%

A threshold indicates the portion of the current priority that can be
allocated from lower priorities.

For example:
-  Disputes take 70%, leaving 30% for approvals and all backings.
- 80% of the remaining goes to approvals, which is 30% * 80% = 24% of
the original 100%.
- If we used parts of the original 100%, approvals couldn't take more
than 24%, even if there are no disputes.

Assuming a maximum of 12 executions per block, with a 6-second window, 2
CPU cores, and a 2-second run time, we get these distributions:

-  With disputes: 8 disputes, 3 approvals, 1 backing
-  Without disputes: 9 approvals, 3 backings

It's worth noting that when there are no disputes, if there's only one
backing job, we continue processing approvals regardless of their
fulfillment status.

### Versi Testing 40/20

Testing showed a slight difference in finality lag and candidate
checking time between this pull request and its base on the master
branch. The more loaded the network, the greater the observed
difference.

Testing Parameters:
-  40 validators (4 malicious)
-  20 gluttons with 2 seconds of PVF execution time
-  6 VRF modulo samples
-  12 required approvals

![Pasted Graphic
3](https://github.com/user-attachments/assets/8b6163a4-a1c9-44c2-bdba-ce1ef4b1eba7)
![Pasted Graphic
4](https://github.com/user-attachments/assets/9f016647-7727-42e8-afe9-04f303e6c862)

### Versi Testing 80/40

For this test, we compared the master branch with the branch from
paritytech#5616. The second branch
is based on the current one but removes backing jobs that have exceeded
their time limits. We excluded malicious nodes to reduce noise from
disputing and banning validators. The results show that, under the same
load, nodes experience less finality lag and reduced recovery and check
time. Even parachains are functioning with a shorter block time,
although it remains over 6 seconds.

Testing Parameters:
-  80 validators (0 malicious)
-  40 gluttons with 2 seconds of PVF execution time
-  6 VRF modulo samples
-  30 required approvals


![image](https://github.com/user-attachments/assets/42bcc845-9115-4ae3-9910-286b77a60bbf)

---------

Co-authored-by: Andrei Sandu <[email protected]>

Bumps [strum](https://github.com/Peternator7/strum) from 0.26.2 to
0.26.3.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/Peternator7/strum/releases">strum's
releases</a>.</em></p>
<blockquote>
<h2>v0.26.3</h2>
<h2>What's Changed</h2>
<ul>
<li>Fix typos &amp; misspellings in docs by <a
href="https://github.com/5-pebbles"><code>@​5-pebbles</code></a> in <a
href="https://redirect.github.com/Peternator7/strum/pull/347">Peternator7/strum#347</a></li>
<li>Update <code>heck</code> requirement by <a
href="https://github.com/smoelius"><code>@​smoelius</code></a> in <a
href="https://redirect.github.com/Peternator7/strum/pull/346">Peternator7/strum#346</a></li>
<li>Fix broken links by <a
href="https://github.com/rainbowatcher"><code>@​rainbowatcher</code></a>
in <a
href="https://redirect.github.com/Peternator7/strum/pull/350">Peternator7/strum#350</a></li>
<li>Interpolate unnamed enum variant fields in to_string attribute by <a
href="https://github.com/gin-ahirsch"><code>@​gin-ahirsch</code></a> in
<a
href="https://redirect.github.com/Peternator7/strum/pull/345">Peternator7/strum#345</a></li>
<li>add hyperlinks to documentation and clarify derive macros by <a
href="https://github.com/lolbinarycat"><code>@​lolbinarycat</code></a>
in <a
href="https://redirect.github.com/Peternator7/strum/pull/355">Peternator7/strum#355</a></li>
<li>Use fully qualified syntax for calling <code>get</code> on an
<code>EnumIter</code>, eliminating ambiguities by <a
href="https://github.com/bluurryy"><code>@​bluurryy</code></a> in <a
href="https://redirect.github.com/Peternator7/strum/pull/357">Peternator7/strum#357</a></li>
</ul>
<h2>New Contributors</h2>
<ul>
<li><a href="https://github.com/5-pebbles"><code>@​5-pebbles</code></a>
made their first contribution in <a
href="https://redirect.github.com/Peternator7/strum/pull/347">Peternator7/strum#347</a></li>
<li><a
href="https://github.com/rainbowatcher"><code>@​rainbowatcher</code></a>
made their first contribution in <a
href="https://redirect.github.com/Peternator7/strum/pull/350">Peternator7/strum#350</a></li>
<li><a
href="https://github.com/gin-ahirsch"><code>@​gin-ahirsch</code></a>
made their first contribution in <a
href="https://redirect.github.com/Peternator7/strum/pull/345">Peternator7/strum#345</a></li>
<li><a
href="https://github.com/lolbinarycat"><code>@​lolbinarycat</code></a>
made their first contribution in <a
href="https://redirect.github.com/Peternator7/strum/pull/355">Peternator7/strum#355</a></li>
<li><a href="https://github.com/bluurryy"><code>@​bluurryy</code></a>
made their first contribution in <a
href="https://redirect.github.com/Peternator7/strum/pull/357">Peternator7/strum#357</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/Peternator7/strum/compare/v0.26.2...v0.26.3">https://github.com/Peternator7/strum/compare/v0.26.2...v0.26.3</a></p>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/Peternator7/strum/blob/master/CHANGELOG.md">strum's
changelog</a>.</em></p>
<blockquote>
<h2>0.26.3 (strum_macros)</h2>
<ul>
<li><a
href="https://redirect.github.com/Peternator7/strum/pull/344">#344</a>:
Hide <code>EnumTable</code> because it's going to be deprecated in the
next
version.</li>
<li><a
href="https://redirect.github.com/Peternator7/strum/pull/357">#357</a>:
Fixes an incompatiblity with <code>itertools</code> by using the fully
qualified name rather than the inherent method.</li>
<li><a
href="https://redirect.github.com/Peternator7/strum/pull/345">#345</a>:
Allows unnamed tuple like variants to use their variants in
string interpolation. <code>#[strum(to_string = &quot;Field 0: {0},
Field 1: {1})&quot;)]</code> will now work for tuple variants</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/Peternator7/strum/commit/c89286fc2a4916ee61133aaa8d63fce83f6fc39e"><code>c89286f</code></a>
Update changelog &amp; strum_macros version</li>
<li><a
href="https://github.com/Peternator7/strum/commit/0c85c16e12e80dd49e75117e7c94f697d0ad06d0"><code>0c85c16</code></a>
Use associated function syntax for calling <code>get</code> on an
<code>EnumIter</code>, eliminatin...</li>
<li><a
href="https://github.com/Peternator7/strum/commit/9689d7bb55bad0269c3fc9679a7434670139b12b"><code>9689d7b</code></a>
add hyperlinks to documentation and clarify derive macros (<a
href="https://redirect.github.com/Peternator7/strum/issues/355">#355</a>)</li>
<li><a
href="https://github.com/Peternator7/strum/commit/186d29f6a1691b6356a2d85d66f8904b9a5d3140"><code>186d29f</code></a>
Interpolate unnamed enum variant fields in to_string attribute (<a
href="https://redirect.github.com/Peternator7/strum/issues/345">#345</a>)</li>
<li><a
href="https://github.com/Peternator7/strum/commit/410062e122e001e6c3725cdc91483a0d4de5ca31"><code>410062e</code></a>
Fix broken links (<a
href="https://redirect.github.com/Peternator7/strum/issues/350">#350</a>)</li>
<li><a
href="https://github.com/Peternator7/strum/commit/1e46337eb2ec71caccf2fc35929e2f0cbedbb3c2"><code>1e46337</code></a>
Update <code>heck</code> requirement (<a
href="https://redirect.github.com/Peternator7/strum/issues/346">#346</a>)</li>
<li><a
href="https://github.com/Peternator7/strum/commit/f5fce032ed381a334e81676bd2c391353c265476"><code>f5fce03</code></a>
Fix typos &amp; misspellings in docs (<a
href="https://redirect.github.com/Peternator7/strum/issues/347">#347</a>)</li>
<li>See full diff in <a
href="https://github.com/Peternator7/strum/compare/v0.26.2...v0.26.3">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=strum&package-manager=cargo&previous-version=0.26.2&new-version=0.26.3)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

…#5967)

✄
-----------------------------------------------------------------------------

Thank you for your Pull Request! 🙏 Please make sure it follows the
contribution guidelines outlined in [this

document](https://github.com/paritytech/polkadot-sdk/blob/master/docs/contributor/CONTRIBUTING.md)
and fill out the
sections below. Once you're ready to submit your PR for review, please
delete this section and leave only the text under
the "Description" heading.

# Description

Please consider adding RadiumBlock bootnodes to Coretime Polkadot Chain
spec

## Integration

*In depth notes about how this PR should be integrated by downstream
projects. This part is mandatory, and should be
reviewed by reviewers, if the PR does NOT have the `R0-Silent` label. In
case of a `R0-Silent`, it can be ignored.*

## Review Notes

*In depth notes about the **implementation** details of your PR. This
should be the main guide for reviewers to
understand your approach and effectively review it. If too long, use

[`<details>`](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/details)*.

*Imagine that someone who is depending on the old code wants to
integrate your new code and the only information that
they get is this section. It helps to include example usage and default
value here, with a `diff` code-block to show
possibly integration.*

*Include your leftover TODOs, if any, here.*

# Checklist

* [x] My PR includes a detailed description as outlined in the
"Description" and its two subsections above.
* [ ] My PR follows the [labeling requirements](

https://github.com/paritytech/polkadot-sdk/blob/master/docs/contributor/CONTRIBUTING.md#Process
) of this project (at minimum one label for `T` required)
* External contributors: ask maintainers to put the right label on your
PR.
* [ ] I have made corresponding changes to the documentation (if
applicable)
* [ ] I have added tests that prove my fix is effective or that my
feature works (if applicable)

You can remove the "Checklist" section once all have been checked. Thank
you for your contribution!

✄
-----------------------------------------------------------------------------

Co-authored-by: Veena <[email protected]>
Co-authored-by: Dónal Murray <[email protected]>

# Description

This PR addresses
paritytech#5878.

After dry running an xcm on asset hub, we had redundant xcms showing up
in the `forwarded_xcms` field of the dry run effects returned.
These were caused by two things:
- The `UpwardMessageSender` router always added an element even if there
were no messages.
- The two routers on asset hub westend related to bridging (to rococo
and sepolia) getting the message from their queues when their queues is
actually the same xcmp queue that was already contemplated.

In order to fix this, we check for no messages in UMP and clear the
implementation of `InspectMessageQueues` for these bridging routers.
Keep in mind that the bridged message is still sent, as normal via the
xcmp-queue to Bridge Hub.
To keep on dry-running the journey of the message, the next hop to
dry-run is Bridge Hub.
That'll be tackled in a different PR.

Added a test in `bridge-hub-westend-integration-tests` and
`bridge-hub-rococo-integration-tests` that show that dry-running a
transfer across the bridge from asset hub results in one and only one
message sent to bridge hub.

## TODO
- [x] Functionality
- [x] Test

---------

Co-authored-by: command-bot <>

Resolves paritytech#5972

Only needed to increase some timeouts

1800 min

The `quick-benchmarks-omni` job was moved to GHA (can be found
[here](https://github.com/paritytech/polkadot-sdk/blob/439b31ef9bbdf0e0709bbab4804a9590b48ba8f0/.github/workflows/check-frame-omni-bencher.yml#L22))
but hasn't been removed from GitLab . PR fixes it and makes the check
required.

# Description

When we send `QueueEvent::StartWork`, we have already completed the
execution. This may be a leftover of a previous logic change. Currently,
the name is misleading, so it would be better to rename it to
`FinishWork`.


https://github.com/paritytech/polkadot-sdk/blob/c52675efdc05e181ddcec72d3bd425dc0a89d622/polkadot/node/core/pvf/src/execute/queue.rs#L632-L646


https://github.com/paritytech/polkadot-sdk/blob/c52675efdc05e181ddcec72d3bd425dc0a89d622/polkadot/node/core/pvf/src/execute/queue.rs#L361-L363

Fixes paritytech#5910

## Integration

Shouldn't affect downstream projects.

---------

Co-authored-by: GitHub Action <[email protected]>

…#5925)

Some of the features enabled for `polkadot-sdk` umbrella crate were not
necessary for substrate node (e.g. all `cumulus-*` or `polkadot-*`
features) resulting in much longer compilation time. This PR fixes that.

…ch#6007)

### Improved devx of running many pallets simultaneously

Changes to /cmd:
- Replace (flip) `--continue-on-fail` with `--fail-fast`, but only for
`bench`. This makes all pallets/runtimes run non-stop by default, as it
was primary use-case during tests
- The list of successful/failed pallets was hard to find within tons of
logs, so decided to write only needed logs in a file, and output as a
summary in the workflow and in the comment
- Side fix: updated `tasks_example` to `pallet_example_tasks` to make
compliant with standard naming

<img width="1006" alt="image"
src="https://github.com/user-attachments/assets/14896041-7018-4a0d-92b7-4508e81913c2">

+ added command results to workflow summary:
<img width="1275" alt="image"
src="https://github.com/user-attachments/assets/b4a8afdb-dc9f-4ff9-9720-28a88956035f">

---------

Co-authored-by: GitHub Action <[email protected]>

fixes paritytech#5320 @sam0x17 @gupnik 

# Description

The issue could be confirmed with the added example. The cause is for
macro hygiene, `entries` in the `#( #entries_builder )*` expansion won't
be able to reference the `entries` defined outside. The solution here is
to allow the reference to be passed into the expansion with closure.

Or we could just switch to the unhygienic span with `quote::quote!`
instead such that `entries` will resolve to the "outer" definition.

30 hrs -> 72 hours
as it has stopped by timeout here
https://github.com/paritytech/polkadot-sdk/actions/runs/11299872333/job/31431758932

Use the umbrella crate for the parachain template

This covers almost all the dependencies. There are just a few exceptions
for which I created a separate issue:
paritytech#5993

Also related to: paritytech#4782

Testing the approach of this before it goes live on Polkadot
polkadot-fellows/runtimes#471

---------

Signed-off-by: Oliver Tale-Yazdi <[email protected]>
Co-authored-by: Dónal Murray <[email protected]>

fixes paritytech#5981 

Could confirm the issue with the added tests:

```
test tests/split_ui/pass/split_call.rs [should pass] ... error
┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈
error[E0423]: expected value, found attribute macro `origin`
  --> tests/split_ui/pass/split_call.rs:23:1
   |
23 | #[frame_support::pallet(dev_mode)]
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ not a value
   |
   = note: this error originates in the attribute macro `frame_support::pallet` (in Nightly builds, run with -Z macro-backtrace for more info)
```

# Description

`origin` unexpectedly resolved to a macro, which is available at the
span of invocation. The solution here is to use the expansion as a
function instead of a call and pass in the desired values to avoid
ambiguities.

This PR removes the `check-migrations` pipelines for all Rococo chains
because they are going down:
paritytech/devops#3589, and these checks are
starting to fail, e.g.:

https://github.com/paritytech/polkadot-sdk/actions/runs/11339904745/job/31535485254?pr=4982

https://github.com/paritytech/polkadot-sdk/actions/runs/11339904745/job/31535486189?pr=4982

https://github.com/paritytech/polkadot-sdk/actions/runs/11339904745/job/31535486471?pr=4982

Additionally, `coretime-westend` was added to the `check-migrations`
matrix.

This is done by zepter any way

Added error logs in pallet-xcm to help in debugging, fixes paritytech#2408 

## TODO

- [x] change `log::error` to `tracing::error` format for `xcm-executor`
- [x] check existing logs, e.g. this one can be extended with more info
`tracing::error!(target: "xcm::reanchor", ?error, "Failed reanchoring
with error");`
- [x] use `tracing` instead of `log` for `pallet-xcm/src/lib.rs`

---------

Co-authored-by: Ayevbeosa Iyamu <[email protected]>
Co-authored-by: Adrian Catangiu <[email protected]>
Co-authored-by: Francisco Aguirre <[email protected]>
Co-authored-by: Branislav Kontur <[email protected]>
Co-authored-by: Bastian Köcher <[email protected]>

…eturn (paritytech#5599)

`XcmPaymentApi::query_acceptable_payment_assets` is an API that returns
the assets that can be used to pay fees on the runtime where it's
called.
For relays and most system chains this was configured only as the native
asset: ROC and WND.
However, the asset hubs have the asset conversion pallet, which allows
fees to be paid in any asset in a pool with the native one.
This PR adds the list of assets in a pool with the native one to the
return value of this API for the asset hubs.

---------

Co-authored-by: Branislav Kontur <[email protected]>

Includes:
- Fixes for `ci`
- Support to pass a json as arg for `js-script`

Co-authored-by: Bastian Köcher <[email protected]>

### Fork-Aware Transaction Pool Implementation

This PR introduces a fork-aware transaction pool (fatxpool) enhancing
transaction management by maintaining the valid state of txpool for
different forks.

### High-level overview
The high level overview was added to
[`sc_transaction_pool::fork_aware_txpool`](https://github.com/paritytech/polkadot-sdk/blob/3ad0a1b7c08e63a2581595cb2cd55f11ccd60f4f/substrate/client/transaction-pool/src/fork_aware_txpool/mod.rs#L21)
module. Use:
```
cargo  doc --document-private-items -p sc-transaction-pool --open
```
to build the doc. It should give a good overview and nice entry point
into the new pool's mechanics.

<details>
  <summary>Quick overview (documentation excerpt)</summary>

#### View
For every fork, a view is created. The view is a persisted state of the
transaction pool computed and updated at the tip of the fork. The view
is built around the existing `ValidatedPool` structure.

A view is created on every new best block notification. To create a
view, one of the existing views is chosen and cloned.

When the chain progresses, the view is kept in the cache
(`retracted_views`) to allow building blocks upon intermediary blocks in
the fork.

The views are deleted on finalization: views lower than the finalized
block are removed.

The views are updated with the transactions from the mempool—all
transactions are sent to the newly created views.
A maintain process is also executed for the newly created
views—basically resubmitting and pruning transactions from the
appropriate tree route.

##### View store
View store is the helper structure that acts as a container for all the
views. It provides some convenient methods.

##### Submitting transactions
Every transaction is submitted to every view at the tips of the forks.
Retracted views are not updated.
Every transaction also goes into the mempool.

##### Internal mempool
Shortly, the main purpose of an internal mempool is to prevent a
transaction from being lost. That could happen when a transaction is
invalid on one fork and could be valid on another. It also allows the
txpool to accept transactions when no blocks have been reported yet.

The mempool removes its transactions when they get finalized.
Transactions are also periodically verified on every finalized event and
removed from the mempool if no longer valid.

#### Events
Transaction events from multiple views are merged and filtered to avoid
duplicated events.
`Ready` / `Future` / `Inblock` events are originated in the Views and
are de-duplicated and forwarded to external listeners.
`Finalized` events are originated in fork-aware-txpool logic.
`Invalid` events requires special care and can be originated in both
view and fork-aware-txpool logic.

#### Light maintain
Sometime transaction pool does not have enough time to prepare fully
maintained view with all retracted transactions being revalidated. To
avoid providing empty ready transaction set to block builder (what would
result in empty block) the light maintain was implemented. It simply
removes the imported transactions from ready iterator.

#### Revalidation
Revalidation is performed for every view. The revalidation process is
started after a trigger is executed. The revalidation work is terminated
just after a new best block / finalized event is notified to the
transaction pool.
The revalidation result is applied to the newly created view which is
built upon the revalidated view.

Additionally, parts of the mempool are also revalidated to make sure
that no transactions are stuck in the mempool.


#### Logs
The most important log allowing to understand the state of the txpool
is:
```
              maintain: txs:(0, 92) views:[2;[(327, 76, 0), (326, 68, 0)]] event:Finalized { hash: 0x8...f, tree_route: [] }  took:3.463522ms
                             ^   ^         ^     ^   ^  ^      ^   ^  ^        ^                                                   ^
unwatched txs in mempool ────┘   │         │     │   │  │      │   │  │        │                                                   │
   watched txs in mempool ───────┘         │     │   │  │      │   │  │        │                                                   │
                     views  ───────────────┘     │   │  │      │   │  │        │                                                   │
                      1st view block # ──────────┘   │  │      │   │  │        │                                                   │
                           number of ready tx ───────┘  │      │   │  │        │                                                   │
                                numer of future tx ─────┘      │   │  │        │                                                   │
                                        2nd view block # ──────┘   │  │        │                                                   │
                                      number of ready tx ──────────┘  │        │                                                   │
                                           number of future tx ───────┘        │                                                   │
                                                                 event ────────┘                                                   │
                                                                       duration  ──────────────────────────────────────────────────┘
```
It is logged after the maintenance is done.

The `debug` level enables per-transaction logging, allowing to keep
track of all transaction-related actions that happened in txpool.
</details>


### Integration notes

For teams having a custom node, the new txpool needs to be instantiated,
typically in `service.rs` file, here is an example:

https://github.com/paritytech/polkadot-sdk/blob/9c547ff3e36cf3b52c99f4ed7849a8e9f722d97d/cumulus/polkadot-omni-node/lib/src/common/spec.rs#L152-L161

To enable new transaction pool the following cli arg shall be specified:
`--pool-type=fork-aware`. If it works, there shall be information
printed in the log:
```
2024-09-20 21:28:17.528  INFO main txpool: [Parachain]  creating ForkAware txpool.
````

For debugging the following debugs shall be enabled:
```
      "-lbasic-authorship=debug",
      "-ltxpool=debug",
```
*note:* trace for txpool enables per-transaction logging.

### Future work
The current implementation seems to be stable, however further
improvements are required.
Here is the umbrella issue for future work:
- paritytech#5472


Partially fixes: paritytech#1202

---------

Co-authored-by: Bastian Köcher <[email protected]>
Co-authored-by: Sebastian Kunert <[email protected]>
Co-authored-by: Iulian Barbu <[email protected]>

PR moves jobs `build-rustdoc`, `test-doc` and `publish-rustdoc` to GHA.
`publish-rustdoc` was changed so it can publish changes using token from
GH APP.
PR removes `test-rustdoc` because the same command in executed in
`build-rustdoc` and I see no reason to run it twice.

cc paritytech/ci_cd#1006

Bumps [tokio-test](https://github.com/tokio-rs/tokio) from 0.4.3 to
0.4.4.
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/tokio-rs/tokio/commit/3d0d0fd2af9192ca5cf2836451e96dffab68216a"><code>3d0d0fd</code></a>
chore: prepare tokio-test v0.4.4 (<a
href="https://redirect.github.com/tokio-rs/tokio/issues/6400">#6400</a>)</li>
<li><a
href="https://github.com/tokio-rs/tokio/commit/7cfb1007969e3fcb28b03854f3126caeca93932e"><code>7cfb100</code></a>
chore: prepare tokio-stream v0.1.15 (<a
href="https://redirect.github.com/tokio-rs/tokio/issues/6401">#6401</a>)</li>
<li><a
href="https://github.com/tokio-rs/tokio/commit/e37bd6385430620f850a644d58945ace541afb6e"><code>e37bd63</code></a>
io: implement <code>try_new</code> and <code>try_with_interest</code>
for <code>AsyncFd</code> (<a
href="https://redirect.github.com/tokio-rs/tokio/issues/6345">#6345</a>)</li>
<li><a
href="https://github.com/tokio-rs/tokio/commit/c9e75785c84a441199992ed38e49aeba2f061a24"><code>c9e7578</code></a>
sync: remove <code>'static</code> bound on <code>impl Sink for
PollSender</code> (<a
href="https://redirect.github.com/tokio-rs/tokio/issues/6397">#6397</a>)</li>
<li><a
href="https://github.com/tokio-rs/tokio/commit/3141ed62287043b5400e24ac930b002dc7d11d92"><code>3141ed6</code></a>
sync: update watch channel docs (<a
href="https://redirect.github.com/tokio-rs/tokio/issues/6395">#6395</a>)</li>
<li><a
href="https://github.com/tokio-rs/tokio/commit/ea1cfbdb97f524a1ae465c0f5454dd6690dd5e6e"><code>ea1cfbd</code></a>
sync: reorder const_new before new_with (<a
href="https://redirect.github.com/tokio-rs/tokio/issues/6392">#6392</a>)</li>
<li><a
href="https://github.com/tokio-rs/tokio/commit/fb2dc97468fead3c1d318f209a65648e11ade55d"><code>fb2dc97</code></a>
readme: update commit message guidelines (<a
href="https://redirect.github.com/tokio-rs/tokio/issues/6393">#6393</a>)</li>
<li><a
href="https://github.com/tokio-rs/tokio/commit/a3d2548789d22d4bf193a4614f229944270e912c"><code>a3d2548</code></a>
sync: implement <code>Clone</code> for <code>watch::Sender</code> (<a
href="https://redirect.github.com/tokio-rs/tokio/issues/6388">#6388</a>)</li>
<li><a
href="https://github.com/tokio-rs/tokio/commit/b4ab6472de9a0708873c5f14f3b8de03b149a1c5"><code>b4ab647</code></a>
signal: fix typo in argument name (<a
href="https://redirect.github.com/tokio-rs/tokio/issues/6389">#6389</a>)</li>
<li><a
href="https://github.com/tokio-rs/tokio/commit/3133af42e123b9469dad292ae3a090da915d23c5"><code>3133af4</code></a>
runtime: make the <code>enter</code> example deterministic (<a
href="https://redirect.github.com/tokio-rs/tokio/issues/6351">#6351</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/tokio-rs/tokio/compare/tokio-test-0.4.3...tokio-test-0.4.4">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=tokio-test&package-manager=cargo&previous-version=0.4.3&new-version=0.4.4)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Bastian Köcher <[email protected]>
Co-authored-by: Sebastian Kunert <[email protected]>

# Description

Sets the correct `RuntimeFreezeReason` type for
`solochain-template-runtime` configuration of pallet_balances.

## Review Notes

For whatever reason `RuntimeFreezeReason` is currently set to
`RuntimeHoldReason`. This in turn causes problems with variant counting
in `MaxFreezes` and results in pallet_balances integrity tests failing
whenever hold/freeze reasons are added to the runtime.
This fixes it by simply setting `RuntimeFreezeReason` to
`RuntimeFreezeReason` in pallet_balances Config.

Co-authored-by: Bastian Köcher <[email protected]>

# Description
Part of paritytech#3326
Removes pallet::getter from pallet-offences from type `Reports`.
Adds a test to verify that retrieval of `Reports` still works with
storage::getter.

polkadot address: 155YyFVoMnv9BY6qxy2i5wxtveUw7WE1n5H81fL8PZKTA1Sd

---------

Co-authored-by: Shawn Tabrizi <[email protected]>
Co-authored-by: Dónal Murray <[email protected]>

…aritytech#5998)

This PR ensures that the `litep2p.public_addresses()` never grows
indefinitely.
- effectively fixes subtle memory leaks
- fixes authority DHT records being dropped due to size limits being
exceeded
- provides a healthier subset of public addresses to the `/identify`
protocol

This PR adds a new `ExternalAddressExpired` event to the
litep2p/discovery process.

Substrate uses an LRU `address_confirmations` bounded to 32 address
entries.
The oldest entry is propagated via the `ExternalAddressExpired` event
when a new address is added to the list (if capacity is exceeded).

The expired address is then removed from the
`litep2p.public_addresses()`, effectively limiting its size to 32
entries (the size of `address_confirmations` LRU).

cc @paritytech/networking @alexggh

---------

Signed-off-by: Alexandru Vasile <[email protected]>
Co-authored-by: Bastian Köcher <[email protected]>
Co-authored-by: Dmitry Markin <[email protected]>

We should start the `recovery-target` node first, then the
`collator-elastic` node. Also increases the resources available to these
pods.

…tAssets

…fig traits (paritytech#5274)

This feature is part of the upcoming metadata V16. The associated types
of the `Config` trait that require the `TypeInfo` or `Parameter` bounds
are included in the metadata of the pallet. The metadata is not yet
exposed to the end-user, however the metadata intermediate
representation (IR) contains these types.

Developers can opt out of metadata collection of the associated types by
specifying `without_metadata` optional attribute to the
`#[pallet::config]`.

Furthermore, the `without_metadata` argument can be used in combination
with the newly added `#[pallet::include_metadata]` attribute to
selectively include only certain associated types in the metadata
collection.

### API Design

- There is nothing to collect from the associated types:

```rust
#[pallet::config]
pub trait Config: frame_system::Config {
		// Runtime events already propagated to the metadata.
		type RuntimeEvent: From<Event<Self>> + IsType<<Self as frame_system::Config>::RuntimeEvent>;

		// Constants are already propagated.
		#[pallet::constant]
		type MyGetParam2: Get<u32>;
	}
```

- Default automatic collection of associated types that require TypeInfo
or Parameter bounds:

```rust
	#[pallet::config]
	pub trait Config: frame_system::Config {
		// Runtime events already propagated to the metadata.
		type RuntimeEvent: From<Event<Self>> + IsType<<Self as frame_system::Config>::RuntimeEvent>;

		// Constants are already propagated.
		#[pallet::constant]
		type MyGetParam2: Get<u32>;

		// Associated type included by default, because it requires TypeInfo bound.
		/// Nonce doc.
		type Nonce: TypeInfo;

		// Associated type included by default, because it requires
		// Parameter bound (indirect TypeInfo).
		type AccountData: Parameter;

		// Associated type without metadata bounds, not included.
		type NotIncluded: From<u8>;
	}
```

- Disable automatic collection

```rust
// Associated types are not collected by default.
	#[pallet::config(without_metadata)]
	pub trait Config: frame_system::Config {
		// Runtime events already propagated to the metadata.
		type RuntimeEvent: From<Event<Self>> + IsType<<Self as frame_system::Config>::RuntimeEvent>;

		// Constants are already propagated.
		#[pallet::constant]
		type MyGetParam2: Get<u32>;

		// Explicitly include associated types.
		#[pallet::include_metadata]
		type Nonce: TypeInfo;

		type AccountData: Parameter;

		type NotIncluded: From<u8>;
	}
```

Builds on top of the PoC:
paritytech#4358
Closes: paritytech#4519

cc @paritytech/subxt-team

---------

Signed-off-by: Alexandru Vasile <[email protected]>
Co-authored-by: Bastian Köcher <[email protected]>
Co-authored-by: Guillaume Thiolliere <[email protected]>
Co-authored-by: Shawn Tabrizi <[email protected]>

# Description
This PR migrates the staking pallet's benchmarks to the `v2` of pallet
benchmarking tooling provided by
[`frame_benchmarking`](https://github.com/paritytech/polkadot-sdk/tree/master/substrate/frame/benchmarking).

## Integration

N/A

## Review Notes

The PR is straightforward, as were paritytech#1676 , paritytech#1838 and paritytech#1868.

---------

Co-authored-by: Dónal Murray <[email protected]>
Co-authored-by: Shawn Tabrizi <[email protected]>

Bumps [platforms](https://github.com/rustsec/rustsec) from 3.0.2 to
3.4.1.
<details>
<summary>Commits</summary>
<ul>
<li>See full diff in <a
href="https://github.com/rustsec/rustsec/commits">compare view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=platforms&package-manager=cargo&previous-version=3.0.2&new-version=3.4.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Bastian Köcher <[email protected]>

…ntiated (paritytech#6045)

Failed call frames do not produce new return data but still reset it.

---------

Signed-off-by: xermicus <[email protected]>
Co-authored-by: GitHub Action <[email protected]>

PR adds timeouts to some jobs, fixes `node-bench-regression-guard` so it
works on master.

cc paritytech/ci_cd#1063

[Issue paritytech#4762 ](paritytech#4762)

- Creates an enum for passing context of `service_queues` being called
from within `on_initialize` and `on_idle` hooks. Uses a match statement
inside of `service_queues` to continue using the same code, but NOT
throw a `defensive` if being called within `on_idle` hook.
- The issue requested to not throw the `defensive` if being called from
within `on_idle` hook.
- Created the `ServiceQueuesContext` enum to pass as an argument of
`service_queues` when called within the `on_initialize` and `on_idle`
hooks. A match statement was added inside of `service_queues` to
continue to throw the defensive if called from `on_initialize` but NOT
throw the defensive if called from `on_idle`.

---------

Co-authored-by: gotnoshoeson <[email protected]>
Co-authored-by: Bastian Köcher <[email protected]>
Co-authored-by: Bastian Köcher <[email protected]>

)

Bump zombienet version, include updated baseline resources request.

Thx!

Co-authored-by: Bastian Köcher <[email protected]>

Implements [RFC#105](polkadot-fellows/RFCs#105)
which, at the time of this PR, has not been approved yet. Some aspects
might be changed as a result of discussion.

## TODO
- [x] Add new instruction and use it in conversion functions
- [x] Implement in xcm-executor
- [x] Setup for xcm-executor unit tests
- [x] Actual xcm-executor unit tests
  - [x] Happy path
  - [x] Unhappy path
- [x] Emulated tests
  - [x] Asset hub westend
  - [x] Asset hub rococo
- [x] Benchmarks
  - [x] Dummy values
  - [x] Actual benchmarks
- [x] PRDoc

---------

Co-authored-by: command-bot <>
Co-authored-by: Adrian Catangiu <[email protected]>

# Description

I'm unable to build a bridge library due to the errors below, so I am
adding the explicit import to `sp_std::vec`.

## Integration

Projects using it can update their dependency. We are using the branch
`stable2407` (mixed them up in my branch).

## Errors
```
error: cannot find macro `vec` in this scope
  --> /Users/drew/.cargo/git/checkouts/polkadot-sdk-cff69157b985ed76/88c3250/bridges/primitives/header-chain/src/justification/verification/mod.rs:99:19
   |
99 |         let mut route = vec![];
   |                         ^^^
   |
help: consider importing one of these items
   |
23 + use scale_info::prelude::vec;
   |
23 + use sp_std::vec;
   |

error: cannot find macro `vec` in this scope
   --> /Users/drew/.cargo/git/checkouts/polkadot-sdk-cff69157b985ed76/88c3250/bridges/primitives/header-chain/src/justification/verification/optimizer.rs:135:36
    |
135 |         duplicate_votes_ancestries_idxs: vec![],
    |                                          ^^^
    |
help: consider importing one of these items
    |
19  + use scale_info::prelude::vec;
    |
19  + use sp_std::vec;
    |

error: cannot find macro `vec` in this scope
   --> /Users/drew/.cargo/git/checkouts/polkadot-sdk-cff69157b985ed76/88c3250/bridges/primitives/header-chain/src/justification/verification/optimizer.rs:134:21
    |
134 |         extra_precommits: vec![],
    |                           ^^^
    |
help: consider importing one of these items
    |
19  + use scale_info::prelude::vec;
    |
19  + use sp_std::vec;
    |

error: cannot find macro `vec` in this scope
  --> /Users/drew/.cargo/git/checkouts/polkadot-sdk-cff69157b985ed76/88c3250/bridges/primitives/header-chain/src/justification/verification/equivocation.rs:89:27
   |
89 |         let mut equivocations = vec![];
   |                                 ^^^
   |
help: consider importing one of these items
   |
19 + use scale_info::prelude::vec;
   |
19 + use sp_std::vec;
```

---------

Co-authored-by: Bastian Köcher <[email protected]>
Co-authored-by: Serban Iorga <[email protected]>
Co-authored-by: command-bot <>
Co-authored-by: Adrian Catangiu <[email protected]>

…h#5435)

## Changes

Allows one Asset Hub on one side, to register assets on the other Asset
Hub over the bridge.

Rococo <> Ethereum test bridge will be dropped in favor of Westend <>
Ethereum test bridge. This PR also changes emulated tests to simulate
double bridging from Ethereum<>Westend<>Rococo.

## Tests

- [x] e2e test: Westend Asset Hub can register Westend and Ethereum
assets on Asset Hub Rococo
- [x] e2e test: Rococo Asset Hub can register Rococo assets on Asset Hub
Westend
- [x] e2e test (existing): Users on Ethereum can register Ethereum
assets on Asset Hub Westend
- [x] e2e test: transfer Rococo assets from Rococo to Westend and back
- [x] e2e test: transfer Westend assets from Westend to Rococo and back
- [x] e2e test: transfer Ethereum assets (bridged in through Snowbridge)
from Westend to Rococo and back

…paritytech#5804)

Closes paritytech#5705

---------

Co-authored-by: Iulian Barbu <[email protected]>
Co-authored-by: Michal Kucharczyk <[email protected]>

…rococo from release (paritytech#6108)

This PR introduces adjustments to the release pipelines so that it could
be used with the new tags in the form of `poilakdot-stableYYMM(-rcX)` in
addition to the old form of tags like `vX.XX.X`.

Also, the rococo runtime and its parachains are deleted now from the
build and release draft as it is decommissioned and not used any more

`prdoc check -n NNNN` (used in CI) enforces that yaml lists only be used
for lists with length more than one.

Previously this script generated a list no matter how many audiences
were provided, which generated a broken PRDoc when that number was 1.

Reproducing the issue locally:
```
python .github/scripts/generate-prdoc.py --pr 6022 --bump patch --audience runtime_user --force
prdoc check -n 6022
```
Fails on master but passes with this change

Co-authored-by: Bastian Köcher <[email protected]>

Implemented is_trusted_reserve and is_trusted_teleporter API methods. 
Tested them with regular and chopstick tests.
Fixes paritytech#97

---------

Co-authored-by: Francisco Aguirre <[email protected]>

# Description
Update `ext_code_hash` to match
[EIP-1052](https://eips.ethereum.org/EIPS/eip-1052) specs. Since all
possible results are written into output pointer then there's no need
for a return value.

paritytech/revive#77

# Description

closes paritytech#5871

> The chainHead_v1_follow is using unbounded channels to send out
messages on the JSON-RPC connection which may use lots of memory if the
client is slow and can't really keep up with server i.e, substrate may
keep lots of message in memory

This PR changes the outgoing stream to abort and send a `Stop` event
downstream in the case that client doesn't keep up with the producer.

## Integration

*In depth notes about how this PR should be integrated by downstream
projects. This part is mandatory, and should be
reviewed by reviewers, if the PR does NOT have the `R0-Silent` label. In
case of a `R0-Silent`, it can be ignored.*

## Review Notes

- `rpc::Subscription::pipe_from_stream` - now takes `Self` param by
reference, change was made to allow sending events to the `Subscription`
after calls to `pipe_from_stream`.
- `chainhead_follow::submit_events` - now uses `Abortable` stream to end
it early in case
     - connection was closed by the client
     - signal received that subscription should stop 
     - error has occured when processing the events 
     - client can't keep up with the events produced
- TODO: 
  - make the abort logic less hacky

---------

Co-authored-by: Niklas Adolfsson <[email protected]>
Co-authored-by: Alexandru Vasile <[email protected]>

A tiny fix for the `Release - Branch off stable branch` pipeline, that
adds an environment to be able to access secrets

)

# Adding instruction to migrate benchmarking from v1 to v2

Even if the documentation for benchmarking v1 and v2 is clear and
detailed, I feel that adding a migration guide from v1 to v2 would help
doing it quicker.

## Integration
This change only affects documentation, so it does not cause integration
issues.

## Review Notes
I followed the migration procedure I applied in PR
paritytech#6018 . I added
everything from there, but I may be missing some extra steps that are
needed in specific case, so in case you notice something please let me
know.

---------

Co-authored-by: Dónal Murray <[email protected]>