Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support multiple refund-message-delivery-cost-at-target-chain signed extensions #1667

Closed
svyatonik opened this issue Nov 29, 2022 · 1 comment
Closed

Support multiple refund-message-delivery-cost-at-target-chain signed extensions #1667

svyatonik opened this issue Nov 29, 2022 · 1 comment
Assignees
@serban300
Labels
P-Runtime
Milestone
Nice To Have

Comments

@svyatonik
Copy link
Contributor

#1657 introduces new signed extension for refunding message relayers at the target chain (RefundRelayerForMessagesFromParachain). The issue is that it may only work with single bridge (single set of pallet_bridge_grandpa::Pallet + pallet_bridge_parachains::Pallet + pallet_bridge_messages::Pallet). We need to fix it to support multiple on-chain bridges.

It may be done using approach similar to what @serban300 has done with our other extensions (

parity-bridges-common/bin/runtime-common/src/lib.rs

Line 79 in 8b50630

macro_rules! generate_bridge_reject_obsolete_headers_and_messages {
).
@svyatonik svyatonik added this to the Nice To Have milestone Nov 29, 2022
@serban300 serban300 self-assigned this Jan 23, 2023
This was referenced Feb 13, 2023
Merged
Merged
@serban300
Copy link
Collaborator

Resolved via #1895

svyatonik pushed a commit that referenced this issue Jul 17, 2023
@shawntabrizi
Companion for #12283 (Anon -> Pure Proxy) (#1667)
142cdfa 
* anon -> pure

* fn pure -> fn create_pure

* update lockfile for {"polkadot", "substrate"}

Co-authored-by: parity-processbot <>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@serban300 serban300

Labels
P-Runtime
Projects
None yet
Milestone
Nice To Have
Development

No branches or pull requests
2 participants
@svyatonik @serban300