Skip to content

Per-lane rewards in pallet-bridge-relayers #1665

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.

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

Merged
merged 5 commits into from
Nov 28, 2022
Merged

Conversation

svyatonik
Copy link
Contributor

addressing #1654 (comment) (see #1654 (comment)) and also required for the #1657

The idea is that every "bridge" (pair of XCM source+destination) will use dedicated lane. Per-lane rewards will be paid using sovereign accounts of corresponding parachains at bridge hubs. The bad thing is that now the configuration will be static and if we'll ever need a way to open new "bridges" without changing the code + upgrading runtimes, we'll need some better way. I'm leaving it for future PRs

@svyatonik svyatonik added P-Runtime P-Message Delivery PR-breaksruntime A PR that is going to break runtime bridge compatibility. We need to be careful with upgrade. labels Nov 28, 2022
@svyatonik svyatonik enabled auto-merge (squash) November 28, 2022 13:41
@svyatonik svyatonik merged commit 8b50630 into master Nov 28, 2022
@svyatonik svyatonik deleted the per-lane-rewards branch November 28, 2022 13:49
serban300 pushed a commit to serban300/parity-bridges-common that referenced this pull request Mar 27, 2024
* per-lane rewards in pallet-bridge-relayers

* add lane id to RewardPaid event

* clippy

* fix benchmarks
serban300 pushed a commit to serban300/parity-bridges-common that referenced this pull request Apr 8, 2024
* per-lane rewards in pallet-bridge-relayers

* add lane id to RewardPaid event

* clippy

* fix benchmarks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P-Message Delivery P-Runtime PR-breaksruntime A PR that is going to break runtime bridge compatibility. We need to be careful with upgrade.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants