mirror of https://github.com/pezkuwichain/pezkuwi-subxt.git synced 2026-04-28 07:27:55 +00:00

Files

T

Branislav Kontur 8b1e14658e Pokladot sdk backport to staging (#2746 )

* Bump to `polkadot-sdk` master `ebe2aad6f0ae576a0e176f38a084fe7579f936dd`

* align with others

* Backport xcm version stuff from `polkadot-sdk`

* Backport Slava's commit from `polkadot-sdk`

* Workspace clippy as `polkadot-sdk` does

* Make submodules use workspace lints

* Add Bridges clippy addons to workspace lints

* Looks like we dont need extra clippy addons anymore?

2024-04-10 10:28:37 +02:00

src

Porting changes from polkadot-sdk to polkadot-staging - before update subtree with removed wococo stuff (#2696 )

2024-04-10 10:28:37 +02:00

Cargo.toml

Pokladot sdk backport to staging (#2746 )

2024-04-10 10:28:37 +02:00

README.md

Crate-level documentation on finality relays and relayers pallet (#1773 )

2024-04-10 10:28:37 +02:00

README.md

Bridge Relayers Pallet

The pallet serves as a storage for pending bridge relayer rewards. Any runtime component may register reward to some relayer for doing some useful job at some messages lane. Later, the relayer may claim its rewards using the claim_rewards call.

The reward payment procedure is abstracted from the pallet code. One of possible implementations, is the PayLaneRewardFromAccount, which just does a Currency::transfer call to relayer account from the relayer-rewards account, determined by the message lane id.

We have two examples of how this pallet is used in production. Rewards are registered at the target chain to compensate fees of message delivery transactions (and linked finality delivery calls). At the source chain, rewards are registered during delivery confirmation transactions. You may find more information about that in the Kusama <> Polkadot bridge documentation.