Skip to content

Commit 45834d5

Browse files
Define101gitbook-bot
authored andcommitted
GITBOOK-123: No subject
1 parent 0beb0c6 commit 45834d5

File tree

1 file changed

+2
-19
lines changed

1 file changed

+2
-19
lines changed

list-your-project/how-to-add-a-new-blockchain.md

Lines changed: 2 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -25,24 +25,7 @@ You should use the field shortName from [https://chainlist.org/rpcs.json](https
2525

2626
***
2727

28-
#### 2. **Update RPC URLs in `env.js (Optional)`**
29-
30-
You'll need to add the appropriate RPC endpoint for the new blockchain in the `projects/helper/env.js` file.
31-
32-
**Example Change**:
33-
34-
```js
35-
const ENV_KEYS = [
36-
"OZONE_RPC": "https://node1.ozonechain.io",
37-
"ZETA_RPC": "https://zetachain-evm.blockpi.network/v1/rpc/public",
38-
"DEFIVERSE_RPC": "https://rpc.defi-verse.org/",
39-
"ZKLINK_RPC": "https://rpc.zklink.io", // Add the RPC URL for your new blockchain
40-
];
41-
```
42-
43-
***
44-
45-
#### 3. **Add Token Mappings in `tokenMapping.js`**
28+
#### 2. **Add Token Mappings in `tokenMapping.js`**
4629

4730
Add the token mappings for the new blockchain to the `projects/helper/tokenMapping.js` file. This file maps token addresses to their respective identifiers for accurate tracking and handling.
4831

@@ -63,7 +46,7 @@ This ensures tokens on the new blockchain (`zklink`) are properly recognized, in
6346

6447
***
6548

66-
#### 4. Submit a Protocol **using your blockchain (e.g.,** projects/savmswap/index.js**)**
49+
#### 3. Submit a Protocol **using your blockchain (e.g.,** projects/savmswap/index.js**)**
6750

6851
Lastly, update the project’s configuration file to add your new blockchain as a valid supported chain. If we don´t track any protocol on your blockchain, we can not add it. So make sure to add the new chain under a current project or add a new adapter to track the project on your blockchain
6952

0 commit comments

Comments
 (0)