Add C-Chain EVM workload to Antithesis tests#5228
Draft
Conversation
DracoLi
force-pushed
the
dl/antithesis-cchain-workload
branch
5 times, most recently
from
f43f9de to
6effaad
Compare
DracoLi
force-pushed
the
dl/antithesis-cchain-workload
branch
from
6effaad to
893df79
Compare
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.
Why this should be merged
Scheduled Antithesis runs exercise Subnet-EVM workloads but not the C-Chain, which is a coverage gap for one of the most used chains.
Fixes #5188
How this works
The Antithesis avalanchego harness already randomizes P/X Chain issue/verify flows; this adds the same style of branch for C-Chain under the existing fault injection.
Each worker has a deterministic C-Chain key. Everyone except the genesis-funded worker gets a one-time AVAX top-up on C-Chain from that funder. The flow signs a small dynamic-fee self-transfer (RPC-suggested tip and base fee) and sends it with SendTransaction.
After inclusion, we open each node’s C-Chain JSON-RPC (/ext/bc/C/rpc), wait for a receipt, and require success on every URI so the cluster agrees; Antithesis reachability is recorded when that passes.
How this was tested
Tested via a 5 hour manual Antithesis run that included these changes.
Need to be documented in RELEASES.md?
No