Correct casing in UniversalRouter addresses Base – prevent invalid checksum in IDE #1058
Conversation
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
|
@ryanshahine is attempting to deploy a commit to the Uniswap Team on Vercel. A member of the Team first needs to authorize it. |
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.
Description
This PR fixes incorrect address casing for UniversalRouter contract entries in the Base deployments documentation.
Some IDEs and linters flagged the previous addresses as invalid due to incorrect checksum casing.
Updated both occurrences to match the proper EIP-55 checksum format.
Type(s) of changes
Motivation for PR
Incorrect casing in the UniversalRouter addresses caused checksum validation errors in IDEs and tools referencing the Base deployment documentation.
This update ensures addresses are compliant and recognized correctly across environments.
How Has This Been Tested?
Verified that the corrected addresses pass EIP-55 checksum validation and no longer trigger IDE warnings or formatting errors.
Applicable screenshots
N/A
Follow-up PR
None expected — this resolves the checksum inconsistency in the Base deployments reference.