Improve RPC Chain version mismatch error message #2021
Merged
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
A significant number of developers, especially those new to Subnet-EVM or Precompile-EVM, encounter the following error:
Feedback from developer chats indicates confusion and uncertainty about how to address this error. It's particularly prevalent when a new version of AvalancheGo is released, but a corresponding update for Subnet-EVM that supports the latest RPC Chain version hasn't been rolled out yet.
How this works
Extend the error message:
This PR enhances the error message by providing:
By doing so, we aim to reduce developer friction and improve their experience when encountering version mismatches.
How this was tested
To ensure the effectiveness of this change, we tested AvalancheGo using VM binaries that had differing RPC Chain versions.