Skip to content

docs: note public testnet RPC method differences across follow endpoints #373

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kutluhaneth46 wants to merge 2 commits into
base: main
Choose a base branch
from
Open

docs: note public testnet RPC method differences across follow endpoints #373

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d97d824
docs: note public testnet RPC method differences
kutluhaneth46 Sep 9, 2026
d72c8f6
docs: tighten public RPC capability note from review
kutluhaneth46 Sep 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions docs/running-an-arc-node.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -225,6 +225,34 @@ companion execution layer.
The consensus layer operates in the **follow** mode.
We provide three endpoints from which the node retrieves finalized blocks.

> **Public testnet RPC methods are not identical across providers for
> application clients.** Follow sync itself is unaffected: the follow client
> only needs `eth_getBlockByNumber`, `eth_call`, `eth_chainId`, and
> `net_listening`, and those work on every public host below. Note the
> differing WebSocket paths in the command above when swapping providers.
>
> The gap is for dapp/bridge/light-client callers that need EIP-1186 proofs or
> access lists. Observed 2026-09-09 against the public fleet (see #371):
>
> | Endpoint | `eth_getProof` | `eth_createAccessList` |
> |---|---|---|
> | `rpc.testnet.arc.io` | unsupported (codes flip) | unsupported (`-32601`) |
> | `rpc.drpc.testnet.arc.io` | OK | OK |
> | `rpc.quicknode.testnet.arc.io` | unsupported (codes flip) | unsupported (`-32601`) |
> | `rpc.blockdaemon.testnet.arc.io` | OK | filtered (`-32003`); a batch containing it is rejected in full, losing unrelated calls |
>
> Prefer `rpc.drpc.testnet.arc.io` when you need proofs or access lists. Some
> hosts return `-32601` (method unsupported) for one call and `-32014` (data
> unavailable) for the next, for the same request. Do not branch on the code —
> treat any error from a capability probe as "unsupported on this host" and
> fail over.
>
> ```bash
> curl -s -X POST -H 'Content-Type: application/json' \
> --data '{"jsonrpc":"2.0","id":1,"method":"eth_getProof","params":["0x3600000000000000000000000000000000000000",["0x0"],"latest"]}' \
> https://rpc.testnet.arc.io
> ```

### Verify operation

After starting both the consensus and execution layer, wait about 30 seconds.
Expand Down