Sync Upstream

.github/workflows/action_lint.yml

@@ -0,0 +1,8 @@
+name: Github-Action linter
+on: [pull_request]
+jobs:
+  actionlint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4.2.2
+      - uses: reviewdog/action-actionlint@v1

.github/workflows/build.yml

@@ -5,13 +5,13 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout
-        uses: actions/checkout@v2.3.1
+        uses: actions/checkout@v4.2.2
         with:
           submodules: recursive
 
       - name: Get changed files
         id: changed-files
-        uses: tj-actions/changed-files@v41
+        uses: step-security/changed-files@v45.0.1
 
       - name: Check changed files
         run: |

.github/workflows/deploy.yml

@@ -7,14 +7,14 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout	
-        uses: actions/checkout@v2.3.1
+        uses: actions/checkout@v4.2.2
         with:
           submodules: recursive
       - name: Build
         run: |
           ./gradlew run
       - name: Set Node.js 18.x
-        uses: actions/setup-node@v3
+        uses: actions/setup-node@v4.2.0
         with:
           node-version: 18.x
       - name: Run yarn install

.github/workflows/pr_intro_comment.yml

@@ -0,0 +1,14 @@
+on:
+  pull_request_target:
+    types: [opened]
+jobs:
+  comment_on_pr:
+    runs-on: ubuntu-latest
+    name: Comment after PR is submitted
+    steps:
+      - name: Comment PR
+        uses: thollander/actions-comment-pull-request@v2
+        with:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          message: |
+            You successfully submitted a PR! Due to the amount of PRs coming in: we will only look at PRs that the CI is happy with. We can also not hold your hand getting the CI green - just look how others that where merged did it and RTFM. So as long as there is any CI check that reports an error - no human will look at this. You might be able to ask for some support after supporting the project - e.g. by sending funds to lists.eth. When you fixed things after a requested change - then you also need to (re-)request a review.

.github/workflows/prettier_check.yml

@@ -2,14 +2,15 @@ name: Run prettier check
 
 on:
   push:
+  pull_request:
 
 jobs:
   prettier:
     runs-on: ubuntu-latest
     steps:
       - name: Check out repo
-        uses: actions/checkout@v2
-      - uses: actions/cache@v2
+        uses: actions/checkout@v4.2.2
+      - uses: actions/cache@v4
         name: Configure npm caching
         with:
           path: ~/.npm

.github/workflows/rebase.yml

@@ -14,7 +14,7 @@ jobs:
       )
     steps:
       - name: Checkout the latest code
-        uses: actions/checkout@v2
+        uses: actions/checkout@v4.2.2
         with:
           token: ${{ secrets.GITHUB_TOKEN }}
           fetch-depth: 0 # otherwise, you will fail to push refs to dest repo

.github/workflows/validate_json.yml

@@ -9,8 +9,8 @@ jobs:
     runs-on: ubuntu-latest
     steps:
     - name: Check out repo
-      uses: actions/checkout@v2
-    - uses: actions/cache@v2
+      uses: actions/checkout@v4.2.2
+    - uses: actions/cache@v4
       name: Configure npm caching
       with:
         path: ~/.npm
@@ -21,4 +21,4 @@ jobs:
       working-directory: ./tools
       run: |-
         npm install
-        node schemaCheck.js
+        node schemaCheck.js

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2018 
+Copyright (c) 2025 
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

README.md

@@ -2,7 +2,7 @@
 
 The source data is in _data/chains. Each chain has its own file with the filename being the [CAIP-2](https://github.com/ChainAgnostic/CAIPs/blob/master/CAIPs/caip-2.md) representation as name and `.json` as extension.
 
-## Example
+## Example:
 
 ```json
 {
@@ -33,7 +33,8 @@ The source data is in _data/chains. Each chain has its own file with the filenam
 }
 ```
 
-when an icon is used in either the network or an explorer there must be a json in _data/icons with the name used (e.g. in the above example there must be a `ethereum.json` and a `etherscan.json` in there) - the icon jsons look like this:
+When an icon is used in either the network or an explorer, there must be a JSON in _data/icons with the name used.
+(e.g. in the above example there must be a `ethereum.json` and a `etherscan.json` in there) - The icon JSON files look like this:
 
 ```json
 
@@ -49,9 +50,10 @@ when an icon is used in either the network or an explorer there must be a json i
 ```
 
 where:
- * the URL must be an IPFS url that is publicly resolvable
- * width and height are positive integers
+ * The URL MUST be publicly resolvable through IPFS
+ * width and height MUST be positive integers
  * format is either "png", "jpg" or "svg"
+ * size MUST be less than 250kb
 
 If the chain is an L2 or a shard of another chain you can link it to the parent chain like this:
 
@@ -67,7 +69,7 @@ If the chain is an L2 or a shard of another chain you can link it to the parent
 }
 ```
 
-where you need to specify type 2 and the reference to an existing parent. The field about bridges is optional.
+where you need to specify the type and the reference to an existing parent. The field about bridges is optional.
 
 You can add a `status` field e.g. to deprecate (via status `deprecated`) a chain (a chain should never be deleted as this would open the door to replay attacks)
 Other options for `status` are `active` (default) or `incubating`
@@ -82,20 +84,20 @@ There are also aggregated json files with all chains automatically assembled:
 
  * the shortName and name MUST be unique - see e.g. EIP-3770 on why
  * if referencing a parent chain - the chain MUST exist in the repo
- * if using a IPFS CID for the icon - the CID MUST be retrievable via `ipfs get` - not only through some gateway (means please do not use pinata for now)
+ * if using an IPFS CID for the icon - the CID MUST be retrievable via `ipfs get` - not only through some gateway (means please do not use pinata for now)
  * for more constraints you can look into the CI
 
 ## Collision management
 
  We cannot allow more than one chain with the same chainID - this would open the door to replay attacks.
  The first pull request gets the chainID assigned. When creating a chain we can expect that you read EIP155 which states this repo.
  All pull requests trying to replace a chainID because they think their chain is better than the other will be closed.
- The only way to get a chain reassigned is when the old chain gets deprecated. This can e.g. be used for testnets that are short-lived. But then you will get the redFlag "reusedChaiID" that should be displayed in clients to warn them about the dangers here.
+ The only way to get a chain reassigned is when the old chain gets deprecated. This can e.g. be used for testnets that are short-lived. But then you will get the redFlag "reusedChainID" that should be displayed in clients to warn them about the dangers here.
 
 ## Getting your PR merged
 ### before PR is submitted
 
-Before submitting a PR, please verify that checks pass with:
+Before submitting a PR, please ensure all checks pass by running:
 
 ```bash
 $ ./gradlew run
@@ -104,7 +106,7 @@ BUILD SUCCESSFUL in 7s
 9 actionable tasks: 9 executed
 ```
 
-Also please run the prettier to format your json according to the style [defined here ](https://github.com/ethereum-lists/chains/blob/master/.prettierrc.json)
+Additionally, run Prettier to format your JSON according to the style [defined here ](https://github.com/ethereum-lists/chains/blob/master/.prettierrc.json)
 e.g. run
 
 ```
@@ -117,7 +119,7 @@ npx prettier --write _data/*/*.json
  * When making changes that fix the CI problems - please re-request a review - otherwise it is too much work to track such changes with so many PRs daily
 
 ## Usages
-### Tools 
+### Tools
  * [MESC](https://paradigmxyz.github.io/mesc)
 
 ### Explorers
@@ -145,6 +147,7 @@ npx prettier --write _data/*/*.json
  * [evmchainlist.org](https://evmchainlist.org)
  * [networks.vercel.app](https://networks.vercel.app)
  * [Wagmi compatible chain configurations](https://spenhouet.com/chains)
+ * [chainlist.simplr.sh - Info packaged single pager](https://chainlist.simplr.sh)
 
 ### Other
  * [FaucETH](https://github.com/komputing/FaucETH)

_data/chains/eip155-1.json

@@ -19,7 +19,8 @@
     "https://rpc.mevblocker.io/noreverts",
     "https://rpc.mevblocker.io/fullprivacy",
     "https://eth.drpc.org",
-    "wss://eth.drpc.org"
+    "wss://eth.drpc.org",
+    "https://api.securerpc.com/v1"
   ],
   "features": [{ "name": "EIP155" }, { "name": "EIP1559" }],
   "faucets": [],
@@ -53,6 +54,11 @@
       "url": "https://ethereum.dex.guru",
       "icon": "dexguru",
       "standard": "EIP3091"
+    },
+    {
+      "name": "Routescan",
+      "url": "https://ethereum.routescan.io",
+      "standard": "EIP3091"
     }
   ]
 }