Historical replay 4: support in-shard transfer transaction#15
Draft
syntrust wants to merge 1 commit into
Draft
Conversation
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
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.
Summary
This PR extends
qkc-history-replay-3with the first ordinary transaction replay path for historical QKC verification.It adds PyQuarkChain typed transaction envelope parsing, embedded EVM RLP decoding, sender recovery, and historical transaction validation for legacy, typed, and EIP-155 signing modes. The verifier now supports minimal in-shard default-QKC transfer execution, including nonce updates, gas precharge/refund, miner fee accounting, reward-tax-aware coinbase handling, and block
gasUsedchecks.It also expands cluster config parsing for replay-related fields, documents the current supported scope in
quarkchain/replay/README.md, and adds tests for transaction parsing, signing validation, and minimal transfer replay.Unsupported execution paths remain explicit, including contract creation/calls, non-empty data, cross-shard ordinary transactions, non-default tokens, gas-bearing x-shard receives, and receipt/meta-root verification.
Tests
The following replay range includes height
191, which contains the first supported ordinaryin-shard transfer transaction in the local PyQuarkChain mainnet DB sample.