You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So bridge hub will have our signed extensions that reject obsolete transactions and pay reward/slash relayers. The obsolete-check reads the same storage entries as the call itself does, so we assume it brings no additional weight (it does, but not that much). However, the post_dispatch may add/update entries of the pallet-bridge-relayers rewards map. So we should add this weight to our call weights (delivery and confirmation). Maybe something as simple as DbWeight.reads_writes(1, 1).set_proof_size(<proof-size-that-we-may-get-from-relayers-pallet-benchmarks>). But maybe some benchmark is ok too.
The text was updated successfully, but these errors were encountered:
So bridge hub will have our signed extensions that reject obsolete transactions and pay reward/slash relayers. The obsolete-check reads the same storage entries as the call itself does, so we assume it brings no additional weight (it does, but not that much). However, the
post_dispatch
may add/update entries of thepallet-bridge-relayers
rewards map. So we should add this weight to our call weights (delivery and confirmation). Maybe something as simple asDbWeight.reads_writes(1, 1).set_proof_size(<proof-size-that-we-may-get-from-relayers-pallet-benchmarks>)
. But maybe some benchmark is ok too.The text was updated successfully, but these errors were encountered: