-
Notifications
You must be signed in to change notification settings - Fork 282
fix(system-contract): Ensure header.coinbase is not set #1127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
WalkthroughThis pull request updates the consensus system contract and versioning. In the consensus package, the Changes
Sequence Diagram(s)sequenceDiagram
participant BH as BlockHeader
participant SC as SystemContract
BH->>SC: Call Prepare()
SC-->>BH: Zeroes Coinbase, Nonce, MixDigest & sets Difficulty = 1
BH->>SC: Call Finalize()
SC-->>BH: Sets Root from intermediate state and calculates UncleHash
BH->>SC: Call FinalizeAndAssemble()
SC-->>BH: Uses pre-set Root (redundant assignment removed)
Suggested labels
Suggested reviewers
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (2)
✅ Files skipped from review due to trivial changes (1)
⏰ Context from checks skipped due to timeout of 90000ms (1)
🔇 Additional comments (4)
✨ Finishing Touches
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
1. Purpose or design rationale of this PR
Coinbase must be empty so that L1 follower nodes can reconstruct block hashes.
2. PR title
Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:
3. Deployment tag versioning
Has the version in
params/version.go
been updated?4. Breaking change label
Does this PR have the
breaking-change
label?Summary by CodeRabbit