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
The existing Polygon consensus client tries to use the clique protocol on Bor (Polygon's execution layer) as a source for finality proofs. In practice, these proofs are unreliable and prone to frequent reorgs.
Rather than relying entirely on Bor, a polygon core dev has pointed out that we should instead rely on Heimdall (Polygon's consensus layer) for finality proofs. This is possible with the recent introduction of PIP-11. A protocol in which Heimdall's validators finalize Bor's blocks. Heimdall itself is a cosmos-sdk chain which uses a tendermint-based consensus mechanism.
This is a tracking issue for Polygon's deterministic finality mechanism on Hyperbridge
Tendermint consensus proof verifier
Tendermint consensus Prover
Integration with the Tesseract consensus relayer
ISMP consensus client implementation
The text was updated successfully, but these errors were encountered:
The existing Polygon consensus client tries to use the clique protocol on Bor (Polygon's execution layer) as a source for finality proofs. In practice, these proofs are unreliable and prone to frequent reorgs.
Rather than relying entirely on Bor, a polygon core dev has pointed out that we should instead rely on Heimdall (Polygon's consensus layer) for finality proofs. This is possible with the recent introduction of PIP-11. A protocol in which Heimdall's validators finalize Bor's blocks. Heimdall itself is a cosmos-sdk chain which uses a tendermint-based consensus mechanism.
This is a tracking issue for Polygon's deterministic finality mechanism on Hyperbridge
The text was updated successfully, but these errors were encountered: