pezkuwichain
bd2d665c4e
- Fix serde optional dependency issues by adding dep:serde to serde features (24 crates) - Run zepter to propagate runtime-benchmarks, std, try-runtime, serde, experimental, with-tracing, tuples-96 features - Regenerate umbrella crate with proper feature propagation - Format all TOML files with taplo This resolves check-umbrella and check-zepter CI failures.
Bridge Relayers Pezpallet
The pezpallet 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 pezpallet 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 pezpallet 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 <> PezkuwiChain bridge documentation.