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
Implement a BEEFY consensus light client pallet. Since BEEFY finality proofs should be much smaller than GRANDPA's (see current pallet-bridge-grandpa), we should be able to reduce the bridge operational costs significantly.
BEEFY payload is expected to contain a MMR root hash (or MMB, see paritytech/grandpa-bridge-gadget#198) we should also be able to efficiently proof anything from the entire blockchain history, not just the latest state.
Ideally if both pallet-bridge-grandpa and pallet-bridge-beefy shared the same external interface for proof verification so that they can be re-used by any delivery mechanism (see #2481 & #215)
The issue is both about the Runtime part and the Relayer part, but in the future it should be split.
The text was updated successfully, but these errors were encountered:
Implement a BEEFY consensus light client pallet. Since BEEFY finality proofs should be much smaller than GRANDPA's (see current
pallet-bridge-grandpa
), we should be able to reduce the bridge operational costs significantly.BEEFY payload is expected to contain a MMR root hash (or MMB, see paritytech/grandpa-bridge-gadget#198) we should also be able to efficiently proof anything from the entire blockchain history, not just the latest state.
Ideally if both
pallet-bridge-grandpa
andpallet-bridge-beefy
shared the same external interface for proof verification so that they can be re-used by any delivery mechanism (see #2481 & #215)The issue is both about the Runtime part and the Relayer part, but in the future it should be split.
The text was updated successfully, but these errors were encountered: