Skip to main content

Custom RPC Provider

Overview​

RPC (Remote Procedure Call) enables communication between external applications like the HOPRd node and the blockchain network. For reliable syncing, balance checks, and blockchain interactions, we highly recommend setting up your own Gnosis Chain node.

RPC Provider Methods​

Here are the different methods for running your own node or connecting to a third-party RPC provider, ranked from most stable to least stable:

1. Run your own gnosis chain node (Most secure and reliable)​

For VPS/PC/Mac users​

To set up a Gnosis chain node, you will need to run both the Execution Layer (EL) and Consensus Layer (CL) clients. Ensure that your hardware meets the necessary requirements:

We recommend using Sedge for an easy node setup. Here's how to get started:

(1) Install sedge: Sedge install guide

(2) Generate a full node setup (without a validator): Generating a full node

(3) Configure log size limitations (Nethermind client v1.27.x):

  • Navigate to the "sedge-data" folder and open the ".env" file.
  • Add this line: NETHERMIND_JSONRPCCONFIG_MAXLOGSPERRESPONSE=300000
  • Save the file and restart the client.

Once the setup is complete and fully synced, you can access your RPC endpoint at http://localhost:8545. For external use, ensure the port is exposed.

Video Tutorial: Watch this gnosis node setup tutorial for step-by-step guidance.

For DAppNode users​

  1. Go to the Stakers section: http://my.dappnode/stakers/gnosis
  2. Select Nethermind xDai for the Execution Layer and Lighthouse Gnosis for the Consensus Layer. Ensure Use checksync is enabled, then click Apply Changes.
  3. Configure log size limitations (Nethermind client v1.27.x):

After syncing, your RPC endpoint for the HOPR node will be http://nethermind-xdai.dappnode:8545.

Video Tutorial: Follow this Gnosis node setup tutorial for DAppNode for visual instructions.

2. Use third-party RPC providers (Moderately stable)​

We recommend using a third-party RPC provider that runs on the Nethermind execution client. These options are typically free and reliable enough for running your node:

3. Use public RPC endpoints from Chainlist (Least reliable)​

You can find public RPC endpoints from Chainlist.org, but note that these are often unstable due to heavy usage. We recommend caution when using these endpoints as they might go offline or rate-limit your HOPRd node.

Table of Contents