Contract tx Text & Single Consensus Client Approach#52
Merged
svlachakis merged 5 commits intonethermindfrom Jan 12, 2026
Merged
Contract tx Text & Single Consensus Client Approach#52svlachakis merged 5 commits intonethermindfrom
svlachakis merged 5 commits intonethermindfrom
Conversation
This was referenced Jan 8, 2026
wurdum
approved these changes
Jan 9, 2026
Collaborator
wurdum
left a comment
There was a problem hiding this comment.
I thought we've deprecated these env vars in favor of cmd args.
Also, makes sense to consider the moment when we migrate to Nitro's RPC implementation that also relies on cmd args.
Author
|
@wurdum yeah they are wrong I'll fix them |
AnkushinDaniil
approved these changes
Jan 12, 2026
svlachakis
added a commit
that referenced
this pull request
Jan 12, 2026
Fixes Closes NethermindEth/nethermind-arbitrum#539 depends on : #52 & NethermindEth/nethermind-arbitrum#540
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.
Fixes Closes NethermindEth/nethermind-arbitrum#537
The single consensus node approach with
WithExecutionClientMode(ExecutionClientModeComparison)works because bothgethandNethermindexecution clients start from a common genesis state with the pre-funded account and receive identical block inputs from the same consensus node, ensuring they execute the exact same transactions. The two-node replica approach fails becausegethwhich has already executed transactions likeTransferBalanceis causing state divergence and different block hashes.This approach cannot be unified for all tests, but is necessary for this one or other similar tests
This approach Flow: L1 Message → Consensus Layer → Both Execution Clients