Skip to content

Conversation

@dmitry-markin
Copy link
Contributor

@dmitry-markin dmitry-markin commented Jul 3, 2025

This merges commit ebebf30 into main branch. This is the commit most of the current work is based on, and merging it should bring us closer to working on the main branch.

The diverging changes on main (as compared to ebebf30) should not bring any conflicts:

  • 2024-10-29 52d9260 disable dependabot
  • 2024-10-30 a0e1bbc edit issue template
  • 2024-11-15 fd079b8 ci: Upgrade actions/upload-artifact and actions/download-artifact to v4

There are no other changes on main compared to ebebf30.

This PR also:

  1. Deprecates toolchain override in order to build on stable Rust.
  2. Updates GitHub workflow to run cargo check on Parity CI container image with Rust version used in polkadot-sdk.

svyatonik and others added 30 commits September 7, 2023 12:49
git-subtree-dir: bridges
git-subtree-split: f346243f6d9da686e47f3c6e9e2d9a286b831dd4
As long as the account has keys to purge.

This effectively allows members of the validator set to step back, as
validators will only be included in the real validator set if they have
provided session keys.
And decrement when their authorization is removed, so the account in
frame_system gets cleaned up.
bf5b4cc1 Add polkadot bulletin chain primitives (#2542)

git-subtree-dir: bridges
git-subtree-split: bf5b4cc18c0ceaed308827627dd4effa5fd68c4a
aa1cf85d fix compilation
262e79fa RefundBridgedGrandpaMessages to refund transaction costs for messages coming to/from bridged standalone/relay chain (#2566)
50c33312 added POLKADOT_BULLETIN_CHAIN_ID constant
e4a52cba prepare refund extension infra to add refund extension for messages from standalone chain (#2558)
a7706c4a Add relays that will be used in Polkadot Bulletin <> Polkadot.BH bridge (#2556)
52d95e5a Polkadot Bulletin Chain client (#2552)
979acf3c instead of requiring sp_std::vec::Vec import when using runtime API generation macro, let's use full type path directly in macro (#2551)

git-subtree-dir: bridges
git-subtree-split: aa1cf85dd90c029b5c5cb8352be43680847595cc
* Squashed 'bridges/' content from commit f346243f

git-subtree-dir: bridges
git-subtree-split: f346243f6d9da686e47f3c6e9e2d9a286b831dd4

* add a BRIDGES.md document

* brides -> bridges

* trigger CI

* Revert "trigger CI"

This reverts commit a4390dc.

* try sudo apt-get update
* add basic XCM configuration

* and lost changes from Cargo.toml

* allow all calls through the bridge

* remove TODO and keep using root to dicspatch incoming calls

* improve matching

* Update runtime/src/xcm_config.rs

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

* Update runtime/src/xcm_config.rs

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

* Update runtime/src/xcm_config.rs

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

* UniversalAliases + WithComputedOrigin

* added TODO

* Update runtime/src/xcm_config.rs

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

* changed expected_message_from_kawabunga_passes_barrier to match real execution params

---------

Co-authored-by: Branislav Kontur <[email protected]>
* updating bridges subtree + remove extra folders

* update BRIDGES.md

* added basic (unworking) bridge configuration

* and lost related changes from node

* also lost changes from Cargo.toml

* removed NeverSentMessage for now
* add RPC required for bridges relay

* apply review suggestions
@dmitry-markin
Copy link
Contributor Author

The CI step Cargo check (benchmarking) that checks the node with --features=runtime-benchmarks is failing, but I think we can leave it as a follow-up.

Copy link
Contributor

@georgepisaltu georgepisaltu left a comment

Choose a reason for hiding this comment

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

Looks good but can you also port this change from the george-update branch please?

Signed-off-by: georgepisaltu <[email protected]>
Copy link
Contributor

@antkve antkve left a comment

Choose a reason for hiding this comment

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

LGTM. My commits revert the switch from rococo to polkadot, but this should be easy to merge into subsequent changes to this branch.

@antkve
Copy link
Contributor

antkve commented Jul 3, 2025

The CI step Cargo check (benchmarking) that checks the node with --features=runtime-benchmarks is failing, but I think we can leave it as a follow-up.

error:#[no_mangle] cannot be used on internal language items
Sounds like we need to use rustc 1.79.0 or .84.1 instead of 1.75.0 to compile here?

@dmitry-markin
Copy link
Contributor Author

error:#[no_mangle] cannot be used on internal language items Sounds like we need to use rustc 1.79.0 or .84.1 instead of 1.75.0 to compile here?

Tried with rust 1.88.0 (latest stable) & 1.90.0 (latest nightly), but the error is the same.

@dmitry-markin
Copy link
Contributor Author

dmitry-markin commented Jul 3, 2025

Sounds like we need to use rustc 1.79.0 or .84.1 instead of 1.75.0 to compile here?

Nice catch, thanks! Updated CI image to 1.84.1 to match the one used in polkadot-sdk.

@antkve
Copy link
Contributor

antkve commented Jul 3, 2025

Think this ^ is needed to stop it upgrading to stable during install

@antkve
Copy link
Contributor

antkve commented Jul 3, 2025

Hmm, rust version is correct now but benchmarking still not building. Think we should leave this to its own issue since it looks like it's just a whole bunch of errors caused by the benchmarking code not being updated with the polkadot-sdk version change.

@dmitry-markin
Copy link
Contributor Author

The issue for fixing benchmarking: #15

@dmitry-markin
Copy link
Contributor Author

Think this ^ is needed to stop it upgrading to stable during install

Honestly I don't know what is better — upgrade Rust as one of CI steps, or use Rust from the container. Let's keep the latter, but keep in mind we will need to manually update the version to follow polkadot-sdk CI to not run into weird errors.

@dmitry-markin dmitry-markin merged commit 194c3c2 into main Jul 4, 2025
3 of 4 checks passed
@dmitry-markin dmitry-markin deleted the common-base branch July 4, 2025 08:52
mudigal added a commit that referenced this pull request Jan 30, 2026
- Add authorize_account_for_size() convenience method that estimates and authorizes in one call
- Add signer_account() method to TransactionSubmitter trait to derive account from signer
- Update AsyncBulletinClient to automatically use signer's account if not explicitly set
- Clarify authorization documentation: mention Root/sudo requirement and no fees
- Clarify estimate_authorization helper purpose in docs

Addresses franciscoaguirre's comments:
- Comment #15: API that calls estimation underneath
- Comments #16/#17: Get account from keypair/signer automatically
- Comment #11: Clarify 'required values' in authorization docs
- Comment #14: Mention Root requirement and no fees for authorization
x3c41a pushed a commit that referenced this pull request Feb 1, 2026
- Add authorize_account_for_size() convenience method that estimates and authorizes in one call
- Add signer_account() method to TransactionSubmitter trait to derive account from signer
- Update AsyncBulletinClient to automatically use signer's account if not explicitly set
- Clarify authorization documentation: mention Root/sudo requirement and no fees
- Clarify estimate_authorization helper purpose in docs

Addresses franciscoaguirre's comments:
- Comment #15: API that calls estimation underneath
- Comments #16/#17: Get account from keypair/signer automatically
- Comment #11: Clarify 'required values' in authorization docs
- Comment #14: Mention Root requirement and no fees for authorization
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.

9 participants