Skip to content

Conversation

@lexnv
Copy link
Contributor

@lexnv lexnv commented Nov 24, 2025

This PR configures the AssetHubKusama runtime to utilize elastic scaling with 3 cores.

  • the runtime is prepared for elastic scaling with expected 2s block times
  • 3 cores will be assigned to AHK when we have sufficient confidence in testing stacks
  • AHK should function similarly with expected 6s block times until cores are assigned

cc @skunert @sandreim

@lexnv lexnv changed the title ahk: Enable ElasticScaling with 3 cores on asset hub kusama ahk: Prepare ElasticScaling with 3 cores on asset hub kusama Nov 24, 2025
Signed-off-by: Alexandru Vasile <[email protected]>
@github-actions
Copy link

Review required! Latest push from author must always be reviewed

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Found one issue regarding a duplicated constant definition which could lead to future maintenance problems.

@sigurpol
Copy link
Contributor

sigurpol commented Dec 4, 2025

A small followup on staking side: paritytech/polkadot-sdk#10311 has been now merged (cc @Ank4n ).
Which means we can target for #1018 and #10311 the same release.
#10311 has also been requested to be audited.
Which branches should we backport 10311 to? 2509 and 2512 or also 2507 ? Thanks! Feel free to ping @Ank4n and myself to coordinate the release at any point in time 🙇

@Ank4n
Copy link
Contributor

Ank4n commented Dec 4, 2025

A small followup on staking side: paritytech/polkadot-sdk#10311 has been now merged (cc @Ank4n ). Which means we can target for #1018 and #10311 the same release. #10311 has also been requested to be audited. Which branches should we backport 10311 to? 2509 and 2512 or also 2507 ? Thanks! Feel free to ping @Ank4n and myself to coordinate the release at any point in time 🙇

To give more context: multi-cores can lead to shorter eras (good to avoid but not disaster). The #10311 would mitigate that (and can go to Kusama before audit is done). I will make a PR with the changes to the runtime once its backported to 2507.

@lexnv
Copy link
Contributor Author

lexnv commented Dec 5, 2025

Thanks @sigurpol and @Ank4n 🙏

Indeed, let's align and include both PRs:

in a release. It looks like more tests are failing and we really need paritytech/polkadot-sdk#10541 to unblock the CI here 🙏

github-merge-queue bot pushed a commit to paritytech/polkadot-sdk that referenced this pull request Dec 10, 2025
…ata (#10541)

This PR ensures that the parachains test-utils crate has 2 relay parent
descendants for testing purposes.

Effectively fixes a panic because we missed this mock data for chains
that started with `RP_offset > 0`:

```
 Unable to verify provided relay parent descendants. expected_rp_descendants_num: 1 error: InvalidNumberOfDescendants { expected: 2, received: 0 }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
```

Detected in:
-
https://github.com/polkadot-fellows/runtimes/actions/runs/19857064730/job/56897622908?pr=1018

Unblocks:
- polkadot-fellows/runtimes#1018

Inspired by a similar fix I've introduced in:
- #9880

---------

Signed-off-by: Alexandru Vasile <[email protected]>
Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Bastian Köcher <[email protected]>
@lexnv lexnv changed the title ahk: Prepare ElasticScaling with 3 cores on asset hub kusama asset-hub-kusama: Prepare ElasticScaling with 3 cores on asset hub kusama Dec 10, 2025
paritytech-release-backport-bot bot pushed a commit to paritytech/polkadot-sdk that referenced this pull request Dec 10, 2025
…ata (#10541)

This PR ensures that the parachains test-utils crate has 2 relay parent
descendants for testing purposes.

Effectively fixes a panic because we missed this mock data for chains
that started with `RP_offset > 0`:

```
 Unable to verify provided relay parent descendants. expected_rp_descendants_num: 1 error: InvalidNumberOfDescendants { expected: 2, received: 0 }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
```

Detected in:
-
https://github.com/polkadot-fellows/runtimes/actions/runs/19857064730/job/56897622908?pr=1018

Unblocks:
- polkadot-fellows/runtimes#1018

Inspired by a similar fix I've introduced in:
- #9880

---------

Signed-off-by: Alexandru Vasile <[email protected]>
Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Bastian Köcher <[email protected]>
(cherry picked from commit 0f28d81)
@lexnv
Copy link
Contributor Author

lexnv commented Dec 12, 2025

Have rebased this PR on top of:

The changes added from my part are limited to:

  • elastic scaling enablement on ahk
  • bumping xcm-emulator: 9e5030f (which is relevant for passing tests)

@lexnv lexnv changed the title asset-hub-kusama: Prepare ElasticScaling with 3 cores on asset hub kusama asset-hub-kusama: Prepare ElasticScaling with 3 cores on asset hub kusama and enable buffered election export Dec 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants