Bring your own RPC

Route the app's Ethereum reads through your own RPC endpoint instead of the default providers. Useful when the defaults are throttled, when you want privacy from third-party node operators, or when yo

Every action in 10102 Computing Legacy that reads on-chain state (checking a legacy's status, listing beneficiaries, verifying ownership, etc.) goes through an Ethereum JSON-RPC endpoint. By default the app rotates through a list of providers we configure, so a single provider being slow or rate-limited doesn't take the app down.

If you have your own node, a paid Alchemy/Infura/drpc key, or simply prefer not to depend on the providers we ship, you can point the app at your endpoint instead.

How it works

The app supports the draft dAppSpec query-parameter convention:

?ds-rpc-<chainId>=<url-encoded-rpc-url>

When present, the endpoint you supply is used for that chain with higher priority than anything we configure. Any provider throttling on our side is bypassed entirely.

The override is also remembered across reloads (saved to your browser's local storage for this origin), so you only have to paste the URL once.

Examples

Mainnet

Append to any page URL:

?ds-rpc-1=https%3A%2F%2Feth-mainnet.g.alchemy.com%2Fv2%2FYOUR_KEY

or, with a self-hosted node:

?ds-rpc-1=https%3A%2F%2Frpc.mynode.example%2F

Sepolia (testnet)

?ds-rpc-11155111=https%3A%2F%2Fsepolia.infura.io%2Fv3%2FYOUR_KEY

Multiple chains at once

You can override both chains in the same URL:

?ds-rpc-1=https%3A%2F%2Fmainnet.example%2F&ds-rpc-11155111=https%3A%2F%2Fsepolia.example%2F

Clearing a saved override

Either:

• Navigate to any page with an empty override value, which resets the saved endpoint:

  ?ds-rpc-1=

• Or clear your browser's site data for the app domain. Both remove the persisted override; the app will fall back to the default providers on the next load.

Automatic eviction on repeated failure

If the override endpoint fails several requests in a row at the network level (DNS failure, timeout, connection refused, HTTP error), the app evicts it automatically and falls back to the defaults for the rest of the session. You'll see a one-line warning in the console like:

[rpc] chain 1: user-override evicted after 5 consecutive failures (was: https://…). Falling back to the default providers.

Eviction is triggered strictly by transport-level failures. A working node that responds with a valid JSON-RPC error (for example, the node saying "that method is not supported") does not count toward eviction, because that means the node itself is healthy. Any successful request resets the counter, so an endpoint that's generally fine but occasionally slow won't get evicted by coincidence.

Once evicted, the app won't auto-reinstate the same endpoint. You can reconfigure one by supplying a fresh ?ds-rpc-<chainId>= query parameter.

Verifying the override is active

Open the browser's developer console (usually F12 → Console tab). When an override is in effect, you'll see a line like:

[rpc] chain 1: using user-override from ?ds-rpc-1= (stored for this origin)

After reloads (without the query parameter), the same log appears but mentions it's using the persisted value:

[rpc] chain 1: using persisted user-override (clear with ?ds-rpc-1=)

Things to know

What this changes and what it doesn't. The override affects read calls the app makes to inspect chain state. It does not change how your wallet connects to the network or where your wallet signs/submits transactions; that is controlled entirely by your wallet's own RPC settings. If you want your transactions to also go through your own node, set that inside your wallet (e.g. MetaMask → Settings → Networks).

Trust the endpoint you point at. An RPC provider can, in principle, serve inaccurate reads or link requests to your IP address. Use endpoints operated by parties you're comfortable relying on. The app only accepts http:// and https:// URLs; other schemes (like javascript: or data:) are rejected so the override can't be used to run code.

If your endpoint embeds an API key, restrict it at the provider. RPC keys you paste into the query parameter end up in the browser request (and transiently in your history, screenshots, and any link you share). This is the same exposure model every web dapp has; the fix isn't to hide the key but to lock it down at the provider. Alchemy, Infura, QuickNode all support per-key "allowed origins" restrictions; enable that so even a leaked key is useless from any domain other than yours, and ideally disable eth_sendRawTransaction on read-only keys. Because the app persists your override after the first paste, you only need to put the URL in the query string once, which limits the exposure window.

The override is per-browser, per-origin. Clearing your browser data, switching browsers, or using a private-browsing window all reset the persisted override to the defaults.

See also

• Authentication: how wallets connect and submit transactions.

• Concepts: what the app does with chain state it reads.