This repository was archived by the owner on Jul 15, 2025. It is now read-only.
Query Heimdall with tendermint-rpc #1290
Unanswered
royvardhan
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm developing a verifier that integrates with Peppermint and standard tendermint using the
tendermint-rpc
crate to fetch headers and consensus proofs, then delegates verification totendermint-light-client-verifier
. You can see my implementation here: https://github.com/polytope-labs/hyperbridge/pull/448/filesCurrent Implementation:
I'm querying the Heimdall RPC endpoint at
https://polygon-heimdall-rpc.publicnode.com:443
. Since there were response field mismatches between Heimdall's format and standard Tendermint types, I created a custom "peppermint client" to transform the responses for heimdall.Issues I'm Facing:
Hash Mismatches: During verification, I'm encountering hash validator mismatches that cause my tests to fail. This suggests the response transformation or verification process has compatibility issues.
Response Format Compatibility: The field mismatches between Heimdall and standard Tendermint formats required custom transformation logic.
Questions:
What are the known differences between Heimdall's RPC responses and standard Tendermint that could cause hash mismatches during verification? Do I need to handle hashing differently in the verifier?
Is there an established crate or library specifically designed for handling Peppermint/Heimdall RPC responses that would eliminate the need for custom transformation logic?
Additionally, what's the recommended approach for integrating
tendermint-light-client-verifier
with Polygon's Heimdall consensus layer while maintaining compatibility?Beta Was this translation helpful? Give feedback.
All reactions