changing native token address standard [SLT-210] #3157
Conversation
WalkthroughThe changes involve the introduction of a new constant, Changes
Possibly related PRs
Suggested labels
Suggested reviewers
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
Defi-Moses
changed the title
Deploying sanguine-fe with
|
| Latest commit: |
a415529
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://93fb17aa.sanguine-fe.pages.dev |
| Branch Preview URL: | https://feat-rest-api-native-token.sanguine-fe.pages.dev |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3157 +/- ##
=============================================
Coverage 37.95009% 37.95009%
=============================================
Files 418 418
Lines 24245 24245
Branches 82 82
=============================================
Hits 9201 9201
Misses 14306 14306
Partials 738 738
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Files selected for processing (12)
- packages/rest-api/src/middleware/normalizeNativeTokenAddress.ts (1 hunks)
- packages/rest-api/src/routes/bridgeRoute.ts (2 hunks)
- packages/rest-api/src/routes/bridgeTxInfoRoute.ts (2 hunks)
- packages/rest-api/src/routes/destinationTokensRoute.ts (2 hunks)
- packages/rest-api/src/routes/swapRoute.ts (2 hunks)
- packages/rest-api/src/routes/swapTxInfoRoute.ts (2 hunks)
- packages/rest-api/src/tests/bridgeRoute.test.ts (4 hunks)
- packages/rest-api/src/tests/bridgeTxInfoRoute.test.ts (4 hunks)
- packages/rest-api/src/tests/destinationTokensRoute.test.ts (7 hunks)
- packages/rest-api/src/tests/swapRoute.test.ts (6 hunks)
- packages/rest-api/src/tests/swapTxInfoRoute.test.ts (7 hunks)
- packages/rest-api/src/utils/tokenAddressToToken.ts (1 hunks)
Additional comments not posted (44)
packages/rest-api/src/middleware/normalizeNativeTokenAddress.ts (1)
6-18: LGTM!The
normalizeNativeTokenAddressmiddleware function is implemented correctly and follows the Express middleware pattern. It properly validates and normalizes the specified Ethereum addresses in the request query parameters using theetherslibrary functions. The replacement of theZeroAddresswith theNativeGasAddressis handled as per the project requirements.The function is well-structured, readable, and should work as intended.
packages/rest-api/src/tests/swapTxInfoRoute.test.ts (7)
5-5: LGTM!Importing constants for token addresses is a good practice to improve code maintainability and avoid hardcoded values.
14-15: LGTM!Replacing hardcoded token addresses with constants is a good practice to improve code maintainability.
28-29: LGTM!Replacing hardcoded token addresses with constants is a good practice to improve code maintainability.
43-44: LGTM!Replacing hardcoded token addresses with constants is a good practice to improve code maintainability.
55-55: LGTM!Replacing hardcoded token address with a constant is a good practice to improve code maintainability.
70-70: LGTM!Replacing hardcoded token address with a constant is a good practice to improve code maintainability.
85-86: LGTM!Replacing hardcoded token addresses with constants is a good practice to improve code maintainability.
packages/rest-api/src/tests/swapRoute.test.ts (8)
5-6: LGTM!Importing constants from a centralized location is a good practice for maintainability. It makes the code more readable and easier to update in the future.
15-16: LGTM!Replacing hardcoded token addresses with constants improves the maintainability of the test suite. It centralizes the token address definitions, making it easier to update them in the future.
26-52: LGTM!The new test cases cover important scenarios involving
ZeroAddressandNativeGasAddress. They ensure that the swap route returns a valid response for these scenarios, improving the overall test coverage.
57-58: LGTM!Replacing hardcoded token addresses with constants improves the maintainability of the test suite. It centralizes the token address definitions, making it easier to update them in the future.
69-69: LGTM!Replacing the hardcoded token address with a constant improves the maintainability of the test suite. It centralizes the token address definition, making it easier to update in the future.
84-84: LGTM!Replacing the hardcoded token address with a constant improves the maintainability of the test suite. It centralizes the token address definition, making it easier to update in the future.
99-99: LGTM!Replacing the hardcoded token address with a constant improves the maintainability of the test suite. It centralizes the token address definition, making it easier to update in the future.
100-100: LGTM!Replacing the hardcoded token address with a constant improves the maintainability of the test suite. It centralizes the token address definition, making it easier to update in the future.
packages/rest-api/src/tests/bridgeTxInfoRoute.test.ts (4)
5-5: LGTM!The import statement is correct and consistent with the list of alterations. Using constants for token addresses is a good practice to avoid hardcoding values in the test cases.
15-16: LGTM!Replacing hardcoded token addresses with references to the
USDCconstant is a good practice. It makes the code more maintainable and less error-prone.
83-84: LGTM!Replacing hardcoded token addresses with references to the
USDCconstant is a good practice. It makes the code more maintainable and less error-prone.
95-96: LGTM!Replacing hardcoded token addresses with references to the
USDCconstant is a good practice. It makes the code more maintainable and less error-prone.packages/rest-api/src/routes/destinationTokensRoute.ts (2)
11-11: LGTM!The import statement for the
normalizeNativeTokenAddressmiddleware is correctly structured and points to the right location.
102-102: Middleware added correctly.The
normalizeNativeTokenAddressmiddleware is correctly added to the route handler chain before thechecksumAddressesmiddleware. It is invoked with the'fromToken'parameter, indicating that it will process thefromTokenquery parameter.This middleware ensures that the native token address in the
fromTokenquery parameter is normalized to a consistent format before it is validated by thechecksumAddressesmiddleware and further processed by the route handler.packages/rest-api/src/tests/bridgeRoute.test.ts (5)
5-6: LGTM!The imports are necessary for the new test cases and follow the correct syntax and path.
16-17: LGTM!Using constants for token addresses is a good practice. The updated addresses correspond to the correct chains as per the test case description.
27-40: LGTM!The new test case is well-structured and covers a previously untested scenario with
ZeroAddress. The assertions are appropriate and cover the important aspects of the response.
42-57: LGTM!The new test case is well-structured and covers a previously untested scenario with
NativeGasAddress. The assertions are appropriate and cover the important aspects of the response.
119-120: LGTM!Using constants for token addresses is a good practice. The updated addresses correspond to the correct chains as per the test case description.
packages/rest-api/src/tests/destinationTokensRoute.test.ts (9)
5-6: LGTM!Importing constants for token addresses is a good practice. It improves code maintainability and readability.
15-15: LGTM!Using a constant from
USDC.addressesinstead of hardcoding the token address is a good practice. It improves code maintainability and readability.
29-30: LGTM!Using the
NativeGasAddressconstant instead of hardcoding the token address is a good practice. It improves code maintainability and readability.
32-38: LGTM!Adding assertions to check the presence of
symbol,address, andchainIdproperties in the response body is a good practice. It improves the test coverage and helps catch potential issues if the response format changes unexpectedly.
40-43: LGTM!Adding a test case for the
/destinationTokensendpoint withfromTokenset toZeroAddressis a good practice. It improves the test coverage and ensures the endpoint handles theZeroAddresstoken correctly.
59-59: LGTM!Using a constant from
USDC.addressesinstead of hardcoding the token address is a good practice. It improves code maintainability and readability.
73-73: LGTM!Using a constant from
USDT.addressesinstead of hardcoding the token address is a good practice. Converting the address to lowercase tests the endpoint's handling of non-checksummed addresses, which improves the test coverage.
126-126: LGTM!Using a constant from
USDC.addressesinstead of hardcoding the token address is a good practice. It improves code maintainability and readability.
138-138: LGTM!Using a constant from
USDC.addressesinstead of hardcoding the token address is a good practice. It improves code maintainability and readability.packages/rest-api/src/routes/swapRoute.ts (2)
10-10: LGTM!The import statement for the
normalizeNativeTokenAddressmiddleware is correctly added.
137-137: Verify the behavior of thenormalizeNativeTokenAddressmiddleware.The
normalizeNativeTokenAddressmiddleware is correctly added to the route handler chain for the GET request at the root path ('/'), and it is applied before thechecksumAddressesmiddleware.The middleware is invoked with the expected parameters 'fromToken' and 'toToken', indicating that it will process these token address parameters in the request.
This change modifies the control flow of the route handling by adding an additional layer of processing for the specified token parameters before the checksum validation occurs.
To fully understand the impact of this change, please verify the behavior of the
normalizeNativeTokenAddressmiddleware and ensure that it correctly normalizes the native token address as expected.Run the following script to navigate to the middleware implementation and analyze its behavior:
Verification successful
Verification of
normalizeNativeTokenAddressmiddleware behavior completedThe
normalizeNativeTokenAddressmiddleware has been analyzed, and its behavior is consistent with the expected functionality:
- It correctly processes the 'fromToken' and 'toToken' parameters in the request query.
- The middleware normalizes valid Ethereum addresses to their checksum format.
- It handles the special case of native gas token by replacing the zero address with a specific native gas address constant.
- The implementation ensures proper chaining with other middlewares by calling
next().The addition of this middleware to the route handler chain enhances the robustness of token address handling in the API. It normalizes addresses before the checksum validation occurs, which is the correct order of operations.
This change positively impacts the route handling by ensuring consistent and correct representation of token addresses, especially for the native gas token.
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Navigate to the `normalizeNativeTokenAddress` middleware implementation and analyze its behavior. # Test: Find the middleware file. Expect: The file path to be found. middleware_file=$(fd normalizeNativeTokenAddress.ts) echo "Middleware file: $middleware_file" # Test: Retrieve the middleware function implementation. Expect: The function to handle the native token address normalization. cat $middleware_file | grep -A 10 -B 5 $'export function normalizeNativeTokenAddress'Length of output: 423
Script:
#!/bin/bash # Description: Analyze the content of the normalizeNativeTokenAddress middleware file # Display the entire content of the middleware file echo "=== Content of normalizeNativeTokenAddress.ts ===" cat packages/rest-api/src/middleware/normalizeNativeTokenAddress.ts # Search for functions related to normalizing addresses echo -e "\n=== Functions related to normalizing addresses ===" grep -n "function" packages/rest-api/src/middleware/normalizeNativeTokenAddress.ts # Search for export statements echo -e "\n=== Export statements ===" grep -n "export" packages/rest-api/src/middleware/normalizeNativeTokenAddress.tsLength of output: 1251
packages/rest-api/src/routes/swapTxInfoRoute.ts (2)
11-11: LGTM!The import statement for the
normalizeNativeTokenAddressmiddleware is correctly added.
119-119: Verify the correctness of thenormalizeNativeTokenAddressmiddleware.The
normalizeNativeTokenAddressmiddleware is correctly added to the route handler for normalizing thefromTokenandtoTokenquery parameters before further processing.To ensure the correctness of the native token address normalization, please verify the following:
- The
normalizeNativeTokenAddressmiddleware correctly handles the new native token address0xEe.- The middleware replaces the old native token address
0x00...with the new address0xEewhen encountered in the specified query parameters.You can use the following script to retrieve the middleware implementation and verify its logic:
packages/rest-api/src/routes/bridgeTxInfoRoute.ts (2)
11-11: LGTM!The import statement for the
normalizeNativeTokenAddressmiddleware is correctly added, following the existing conventions.
127-127: Middleware addition looks good!The
normalizeNativeTokenAddressmiddleware is correctly added to the route handler chain, targeting thefromTokenandtoTokenquery parameters. Its placement before thechecksumAddressesmiddleware ensures that the token addresses are normalized prior to the checksum validation.This addition aligns with the PR objective of updating the native token address standard. It modifies the request handling flow to normalize the token addresses before further processing, ensuring consistency with the new standard.
packages/rest-api/src/routes/bridgeRoute.ts (2)
10-10: LGTM!The import statement for the
normalizeNativeTokenAddressmiddleware is syntactically correct and follows the common practice of importing middleware functions in Express.js.
191-191: Verify the implementation of thenormalizeNativeTokenAddressmiddleware.The usage of the
normalizeNativeTokenAddressmiddleware in the route handler is correct. It is applied to thefromTokenandtoTokenparameters before thechecksumAddressesmiddleware, suggesting that the normalization of native token addresses needs to happen before the checksum validation.However, it is important to review the implementation of the
normalizeNativeTokenAddressmiddleware to ensure that it correctly normalizes the native token addresses and handles any edge cases or potential errors.To verify the implementation, navigate to the
normalizeNativeTokenAddressmiddleware file and review the logic:Verification successful
The
normalizeNativeTokenAddressmiddleware implementation is correct and robust.The middleware successfully normalizes native token addresses for the specified fields. It handles the following key aspects:
- Processes multiple address fields as specified in the
addressFieldsarray.- Validates input as Ethereum addresses and converts them to checksum format.
- Replaces the zero address with a native gas address (likely representing the native token, e.g., ETH).
- Properly handles edge cases by checking for valid addresses and string types.
The implementation aligns with the expected behavior and should work as intended in the route handler.
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the implementation of the `normalizeNativeTokenAddress` middleware. # Test: Search for the middleware file. Expect: The file to exist. fd normalizeNativeTokenAddress.ts ./packages/rest-api/src/middleware # Test: Search for the middleware function. Expect: The function to be exported. rg --type typescript $'export\s+(const|function)\s+normalizeNativeTokenAddress' ./packages/rest-api/src/middleware/normalizeNativeTokenAddress.ts # Test: Search for the middleware logic. Expect: The logic to handle normalization and edge cases. rg --type typescript --multiline $'(req|res|next)' ./packages/rest-api/src/middleware/normalizeNativeTokenAddress.tsLength of output: 471
Script:
#!/bin/bash # Description: Display the contents of the normalizeNativeTokenAddress middleware and search for its implementation # Display the entire content of the file cat ./packages/rest-api/src/middleware/normalizeNativeTokenAddress.ts # Search for the exported function grep -E "export (const|function) normalizeNativeTokenAddress" ./packages/rest-api/src/middleware/normalizeNativeTokenAddress.ts # Search for the middleware logic grep -E "(req|res|next)" ./packages/rest-api/src/middleware/normalizeNativeTokenAddress.tsLength of output: 1644
* update bl * remove global solidity extension settings * use monorepo support in global workspace only * - use Solidity extension for formatting *.sol files - use `forge fmt` as formatter in Solidity extension * REST API Improvements [SLT-179] (#3133) * fix swaptxinfo function * Updates test coverage command * migrating to using token addresses instead of symbols * fix linting errors * fixing swaptxinfocontroller * new tests and new functionality --------- Co-authored-by: abtestingalpha <abtestingalpha@gmail.com> * Publish - @synapsecns/rest-api@1.0.75 - @synapsecns/synapse-interface@0.38.4 * fix harmony proxy (#3149) Co-authored-by: Trajan0x <trajan0x@users.noreply.github.com> * merging rfq indexer into monorepo [SLT-164] [SLT-176] (#3136) * merging rfq indexer into monorepo * nuke .env * fix commands * fix package name * test coverage script * rough pass at docs and some linting and fixes yarn * Upgrades wagmi & rainbowkit * indxer * Adds invisible but used packages * +recent-invalid-fills [SLT-188] * Moves wagmi to root * new endpoints and clean up linting --------- Co-authored-by: Trajan0x <trajan0x@users.noreply.github.com> Co-authored-by: abtestingalpha <abtestingalpha@gmail.com> Co-authored-by: parodime <jordan@protochainresearch.com> * Publish - @synapsecns/synapse-interface@0.38.5 - @synapsecns/rfq-indexer-api@1.0.2 - @synapsecns/rfq-indexer@0.0.2 * Adds /destinationTokens route [SLT-204] (#3151) * Adds /destinationTokens route * ZeroAddress & NativeGasAddress * Adds test for native gas tokens * Checksums incoming token address params * Publish - @synapsecns/rest-api@1.0.76 * boba pause (#3150) * boba pause * only boba to txns * Publish - @synapsecns/synapse-interface@0.38.6 * fix(synapse-interface): Reorders validation to check existence first (#3156) * Reorders validation to check existence first * Removes duplicates * Publish - @synapsecns/rest-api@1.0.77 * Fix boba pause (#3158) * Publish - @synapsecns/synapse-interface@0.38.7 * update bl * feat(rest-api): Adds Swagger for api docs [SLT-205] (#3159) * Adds Swagger for api docs * Replace prepended verb Get routes with nouns * Adds dev flag for swagger serverUrl * Publish - @synapsecns/rest-api@1.1.0 - @synapsecns/synapse-interface@0.38.8 - @synapsecns/rfq-indexer-api@1.0.3 - @synapsecns/rfq-indexer@0.0.3 * Pulls version from package json (#3160) * Publish - @synapsecns/rest-api@1.1.1 * Require vs import due to file location (#3161) * Require vs import due to file location * Publish - @synapsecns/rest-api@1.1.2 * Prevent caching of api docs (#3162) * Publish - @synapsecns/rest-api@1.1.3 * feat(contracts-rfq): relay/prove/claim with different address [SLT-130] (#3138) * init. solidity ^. FbV2 relay/prove/claim overloads * +IFastBridgeV2, explicit address0 cast, func scope & inheritdoc fixes * pragma lock, contract relabel * feat: start scoping V2 tests * test: override relayer role scenarios, no longer enforced by V2 * test: finish the parity test * test: the management methods * test: dst chain scenarios * test: bridge * test: prove * test: claim * test: dispute * test: refund * test: bridge reverts * remove redundant extend. rearrange inherit list * revert 0.8.20 in favor of user (non-ws) setting --------- Co-authored-by: ChiTimesChi <88190723+ChiTimesChi@users.noreply.github.com> * Publish - FastBridge@0.4.0 * fix(promexporter): make spans better (#3164) * move the errors * [goreleaser] * fix v to w * changing native token address standard [SLT-210] (#3157) * changing native token address standard * fixing tests * normalizeNativeTokenAddress middleware, additional tests --------- Co-authored-by: abtestingalpha <abtestingalpha@gmail.com> * Publish - @synapsecns/rest-api@1.1.4 * Refactoring rfq-indexer API and adding swagger docs [SLT-228] (#3167) * refactoring and adding swagger * remove testing scripts * fix typos and consistency with 404 errors * Publish - @synapsecns/rfq-indexer-api@1.0.4 * fix read mes (#3168) * Publish - @synapsecns/contracts-core@1.0.32 - FastBridge@0.4.1 - @synapsecns/solidity-devops@0.4.5 * fix(opbot): use submitter get tx status [SLT-158] (#3134) * use experimental logger to debug * fix lint * [goreleaser] * use submitter instead of client * [goreleaser] * [goreleaser] * fix(synapse-interface): Additional checks on screen [SLT-166] (#3152) * Additional checks on screen * Adds checks on chain/token changes * Publish - @synapsecns/synapse-interface@0.38.9 * feat(synapse-interface): confirm new price [SLT-150] (#3084) * add bridge quote history middleware * request user confirm changes when quoted price updates * add conditions for displaying confirm change state * track initial quote initializing confirm change state * specify output delta threshold * callback functions to handle initialize/accept/reset confirm changes flow * quote countdown timer animation to signal refresh * implement automatic refresh intervals * mouse move to refresh automatic intervals * add i8n translations for button text --------- Co-authored-by: abtestingalpha <abtestingalpha@gmail.com> * Publish - @synapsecns/synapse-interface@0.39.0 * fix: formatted bridge fee amount (#3165) * Publish - @synapsecns/rest-api@1.1.5 * fix(contracts-rfq): CI workflows [SLT-245] (#3178) * fix: license, files * fix: package name * build: update solhint to latest * build: remove prettier dependencies * fix: solhint workflows * build: update solhint in other packages as well * chore: solhint rules, exceptions * fix: silence linter warnings in tests * chore: forge fmt * add variable to test linter CI * Revert "add variable to test linter CI" This reverts commit 0629309. * Publish - @synapsecns/contracts-core@1.0.33 - @synapsecns/contracts-rfq@0.5.0 - @synapsecns/solidity-devops@0.4.6 * feat(api): bridge limits [SLT-165] (#3179) * adds `/bridgeLimits` route, controller * fetch best sdk quote for min/max origin amounts * add tests * implement middleware to normalize addresses * adds swagger doc * Publish - @synapsecns/rest-api@1.2.0 * fix(contracts-rfq): limit the amount of solhint warnings [SLT-245] (#3182) * ci: limit the amount of solhint warnings * refactor: move the errors into the separate interface * refactor: errors imports in tests * Publish - @synapsecns/contracts-rfq@0.5.1 * ci: Solidity gas diff [SLT-259] (#3181) * ci: run tests w/o coverage first for better visibility * test: malform the test to check the adjusted workflow * Revert "test: malform the test to check the adjusted workflow" This reverts commit e7db6e1. * ci: add gas-diff workflow * try changing the contract to trigger gas diffs * retrigger the workflow * ci: provide the correct report path * ci: run on pull requests only * ci: save gas reports in monorepo root * Revert "ci: run on pull requests only" This reverts commit 0a01d60. * Revert "try changing the contract to trigger gas diffs" This reverts commit 91bc03e. * refactor: wrap if statement * refactor: exclude `solidity-devops` package in a more generic way * ci: run tests w/o coverage for `solidity-devops`, add comments * add generic comment to trigger `solidity-devops` workflows * Revert "add generic comment to trigger `solidity-devops` workflows" This reverts commit cc35a43. * Publish - @synapsecns/contracts-rfq@0.5.2 * fix(contracts-core): set very high gas limit for intensive tests [SLT-259] (#3186) * fix: set very high gas limit for intensive tests * ci: speed up solidity coverage * Publish - @synapsecns/contracts-core@1.0.34 * feat(rest-api): Adds validateRouteExists validation [SLT-260] (#3180) * Adds validateRouteExists validation * Remove timeouts for 400s * Publish - @synapsecns/rest-api@1.3.0 * add duplicate command warning (#3174) Co-authored-by: Trajan0x <trajan0x@users.noreply.github.com> * reduce solhint warnings on FbV2 (#3189) * reduce solhint warnings on FbV2 * fix whitespace * Publish - @synapsecns/contracts-rfq@0.5.3 * ci: solidity gas diff options [SLT-267] (#3193) * ci: ignore test files in gas diff report * add some changes to the test files * ci: define some options for gas-diff * try changing the contract to trigger gas diffs * Revert "try changing the contract to trigger gas diffs" This reverts commit 4504e3c. * Revert "add some changes to the test files" This reverts commit 7e7d6cb. * prove w/ tx id [SLT-181] (#3169) * prove w/ tx id SLT-181 * +proveOther tests, forge fmt * fmt * fmt * Publish - @synapsecns/contracts-rfq@0.5.4 * fix(sdk-router): disable ARB airdrop tests (#3195) * Publish - @synapsecns/rest-api@1.3.1 - @synapsecns/sdk-router@0.11.2 - @synapsecns/synapse-interface@0.39.1 - @synapsecns/widget@0.7.2 * Fixing issue for wallet integration [SLT-270] (#3194) * slight modification to graphql call * fixing explorer frontend as well * Publish - @synapsecns/explorer-ui@0.3.3 - @synapsecns/rest-api@1.3.2 * store relayer on relay [SLT-182] (#3170) * store relayer on relay [SLT-182] * +tests, zeroAddr check, fmt * Publish - @synapsecns/contracts-rfq@0.5.5 * Adjust text to trigger build (#3199) * Publish - @synapsecns/synapse-interface@0.39.2 * feat(synapse-interface): refund RFQ transaction [SLT-272] (#3197) * Txn transaction refund tracking * Update store to support tracking * Query FastBridge contract for `bridgeStatuses` to find refund status * Track bridge transaction `bridgeQuote.routerAddress` in store * Fetch FastBridge contract address when only provided router address * add translations --------- Co-authored-by: aureliusbtc <82057759+aureliusbtc@users.noreply.github.com> Co-authored-by: ChiTimesChi <88190723+ChiTimesChi@users.noreply.github.com> Co-authored-by: abtestingalpha <abtestingalpha@gmail.com> Co-authored-by: Defi-Moses <Defi-Moses@users.noreply.github.com> Co-authored-by: trajan0x <83933037+trajan0x@users.noreply.github.com> Co-authored-by: Trajan0x <trajan0x@users.noreply.github.com> Co-authored-by: parodime <jordan@protochainresearch.com> Co-authored-by: abtestingalpha <104046418+abtestingalpha@users.noreply.github.com> Co-authored-by: abtestingalpha <abtestingalpha@users.noreply.github.com> Co-authored-by: parodime <parodime@users.noreply.github.com> Co-authored-by: vro <168573323+golangisfun123@users.noreply.github.com> Co-authored-by: ChiTimesChi <ChiTimesChi@users.noreply.github.com> Co-authored-by: bigboydiamonds <57741810+bigboydiamonds@users.noreply.github.com> Co-authored-by: bigboydiamonds <bigboydiamonds@users.noreply.github.com>
Changes the native gas token address from 0x00... to 0xEe
Summary by CodeRabbit
New Features
Improvements