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

Files

T

Svyatoslav Nikolsky ec9cd8ddb0 Remove chain-specific dependencies from crates that will be used in Cumulus (#1783 )

* leave-modules.sh

* remove bp-rialto dependency from bp-relayers

* update leave-modules.sh

* fix Cargo.toml of pallet-bridge-relayers

* update leave-modules.sh

* remove bp-rialto and millau-runtime frombridge-runtime-common Cargo.toml

* update leave-modules.sh

* remove chain dependencies from bridge-runtime-common crate

* fix tests

* cleanup script

* rename script

* kind of success message

* remove leave-modules.sh

* use TargetHeaderChainAdapter and SourceHeaderChainAdapter in our testnets

* update script

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

src

Relayer reward metric (#1742 )

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

Cargo.toml

Remove chain-specific dependencies from crates that will be used in Cumulus (#1783 )

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.