mirror of https://github.com/pezkuwichain/pezkuwi-subxt.git synced 2026-05-07 07:18:03 +00:00

Files

T

Svyatoslav Nikolsky 948f80733e Update bridges subtree (#2903 )

* Squashed 'bridges/' changes from 0417308a48..3c4ada921b

3c4ada921b Update dependecies (#2277) (#2281)
3e195c9e76 GRANDPA: optimize votes_ancestries when needed (#2262) (#2264)
7065bbabc6 Implement RuntimeDebug for GrandpaJustification (#2254)
8c9e59bcbc Define generate_grandpa_key_ownership_proof() (#2247) (#2248)
0b46956df7 Deduplicate Grandpa consensus log reading logic (#2245) (#2246)
96c9701710 Fix deps from Cumulus (#2244)

git-subtree-dir: bridges
git-subtree-split: 3c4ada921bbdbdba945c3aa85d76ce316f7baab3

* removed extra files

* post-merge fixes

* also post-merge fixes

2023-07-19 19:29:12 +03:00

src

Update bridges subtree (#2903 )

2023-07-19 19:29:12 +03:00

Cargo.toml

Bump scale-info from 2.8.0 to 2.9.0 (#2815 )

2023-07-03 23:52:08 +02:00

README.md

Initial version of bridging pallets as git subtree (#2458 )

2023-05-04 06:36:58 +00: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.