Implement Standalone Hyperbridge Proof Verification with EVM Log Emission Using Inherent #574
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a dedicated system for verifying Hyperbridge parachain proofs submitted via inherents and subsequently emitting an EVM-compatible log through pallet-revive.
The primary goal is to provide a standalone mechanism for verifying Hyperbridge consensus updates directly within the runtime while maintaining compatibility with the relayers and indexer that expects EVM log events (specifically StateMachineUpdated). Existing ISMP mechanisms were deemed unsuitable as we needed this inherent and inherent handler to reside upstream (in Polkadot SDK) without depending on ISMP pallets.
Implementation Details:
hyperbridge-ismp-parachain:InherentHandlertrait that resides inpallet-revivefor processing system log message so as to emit EVM log events.hyperbridge-ismp-parachain-inherent:HyperbridgeVerifierApiruntime API trait to allow querying the runtime for theHyperbridgeParaIdandcurrent_relay_chain_state.HyperbridgeConsensusProofdata under theINHERENT_IDENTIFIER(b"hypbridg").companion
introduce inherent handler in pallet revive paritytech/polkadot-sdk#10140