# Zenon Public RPC Node Database Repo
**URL:** https://forum.hypercore.one/t/zenon-public-rpc-node-database-repo/386
**Category:** Development
**Created:** [February 28, 2024, 3:05pm UTC](https://forum.hypercore.one/t/zenon-public-rpc-node-database-repo/386 "2024-02-28T15:05:58Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@0x3639](https://forum.hypercore.one/u/0x3639)
#### Post date: [February 28, 2024, 3:05pm UTC](https://forum.hypercore.one/t/zenon-public-rpc-node-database-repo/386/1 "2024-02-28T15:05:58Z")
As a follow up to this post: [Public RPC Nodes in syrius v0.2.0 - #3 by CryptoFish](https://forum.hypercore.one/t/public-rpc-nodes-in-syrius-v0-2-0/385/3)
I’m discussing this idea with @CryptoFish. We have come up with an idea to create a file called `mainnet-rpc-node-db.json` that would live in a new `/zenon-network` repo. See the proposed repo here: [https://github.com/KingGorrin/zenon-node-database](https://github.com/KingGorrin/zenon-node-database).
In this `.json` file we could include a list of Public RPC Nodes like this:
```auto
{
"HyperCore-One": {
"url": "wss://my.hc1node.com:35998"
},
"Zenon Hub": {
"url": "wss://node.zenonhub.io:35998"
}
}
```
When we build `syrius` and other applications, they can pull in this file and use it when we build the binary. Putting this information in a separate repo and easily accessible file will make it “ez” for the community to see it and propose changes.
In addition, we can also expand this idea to include more information, like what is proposed below:
```auto
"name":"Zenon Mainnet",
"chain":"ZNN",
"icon":"zenon",
"infoURL":"https://zenon.network",
"shortName":"znn",
"chainId":1,
"networkId":1,
"rpc":[
"wss://my.hc1node.com:35998",
"wss://node.zenonhub.io:35998"
],
"faucets":[],
"nativeCurrency":{"name":"Zenon","symbol":"ZNN","decimals":18},
"explorers":[{"name":"Zenon Explorer","url":"https://explorer.zenon.org"}]
```
The alternative is to hard code the Public RPC Nodes into the code or create a `.json` for each application, but that could be hard to manage and duplicate information needed in multiple apps.
Do you guys have any opinions on this idea? If not, we will move forward as proposed.
---
### Author:  [@CryptoFish](https://forum.hypercore.one/u/CryptoFish)
#### Post date: [February 29, 2024, 2:41pm UTC](https://forum.hypercore.one/t/zenon-public-rpc-node-database-repo/386/2 "2024-02-29T14:41:26Z")
I think it’s better to the json file as basic as possible. Just a list of strings representing the rpc urls.
This [PR](https://github.com/zenon-network/syrius/pull/69) contains a working example in which the node file is copied by the workflow and loaded as an asset by syrius.
Currently using [HyperCore-One:zenon-node-database](https://github.com/hypercore-one/zenon-node-database) as the central repository because of permission limitations on zenon-network.
---
### Author:  [@0x3639](https://forum.hypercore.one/u/0x3639)
#### Post date: [February 29, 2024, 6:18pm UTC](https://forum.hypercore.one/t/zenon-public-rpc-node-database-repo/386/3 "2024-02-29T18:18:26Z")
> [@CryptoFish](#):
>
> I think it’s better to the json file as basic as possible. Just a list of strings representing the rpc urls.
this makes sense to me too.
> [@CryptoFish](#):
>
> This [PR](https://github.com/zenon-network/syrius/pull/69) contains a working example in which the node file is copied by the workflow and loaded as an asset by syrius.
By doing this users can modify this file locally themselves after installing `syrius`.