We’re aware of recent struggles with RPCs on the chain, impacting the user experience from protocol site-load to transaction reliability on the chain.

There are multiple steps we’re currently taking to resolve the issue which we’ll share below, along with some additional steps users can take to help ensure transaction reliability on the chain.

On the protocol side, we are currently implementing alternatives to dRPC as the sole public node provider on the chain.

A Tenderly public RPC is now available to all users, updated in Docs:https://tangible-real.gateway.tenderly.co/

We’re submitting a PR to ChainList to integrate Tenderly as an additional public RPC to users.

We’re also in talks with additional public RPC providers to add to the list.

Each protocol on re.al has access to a minimum of two nodes (dRPC and Tenderly) and in the event of total failure of one of the nodes, the data is routed to another. We are working on a solution that would make load balancing between the existing RPC nodes even better. As additional node providers are added (noted above) those will be added to the solution, further improving load balancing across the network.

Users on re.al also have the option to set-up their own private RPC from either Tenderly or dRPC. It’s completely free and takes less than 5 minutes. Below is a quick tutorial on set-up for both providers.

Each provider has its upsides. On dRPC you can specify which IPs or domains can use your private RPC. But Tenderly has recently been more reliable.

There’s no harm in making two private RPCs to use based on need/circumstance.

Visit Tenderly.co and click the Sign-Up button on the top right.

On the sign-up screen, feel free to use Google or GitHub to quickly move through the process, we used Google for our account.

Once you’re logged in, select “Node RPCs” at the top of the left-hand navigation bar.

You can then create a new node following these steps:

1. Searching for “real”

2. Selecting it from the list of networks

3. Naming your private node

4. Clicking “Create”

You’ll be directed to your Private Node page where you can copy your private Tenderly RPC Url.

Grab the HTTP URL at the top (not WSS) and drop it into MetaMask or your preferred DeFi wallet.

It’s easy to add your new RPC URL into MetaMask:

1. Got to Settings

2. Network

3. Select re.al (this opens MetaMask full screen)

4. Replace the dRPC URL with your private Tenderly URL copied from above

5. Save

Visit drpc.org and click the Connect button on the top right.

On the sign-up screen, feel free to use Google or your DeFi wallet to quickly move through the process, we used Google for our account.

Click on the “Create new” button on the right, name your new API Key and click “Create.”

On the following screen you’ll search for re.al and then copy your new private RPC URL.

Past your new RPC URL into MetaMask using the steps above.

We’re aware of recent struggles with RPCs on the chain, impacting the user experience from protocol site-load to transaction reliability on the chain.

There are multiple steps we’re currently taking to resolve the issue which we’ll share below, along with some additional steps users can take to help ensure transaction reliability on the chain.

On the protocol side, we are currently implementing alternatives to dRPC as the sole public node provider on the chain.

A Tenderly public RPC is now available to all users, updated in Docs:https://tangible-real.gateway.tenderly.co/

We’re submitting a PR to ChainList to integrate Tenderly as an additional public RPC to users.

We’re also in talks with additional public RPC providers to add to the list.

Each protocol on re.al has access to a minimum of two nodes (dRPC and Tenderly) and in the event of total failure of one of the nodes, the data is routed to another. We are working on a solution that would make load balancing between the existing RPC nodes even better. As additional node providers are added (noted above) those will be added to the solution, further improving load balancing across the network.

Users on re.al also have the option to set-up their own private RPC from either Tenderly or dRPC. It’s completely free and takes less than 5 minutes. Below is a quick tutorial on set-up for both providers.

Each provider has its upsides. On dRPC you can specify which IPs or domains can use your private RPC. But Tenderly has recently been more reliable.

There’s no harm in making two private RPCs to use based on need/circumstance.

Visit Tenderly.co and click the Sign-Up button on the top right.

On the sign-up screen, feel free to use Google or GitHub to quickly move through the process, we used Google for our account.

Once you’re logged in, select “Node RPCs” at the top of the left-hand navigation bar.

You can then create a new node following these steps:

1. Searching for “real”

2. Selecting it from the list of networks

3. Naming your private node

4. Clicking “Create”

You’ll be directed to your Private Node page where you can copy your private Tenderly RPC Url.

Grab the HTTP URL at the top (not WSS) and drop it into MetaMask or your preferred DeFi wallet.

It’s easy to add your new RPC URL into MetaMask:

1. Got to Settings

2. Network

3. Select re.al (this opens MetaMask full screen)

4. Replace the dRPC URL with your private Tenderly URL copied from above

5. Save

Visit drpc.org and click the Connect button on the top right.

On the sign-up screen, feel free to use Google or your DeFi wallet to quickly move through the process, we used Google for our account.

Click on the “Create new” button on the right, name your new API Key and click “Create.”

On the following screen you’ll search for re.al and then copy your new private RPC URL.

Past your new RPC URL into MetaMask using the steps above.