Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

devop: new networks #603

Merged
merged 16 commits into from
Jan 29, 2025
Merged

devop: new networks #603

merged 16 commits into from
Jan 29, 2025

Conversation

kvhnuke
Copy link
Contributor

@kvhnuke kvhnuke commented Jan 23, 2025

  • 5ire
  • syscoin
  • form

Summary by CodeRabbit

  • New Features

    • Added support for 5ireChain network.
    • Added support for Form Mainnet network.
    • Updated Syscoin network to Syscoin NEVM.
    • Introduced buy links for various networks.
  • Network Updates

    • Replaced Syscoin and Syscoin Test networks with Syscoin NEVM and Syscoin NEVM Test.
    • Updated network configurations and endpoints.
    • Improved token balance retrieval for new networks.
  • Documentation

    • Updated README to reflect new supported chains.
    • Enhanced clarity in network configurations and supported chains.
  • Version Update

    • Package version updated from 2.1.0 to 2.2.0.

Copy link

coderabbitai bot commented Jan 23, 2025

Walkthrough

This pull request introduces updates to the Ethereum network providers, focusing on network configurations for Syscoin NEVM, Rollux, and 5ire Chain. The changes include modifying network names, updating import paths, adding new network configurations, and enhancing token balance retrieval mechanisms. Key modifications involve replacing Syscoin with Syscoin NEVM, introducing 5ireChain, updating token lists and balance handling, and restructuring network-related files and imports.

Changes

File Change Summary
README.md Updated "Syscoin" to "Syscoin NEVM", added "5ireChain" to supported chains
packages/extension/src/providers/ethereum/libs/activity-handlers/providers/etherscan/configs.ts Updated network endpoints for Form, SyscoinNEVM, and SyscoinNEVMTest; removed old Syscoin endpoints
packages/extension/src/providers/ethereum/libs/assets-handlers/assetinfo-mew.ts Added support for Blockscout balances for SyscoinNEVM and updated Rollux configuration
packages/extension/src/providers/ethereum/libs/assets-handlers/blockscout.ts Introduced getBlockscoutBalances function for fetching token balances
packages/extension/src/providers/ethereum/libs/assets-handlers/token-lists.ts Added token data fetching URLs for SyscoinNEVM and Rollux
packages/extension/src/providers/ethereum/libs/assets-handlers/types/tokenbalance-mew.ts Made tbName optional and added bsEndpoint to SupportedNetwork interface
packages/extension/src/providers/ethereum/networks/* Added new network configurations for 5ire, Form, SyscoinNEVM, and SyscoinNEVMTest; removed old Syscoin configurations
packages/types/src/networks.ts Updated NetworkNames enum with new network names
packages/extension/package.json Updated version from 2.1.0 to 2.2.0
packages/extension/src/providers/common/libs/new-features.ts Updated newNetworks to include new network names

Suggested Reviewers

  • NickKelly1
  • gamalielhere

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8fedb67 and d24108a.

📒 Files selected for processing (1)
  • packages/extension/src/providers/ethereum/libs/transaction/index.ts (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: buildAll
  • GitHub Check: test
🔇 Additional comments (1)
packages/extension/src/providers/ethereum/libs/transaction/index.ts (1)

95-96: Strengthen fee market network detection logic.

The additional check history.baseFeePerGas.length !== 0 makes the fee market detection more robust by ensuring both current and historical base fees exist. This helps prevent edge cases where a network might report a base fee but lack fee history support.

Let's verify the fee market support across the new networks (5ire, Syscoin NEVM) by checking their EIP-1559 compatibility:

✅ Verification successful

Additional fee history check is crucial for EIP-1559 detection

The verification confirms that the additional history.baseFeePerGas.length !== 0 check is necessary. While 5ire Chain returns baseFeePerGas in blocks but lacks fee history support, Syscoin NEVM properly implements both. This prevents incorrect fee market detection on networks with partial EIP-1559 implementation.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check if the new networks support EIP-1559 fee market
# Expected: Networks should return base fee and fee history if they support EIP-1559

# Search for network configurations
echo "Searching for network configurations..."
rg -A 10 "SyscoinNEVM|5ire" --type ts

# Check if the networks are configured as EIP-1559 compatible
echo "Checking for EIP-1559 compatibility indicators..."
rg -A 5 "defaultHardfork.*London" --type ts

Length of output: 14471


Script:

#!/bin/bash
# Check EIP-1559 support on 5ire and Syscoin NEVM

# Function to check EIP-1559 support
check_eip1559() {
    network_name=$1
    rpc_url=$2
    
    echo "Checking $network_name..."
    
    # Get latest block
    echo "Latest block:"
    curl -s -X POST -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_getBlockByNumber","params":["latest",false],"id":1}' $rpc_url
    
    echo -e "\nFee history:"
    # Get fee history (1 block)
    curl -s -X POST -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_feeHistory","params":["0x1", "latest", [25]],"id":1}' $rpc_url
    echo -e "\n---"
}

# Check 5ire
check_eip1559 "5ire" "https://rpc.5ire.network"

# Check Syscoin NEVM
check_eip1559 "Syscoin NEVM" "https://rpc.syscoin.org"

Length of output: 4482

✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

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?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

github-actions bot commented Jan 23, 2025

💼 Build Files
chrome: enkrypt-chrome-d24108ae.zip
firefox: enkrypt-firefox-d24108ae.zip

💉 Virus total analysis
chrome: d24108ae
firefox: d24108ae

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🔭 Outside diff range comments (1)
packages/extension/src/providers/ethereum/libs/assets-handlers/types/tokenbalance-mew.ts (1)

Missing network configuration file for Sanko network

All networks added to SupportedNetworkNames have their corresponding configuration files except for Sanko network. While Sanko is referenced in the network index, it appears to be missing its dedicated configuration file.

The following networks are properly configured:

  • Degen (degen.ts)
  • Blast (blast.ts)
  • XLayer (xlayer.ts)
  • ProofOfPlayApex (pop-apex.ts)
  • Godwoken (godwoken.ts)
  • Linea (linea.ts)
  • MantaPacific (manta-pacific.ts)
  • Mode (mode.ts)
  • OpBNB (op-bnb.ts)
  • Scroll (scroll.ts)
  • Rari (rari.ts)
🔗 Analysis chain

Line range hint 54-68: Verify network configuration files exist.

Multiple networks have been added to SupportedNetworkNames. Please ensure that corresponding network configuration files exist for each new network.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for network configuration files
echo "Searching for network configuration files..."
fd -e ts -e js "sanko|degen|blast|xlayer|proofofplayapex|godwoken|linea|mantapacific|mode|opbnb|scroll|rari"

Length of output: 847


Script:

#!/bin/bash
# Search for missing network configs with flexible patterns
echo "Searching for missing network configs..."
rg -l "sanko|proof.*play|manta|opbnb|pacific" packages/extension/src/providers/ethereum/networks/

echo -e "\nVerifying network configuration structure..."
for file in packages/extension/src/providers/ethereum/networks/*.ts; do
  echo -e "\n=== $file ==="
  # Look for standard network configuration exports
  rg "export const \w+Config = {" "$file" || rg "export default {" "$file"
done

Length of output: 37960


Script:

#!/bin/bash
# Search for Sanko network configuration with more variations
echo "Searching for Sanko network configuration..."
rg -l "sanko|sanc?ko" packages/extension/src/providers/ethereum/networks/

Length of output: 292

🧹 Nitpick comments (5)
packages/extension/src/providers/ethereum/networks/5ire.ts (1)

6-20: Add buyLink property for consistency.

Other network configurations include a buyLink property. Consider adding it for consistency if there's a faucet or exchange available for 5IRE tokens.

packages/extension/src/providers/ethereum/libs/assets-handlers/blockscout.ts (2)

34-37: Consider implementing rate limiting.

Multiple concurrent requests to the Blockscout API might trigger rate limiting. Consider implementing request queuing or rate limiting.


79-87: Enhance error handling specificity.

The catch-all error handler returns a zero balance without distinguishing between different types of errors (network, API, parsing). Consider implementing more specific error handling.

   .catch(error => {
     console.error('Error fetching balances:', error);
+    // Log specific error types for better debugging
+    if (error instanceof TypeError) {
+      console.error('Network error:', error);
+    } else if (error instanceof SyntaxError) {
+      console.error('JSON parsing error:', error);
+    }
     return [
       {
         contract: NATIVE_TOKEN_ADDRESS,
         balance: '0x0',
       },
     ];
   });
packages/extension/src/providers/ethereum/networks/index.ts (1)

65-65: Consider renaming the 5ire import and key.

While the implementation works, consider renaming _5ireNode to fireNode and using fire as the key instead of '5ire' for consistency with other network naming patterns.

-import _5ireNode from './5ire';
+import fireNode from './fire';
 
 export default {
-  '5ire': _5ireNode,
+  fire: fireNode,
 };

Also applies to: 141-141

packages/extension/src/ui/action/App.vue (1)

365-384: Consider adding error handling.

The function should handle cases where:

  • Selected account is undefined
  • Network display address fails
  • Buy link is undefined
 const buyLink = (() => {
+  if (!accountHeaderData.value.selectedAccount) {
+    throw new Error('No account selected');
+  }
   switch (currentNetwork.value.name) {
     case NetworkNames.KadenaTestnet:
-      return (currentNetwork.value as KadenaNetwork).options.buyLink;
+      const kadenaLink = (currentNetwork.value as KadenaNetwork).options.buyLink;
+      if (!kadenaLink) throw new Error('Buy link not configured');
+      return kadenaLink;
     // ... rest of the cases
     default:
       return `https://ccswap.myetherwallet.com/?to=${currentNetwork.value.displayAddress(
         accountHeaderData.value.selectedAccount!.address,
       )}&network=${currentNetwork.value.name}&crypto=${
         currentNetwork.value.currencyName
       }&platform=enkrypt`;
   }
 })();
+if (!buyLink) throw new Error('Failed to generate buy link');
 Browser.tabs.create({
   url: buyLink,
 });
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 422eda8 and d491816.

⛔ Files ignored due to path filters (1)
  • packages/extension/src/providers/ethereum/networks/icons/5ire.svg is excluded by !**/*.svg
📒 Files selected for processing (19)
  • README.md (2 hunks)
  • packages/extension/src/providers/ethereum/libs/activity-handlers/providers/etherscan/configs.ts (1 hunks)
  • packages/extension/src/providers/ethereum/libs/assets-handlers/assetinfo-mew.ts (3 hunks)
  • packages/extension/src/providers/ethereum/libs/assets-handlers/blockscout.ts (1 hunks)
  • packages/extension/src/providers/ethereum/libs/assets-handlers/token-lists.ts (1 hunks)
  • packages/extension/src/providers/ethereum/libs/assets-handlers/types/tokenbalance-mew.ts (2 hunks)
  • packages/extension/src/providers/ethereum/networks/5ire.ts (1 hunks)
  • packages/extension/src/providers/ethereum/networks/bsc.ts (0 hunks)
  • packages/extension/src/providers/ethereum/networks/form.ts (1 hunks)
  • packages/extension/src/providers/ethereum/networks/index.ts (4 hunks)
  • packages/extension/src/providers/ethereum/networks/sys.ts (0 hunks)
  • packages/extension/src/providers/ethereum/networks/syscoin/nevm-testnet.ts (1 hunks)
  • packages/extension/src/providers/ethereum/networks/syscoin/nevm.ts (1 hunks)
  • packages/extension/src/providers/ethereum/networks/syscoin/rollux-testnet.ts (2 hunks)
  • packages/extension/src/providers/ethereum/networks/syscoin/rollux.ts (2 hunks)
  • packages/extension/src/providers/ethereum/networks/tsys.ts (0 hunks)
  • packages/extension/src/providers/ethereum/types/evm-network.ts (2 hunks)
  • packages/extension/src/ui/action/App.vue (1 hunks)
  • packages/types/src/networks.ts (2 hunks)
💤 Files with no reviewable changes (3)
  • packages/extension/src/providers/ethereum/networks/bsc.ts
  • packages/extension/src/providers/ethereum/networks/sys.ts
  • packages/extension/src/providers/ethereum/networks/tsys.ts
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: buildAll
  • GitHub Check: test
🔇 Additional comments (21)
packages/extension/src/providers/ethereum/networks/5ire.ts (1)

16-16: Consider using WSS endpoint for enhanced security.

The current HTTP RPC endpoint could be vulnerable to man-in-the-middle attacks. Consider using a secure WebSocket (WSS) endpoint if available.

packages/extension/src/providers/ethereum/networks/form.ts (2)

15-16: Verify currency configuration.

The network is Form Mainnet but uses ETH as currency. This seems inconsistent. Please verify if this is correct or if Form has its own native token.


19-19: Review activity handler configuration.

The network uses EtherscanActivity handler but Form doesn't appear to use Etherscan. Consider implementing a custom activity handler or using a more appropriate one.

packages/extension/src/providers/ethereum/networks/syscoin/rollux-testnet.ts (1)

1-1: LGTM!

The changes look good:

  • Import paths are correctly updated
  • Added buyLink property pointing to the correct faucet
  • Configuration maintains security best practices with WSS endpoint

Also applies to: 3-4, 19-19

packages/extension/src/providers/ethereum/networks/syscoin/nevm-testnet.ts (1)

7-21: LGTM!

The network configuration is complete and follows best practices:

  • Uses secure WSS endpoint
  • Includes faucet link
  • Chain ID matches official documentation
packages/extension/src/providers/ethereum/networks/syscoin/rollux.ts (2)

1-1: LGTM! Import paths updated correctly.

The import paths have been properly updated to reflect the new directory structure.

Also applies to: 3-5


23-23: Verify the buyLink functionality.

The buyLink includes multiple cryptocurrencies (SYSROLLUX, SYSEVM, SYS). Please ensure that:

  1. The Coinify trade URL is accessible
  2. All listed cryptocurrencies are available for purchase
packages/extension/src/providers/ethereum/networks/syscoin/nevm.ts (2)

19-20: Potential conflict in coingeckoID configuration.

Both Rollux and Syscoin NEVM networks use the same coingeckoID: "syscoin". This might cause issues with price tracking as both networks would fetch the same price data.

✅ Verification successful

Configuration is correct - no conflict in price tracking

The shared coingeckoID: "syscoin" is not problematic because each network uses a different coingeckoPlatform value:

  • NEVM: CoingeckoPlatform.Syscoin
  • Rollux: CoingeckoPlatform.Rollux

The combination of both values ensures unique price tracking for each network.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for other occurrences of coingeckoID: "syscoin"
rg -l 'coingeckoID.*syscoin' --type ts

Length of output: 176


Script:

#!/bin/bash
# Get the complete coingecko configuration from both files
echo "=== NEVM Configuration ==="
rg "coingecko[A-Z][a-zA-Z]+.*" packages/extension/src/providers/ethereum/networks/syscoin/nevm.ts -A 1

echo -e "\n=== Rollux Configuration ==="
rg "coingecko[A-Z][a-zA-Z]+.*" packages/extension/src/providers/ethereum/networks/syscoin/rollux.ts -A 1

Length of output: 510


8-25: Verify network configuration parameters.

Please ensure:

  1. The WebSocket endpoint is operational
  2. The block explorer endpoints are accessible
  3. The chain ID is correctly registered with chainlist.org
✅ Verification successful

Network configuration parameters verified successfully

All critical network parameters are correctly configured:

  • Chain ID 0x39 is officially registered on chainlist.org
  • Block explorer endpoints are operational and correctly formatted
  • WebSocket endpoint is officially listed and matches chainlist.org data
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Verify WebSocket endpoint
curl --include --no-buffer \
  --header "Connection: Upgrade" \
  --header "Upgrade: websocket" \
  --header "Sec-WebSocket-Version: 13" \
  "wss://rpc.syscoin.org/wss"

# Verify block explorer endpoints
curl -I "https://explorer.syscoin.org/"

# Verify chain ID registration
curl -s "https://chainid.network/chains.json" | jq '.[] | select(.chainId == 57)'

Length of output: 2975


Script:

#!/bin/bash
# Install wscat for WebSocket testing
npm install -g wscat

# Test WebSocket connection
timeout 5 wscat -c wss://rpc.syscoin.org/wss

# Test specific explorer endpoints with a known transaction and address
curl -I "https://explorer.syscoin.org/tx/0x0000000000000000000000000000000000000000000000000000000000000000"
curl -I "https://explorer.syscoin.org/address/0x0000000000000000000000000000000000000000"

Length of output: 5824

packages/extension/src/providers/ethereum/libs/assets-handlers/types/tokenbalance-mew.ts (1)

8-8: Interface changes look good but need verification.

The optional properties tbName and bsEndpoint have been added correctly. However, please verify that all implementations handle these optional properties appropriately.

Also applies to: 10-10

✅ Verification successful

Optional properties are properly implemented and handled

The verification shows that both tbName and bsEndpoint optional properties are correctly implemented in assetinfo-mew.ts with proper fallbacks and conditional checks. The code handles undefined cases appropriately.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for usages of tbName and bsEndpoint
ast-grep --pattern 'interface $_ {
  $$$
  tbName$_
  $$$
}'

ast-grep --pattern 'interface $_ {
  $$$
  bsEndpoint$_
  $$$
}'

Length of output: 129


Script:

#!/bin/bash
# First, let's find the interface name and its usages
echo "=== Interface Definition ==="
rg -A 5 "interface.*\{" "packages/extension/src/providers/ethereum/libs/assets-handlers/types/tokenbalance-mew.ts"

echo -e "\n=== Interface Usages ==="
# Search for any imports of this file
rg -l "tokenbalance-mew" packages/extension/src/providers/ethereum/

echo -e "\n=== Property Access Patterns ==="
# Search for tbName and bsEndpoint usage
rg "tbName|bsEndpoint" packages/extension/src/providers/ethereum/

Length of output: 5992

packages/types/src/networks.ts (2)

69-69: LGTM! Network names follow consistent naming conventions.

The new network entries maintain consistent naming patterns and preserve backward compatibility with existing identifiers.

Also applies to: 72-73


100-100: Add CoingeckoPlatform entry for Fire network.

The Fire network (5ire) is missing its corresponding entry in the CoingeckoPlatform enum, which might affect token list functionality.

Run this script to check if the network requires token list support:

packages/extension/src/providers/ethereum/networks/index.ts (1)

38-41: LGTM! Well-organized network node structure.

The Syscoin and Rollux networks are properly organized under the syscoin directory, indicating good code organization.

packages/extension/src/providers/ethereum/libs/activity-handlers/providers/etherscan/configs.ts (1)

52-52: LGTM! Secure explorer endpoints configured.

The new network explorer endpoints:

  • Use HTTPS for secure communication
  • Follow consistent naming patterns for test/main networks
  • Point to official block explorers

Also applies to: 55-56

packages/extension/src/providers/ethereum/types/evm-network.ts (2)

37-37: LGTM! Well-typed interface extension.

The addition of the optional buyLink property maintains backward compatibility while extending the network configuration options.


102-102: LGTM! Good practice storing options.

Storing the options in the class enables access to network configuration after initialization, which is necessary for the new buyLink functionality.

packages/extension/src/providers/ethereum/libs/assets-handlers/assetinfo-mew.ts (3)

23-23: LGTM! Clean import.

The import follows the project's conventions and supports the new balance fetching functionality.


124-130: LGTM! Clear network configurations.

The configurations for SyscoinNEVM and Rollux are well-structured and consistently use the blockscout endpoint.


199-200: LGTM! Clean integration of blockscout support.

The addition of blockscout endpoint support is well-integrated into the existing control flow.

packages/extension/src/ui/action/App.vue (1)

365-384: LGTM! Well-structured network handling.

The switch statement provides clear, network-specific logic for buy links.

Verify the network configurations with:

✅ Verification successful

Verified: Network-specific buy links are properly handled

The switch statement correctly handles all networks with specific buyLink configurations, including:

  • Syscoin NEVM and Rollux networks with Coinify integration
  • Test networks with appropriate fallbacks
  • Default case for other networks using ccswap
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify that all networks with buyLink option are handled in the switch statement
ast-grep --pattern 'case NetworkNames.$_: return $_'

Length of output: 54


Script:

#!/bin/bash
# Find NetworkNames enum definition and network configurations
echo "=== NetworkNames enum ==="
rg "enum NetworkNames" -A 10

echo -e "\n=== Network configurations with buyLink ==="
rg "buyLink.*=" -B 2 -A 2

echo -e "\n=== Network type definitions ==="
ast-grep --pattern 'interface $_ extends Network {
  $$$
}'

Length of output: 2891

README.md (1)

Line range hint 102-111: LGTM! Documentation aligned with code changes.

The supported chains list accurately reflects the network configuration changes in the codebase.

🧰 Tools
🪛 LanguageTool

[duplication] ~99-~99: Possible typo: you repeated a word.
Context: ...ck - Sanko Chain - Scroll - Shibarium - Shiden - Shiden EVM - Sepolia - Syscoin NEVM - Telos EV...

(ENGLISH_WORD_REPEAT_RULE)

Comment on lines +6 to +7
[NetworkNames.SyscoinNEVM]: `https://tokens.coingecko.com/${CoingeckoPlatform.Syscoin}/all.json`,
[NetworkNames.Rollux]: `https://tokens.coingecko.com/${CoingeckoPlatform.Rollux}/all.json`,
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Remove duplicate Rollux entry.

The Rollux network has two entries in the TokenList:

  1. Line 7: [NetworkNames.Rollux]
  2. Line 27: [NetworkNames.Rollux]

Please remove one of the duplicate entries.

coderabbitai[bot]
coderabbitai bot previously requested changes Jan 23, 2025
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d491816 and f83eb37.

📒 Files selected for processing (2)
  • packages/extension/package.json (1 hunks)
  • packages/extension/src/providers/common/libs/new-features.ts (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • packages/extension/package.json
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: buildAll
  • GitHub Check: test
🔇 Additional comments (1)
packages/extension/src/providers/common/libs/new-features.ts (1)

7-7: Verify if "Fire" should be "5ire".

The PR objective mentions "5ire" but the code uses "Fire". This might be a naming inconsistency.

Let's check for any references to both names:

@kvhnuke kvhnuke merged commit aa64ffc into develop Jan 29, 2025
3 of 4 checks passed
@kvhnuke kvhnuke deleted the devop/new-networks-2 branch January 29, 2025 21:46
@coderabbitai coderabbitai bot mentioned this pull request Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants