aptos: set fork-choice to height#237
Merged
Merged
Conversation
The Aptos REST head-poll path carries synthetic height-encoded block ids (no real block hashes), so quorum-based fork choice can't compare hashes - pick heads by height, as Aztec and Kadena do. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Aptos head events in nodecore use synthetic, height-encoded block ids — the REST head-poll path exposes no usable parent hash, so hash-based (quorum) fork choice can't work. Set
fork-choice: heightfor the Aptos protocol, same as Aztec and Kadena.Follow-up to #235; surfaced in the review of drpcorg/nodecore#237 (parent-hash discussion).
🤖 Generated with Claude Code