e2e: Ensure pre-funded test keys are also funded on the C-Chain #1880
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
Previously pre-funded keys were only funded on the X-Chain. This change ensures that pre-funded keys are also funded on the C-Chain to ensure C-Chain tests have the same isolation guarantees.
How this works
The keys generated with a testnet network are funded in the C-Chain genesis.
How this was tested
CI will ensure that this doesn't break anything. #1871 will validate that C-Chain funding was successful.
TODO