mirror of https://github.com/pezkuwichain/pezkuwi-subxt.git synced 2026-04-26 04:07:57 +00:00

Files

T

Serban Iorga 2c26640ac3 polkadot-staging branch: Use polkadot-sdk dependencies (#2524 )

* Use polkadot-sdk dependencies

* Fix ring-proof ref

* Fix Beefy

* Fix imports

* Simple runtimes fixes

* Fix substrate-relay

* Add ParaAssignmentProvider for Rialto

* Rialto chain_spec fix

* Fix Rialto build

* Fix Rialto pvf workers

* Allow rialto-parachain deprecated features warnings

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

src

Backport polkadot-sdk changes to polkadot-staging (#2518 )

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

Cargo.toml

polkadot-staging branch: Use polkadot-sdk dependencies (#2524 )

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.