Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
P
polkadot-sdk
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
0
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
parity
Mirrored projects
polkadot-sdk
Commits
6d3ef635
Unverified
Commit
6d3ef635
authored
1 year ago
by
Branislav Kontur
Browse files
Options
Downloads
Patches
Plain Diff
Backport from staging (#2243)
* Updated version according to Cumulus * Updated docs
parent
bdbfb807
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
bridges/docs/polkadot-kusama-bridge-overview.md
+10
-8
10 additions, 8 deletions
bridges/docs/polkadot-kusama-bridge-overview.md
bridges/modules/messages/README.md
+4
-3
4 additions, 3 deletions
bridges/modules/messages/README.md
with
14 additions
and
11 deletions
bridges/docs/polkadot-kusama-bridge-overview.md
+
10
−
8
View file @
6d3ef635
...
...
@@ -25,8 +25,9 @@ You won't be able to directly use bridge hub transactions to send XCM messages o
use other parachains transactions, which will use HRMP to deliver messages to the Bridge Hub. The Bridge Hub will just
queue these messages in its outbound lane, which is dedicated to deliver messages between two parachains.
Our first planned bridge will connect the Polkadot and Kusama Asset Hubs. A bridge between those two parachains would
allow Asset Hub Polkadot accounts to hold wrapped KSM tokens and Asset Hub Kusama accounts to hold wrapped DOT tokens.
Our first planned bridge will connect the Polkadot and Kusama Asset Hubs. A bridge between those two
parachains would allow Asset Hub Polkadot accounts to hold wrapped KSM tokens and Asset Hub Kusama
accounts to hold wrapped DOT tokens.
For that bridge (pair of parachains under different consensus systems) we'll be using the lane 00000000. Later, when
other parachains will join the bridge, they will be using other lanes for their messages.
...
...
@@ -92,13 +93,14 @@ Obviously, there should be someone who is paying relayer rewards. We want bridge
can't use fees for rewards. Instead, the parachains using the bridge, use sovereign accounts on both sides of the bridge
to cover relayer rewards.
Bridged Parachains will have sovereign accounts at bridge hubs. For example, the Kusama Asset Hub will have an account
at the Polkadot Bridge Hub. The Polkadot Asset Hub will have an account at the Kusama Bridge Hub. The sovereign accounts
are used as a source of funds when the relayer is calling the
`pallet_bridge_relayers::claim_rewards`
.
Bridged Parachains will have sovereign accounts at bridge hubs. For example, the Kusama Asset Hub will
have an account at the Polkadot Bridge Hub. The Polkadot Asset Hub will have an account at the Kusama
Bridge Hub. The sovereign accounts are used as a source of funds when the relayer is calling the
`pallet_bridge_relayers::claim_rewards`
.
Since messages lane is only used by the pair of parachains, there's no collision between different bridges. E.g.
Kusama
Asset Hub will only reward relayers that are delivering messages from Kusama Asset Hub. The Kusama Asset Hub sovereign
account
is not used to cover rewards of bridging with some other Polkadot Parachain.
Since messages lane is only used by the pair of parachains, there's no collision between different bridges. E.g.
Kusama
Asset Hub will only reward relayers that are delivering messages from Kusama Asset Hub. The Kusama Asset Hub sovereign
account
is not used to cover rewards of bridging with some other Polkadot Parachain.
### Multiple Relayers and Rewards
...
...
This diff is collapsed.
Click to expand it.
bridges/modules/messages/README.md
+
4
−
3
View file @
6d3ef635
...
...
@@ -28,9 +28,10 @@ Single message lane may be seen as a transport channel for single application (o
time the module itself never dictates any lane or message rules. In the end, it is the runtime developer who defines
what message lane and message mean for this runtime.
In our
[
Kusama<>Polkadot bridge
](
../../docs/polkadot-kusama-bridge-overview.md
)
we are using lane as a channel of
communication between two parachains of different relay chains. For example, lane
`[0, 0, 0, 0]`
is used for Polkadot
<>
Kusama Asset Hub communications. Other lanes may be used to bridge other parachains.
In our
[
Kusama<>Polkadot bridge
](
../../docs/polkadot-kusama-bridge-overview.md
)
we are using lane
as a channel of communication between two parachains of different relay chains. For example, lane
`[0, 0, 0, 0]`
is used for Polkadot
<>
Kusama Asset Hub communications. Other lanes may be used to
bridge other parachains.
## Message Workflow
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment