# Public RPC Nodes in syrius v0.2.0

**URL:** https://forum.hypercore.one/t/public-rpc-nodes-in-syrius-v0-2-0/385
**Category:** Development
**Created:** [February 28, 2024, 11:14am UTC](https://forum.hypercore.one/t/public-rpc-nodes-in-syrius-v0-2-0/385 "2024-02-28T11:14:54Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![0x3639](https://forum.hypercore.one/user_avatar/forum.hypercore.one/0x3639/32/33_2.png) [@0x3639](https://forum.hypercore.one/u/0x3639)
#### Post date: [February 28, 2024, 11:14am UTC](https://forum.hypercore.one/t/public-rpc-nodes-in-syrius-v0-2-0/385/1 "2024-02-28T11:14:54Z")

</div>

We are moving forwards towards a `syrius v0.2.0` release. Like other blockchain wallet, we are offering (trusted) public RPC nodes for users to select if they don’t want to sync. Today in TG Main we have three options. I would like to proposing adding @coinselor’s node to the list in `syrius`.

@coinselor is that OK and does anyone object?

 ![image](https://hypercore.nyc3.digitaloceanspaces.com/original/1X/03f6acd76fc3e6c4cb52c432e5d81181f951466d.jpeg)

In the future we need to come up with a better way to add / remove nodes. Maybe we have a `.json` file in the `syrius` repo that community members can submit PRs on to add / remove nodes. Does anyone have ideas for this?

Maybe we have a stand alone `nodes.json` file that is easy to find with instructions in the readme.md explaining how to add / remove nodes. Basically fork the repo, make the change, submit PR. And we can establish minimum requirements to be considered.

---

<div class="post-metadata">

### Author: ![coinselor](https://forum.hypercore.one/letter_avatar_proxy/v4/letter/c/41988e/32.png) [@coinselor](https://forum.hypercore.one/u/coinselor)
#### Post date: [February 28, 2024, 11:30am UTC](https://forum.hypercore.one/t/public-rpc-nodes-in-syrius-v0-2-0/385/2 "2024-02-28T11:30:44Z")

</div>

It’s ok by me, but my node is currently not as robust as the other two and should be the last considered option. I still need to configure a load balancer in front and setup a couple backup locations, devops noob here so I’m learning as I go.

---

<div class="post-metadata">

### Author: ![CryptoFish](https://forum.hypercore.one/user_avatar/forum.hypercore.one/cryptofish/32/41_2.png) [@CryptoFish](https://forum.hypercore.one/u/CryptoFish)
#### Post date: [February 28, 2024, 12:23pm UTC](https://forum.hypercore.one/t/public-rpc-nodes-in-syrius-v0-2-0/385/3 "2024-02-28T12:23:04Z")

</div>

The public nodes are randomized each time they are loaded, so there is no difference or any meaning attached to one particular node.

The public nodes are currently hard-coded. It is possible to setup a separate repo specifically for the purpose for maintaining a public node database. Something similar as to what ledger does with the [ledger-app-database](https://github.com/LedgerHQ/ledger-app-database).

PR’s are made to add or remove app registrations from the list, which is basically one big json file.

In our case the repo would serve as a public node database which can be used by various applications. bc I believe syrius isn’t the only application in need of this list.

Once the repo is setup, syrius can use the repo from within the build workflow. This would still require a build to include the latest version, but it does separate the list from the syrius repo. Making it available for other applications to use and in the same time have some standardized way of maintaining it.

---

<div class="post-metadata">

### Author: ![aliencoder](https://forum.hypercore.one/user_avatar/forum.hypercore.one/aliencoder/32/49_2.png) [@aliencoder](https://forum.hypercore.one/u/aliencoder)
#### Post date: [February 28, 2024, 4:40pm UTC](https://forum.hypercore.one/t/public-rpc-nodes-in-syrius-v0-2-0/385/4 "2024-02-28T16:40:15Z")

</div>

> [@CryptoFish](#):
>
> The public nodes are currently hard-coded

And they have a “Community” label for increased transparency.
