Choose RPC access
A chain ID identifies a network; it does not locate its RPC service. Provider access, blockchain gas and wallet authority are separate requirements.
| Use | Endpoint boundary |
|---|---|
| Operator deployment | A complete RPC URL in private instance configuration. It must support reads, fee/gas queries, signed-transaction submission and receipt lookup. |
| Browser viewer | A browser-accessible endpoint with the appropriate CORS/HTTPS behavior. Do not put a private credential into a shared viewer link. |
| Contract indexing | The separate restricted proxy below; event/block reads only, no transaction submission. |
Find the network and available service choices
Use the network table, which reads the same source catalog as the tools. It contains chain IDs, gas tokens, service templates, explorers and dated primary references. To list it in a source checkout:
make release/rpc/list DOCKER_CONTEXT=your-local-contextThe catalog is not a live service test. A shared no-key service can limit traffic or methods. An authenticated URL needs your provider credentials and plan. Check historical-state retention as well as ordinary latest-state access: verification may need the deployment block.
Recorded RPC capabilities
The measurements below come from the rpc/catalog/probe read-only experiment, not from the network catalog's reference dates. The probe checks recent block data, limited event-log queries, hash-addressed calls, and historical reads 4,096 blocks behind the sampled head. Credential-required services are listed but not tested. A method accepting one sample does not prove complete historical state, correct event logs, reliable finality, or future availability.
Loading recorded RPC measurements…
Select the deployment endpoint through the instance
Run the current setup procedure with the app and private instance:
make pay-to-play/release/setup \
DOCKER_CONTEXT=your-local-context \
INSTANCE=/absolute/private/pay-to-play-instanceSupply the complete issued HTTPS RPC URL through setup, not an API key embedded in a shell command. Setup stores rpcUrl in its protected configuration and checks the chain. See the release procedure for the required source, signer and app choices.
Saved operations retain their configuration references. To verify or resume one, use that same instance and select the saved work. Exporting a new endpoint or editing top-level defaults does not silently change the operation's retained choice. Follow recovery when a credential or provider must be restored.
Check the transport, not just its name
The public release boundary requires HTTPS on port 443, public IP addresses, no URL userinfo and no custom authorization headers. A key can be part of the protected issued URL. A write-only sequencer endpoint or beacon API cannot serve the complete execution workflow.
Before broadcasting, the deployment checks the RPC's chain ID against the selected expected chain. That detects disagreement; it does not independently authenticate an untrusted RPC. Private local rehearsals use their explicitly selected Anvil transport instead.
For a browser viewer, choose a separately suitable public endpoint through app setup. The browser contacts it directly; a working RPC on the server does not prove that browser CORS and mixed-content rules permit it. Never reuse a private signing URL in a shareable link.
Run the restricted indexing proxy
This is an independent, persistent service. It keeps one provider URL away from an indexer and permits only:
eth_chainId eth_blockNumber eth_getBlockByNumber eth_getLogsRun the indexer, its database, ABI/address configuration and start blocks separately. This proxy provides HTTP event/block polling, not calls, receipts, traces, WebSocket subscriptions or transaction submission. It restricts methods, not the contracts a client may query.
Start one explicitly selected upstream
As the non-root Docker operator, prepare an existing file outside the checkout containing the complete public HTTPS RPC URL. Its normalized absolute path must have no symlink components; keep it owner-only, such as mode 0600, owned by the invoking operator. Do not place its URL/key in Make arguments or indexer configuration.
make rpc/indexer/up \
DOCKER_CONTEXT=your-local-context \
RPC_URL_FILE=/absolute/private/base-sepolia-rpc-url \
RPC_INDEXER_COMPOSE_PROJECT_NAME=contract-base-sepoliaKeep the file available while the proxy runs. Startup waits for local /healthz and prints:
Client network: contract-base-sepolia_rpc_internal
RPC URL: http://contract-base-sepolia-rpc:8080Health checks local request handling, not provider reachability or chain identity. Configure and verify the expected chain in the indexer. Choose a different project and private URL file for another chain or provider.
Attach only the networks the indexer needs
This is a network fragment, not a complete indexer deployment. Combine it with your pinned indexer/database configuration and use the printed RPC address:
yaml
services:
rindexer:
networks: [base_sepolia_rpc, indexer_database]
postgres:
networks: [indexer_database]
networks:
base_sepolia_rpc:
external: true
name: contract-base-sepolia_rpc_internal
indexer_database:
internal: trueDo not add a default/egress network or share the proxy's network namespace: those can create an unintended internet route. Give the indexer its own database role; keep provider credentials and signing keys out of it. The proxy needs no database access.
Use bounded polling and handle refusal
| Indexing profile | Limit |
|---|---|
| Active connections, including health probes | 4 |
| JSON-RPC batch items | 100 |
| Request / response body | 1 MiB / 16 MiB |
| Connect or socket inactivity | 10 seconds |
| Complete upstream operation | 60 seconds |
| Whole accepted client connection | 90 seconds |
Health probes share capacity. A full worker set rejects new connections, with HTTP 503 and Retry-After when a response can be delivered. Start with low combined indexer concurrency; reduce block ranges for response-size or deadline failures. These limits do not enforce a provider's per-second or daily quota.
The proxy does not retry, cache or switch upstreams. Read-only clients can use bounded backoff. See the profile before changing limits together with container memory/PID budgets.
Inspect or stop the owned service
make rpc/indexer/logs \
DOCKER_CONTEXT=your-local-context \
RPC_INDEXER_COMPOSE_PROJECT_NAME=contract-base-sepoliaStop indexer clients and disconnect them from this proxy's internal network before removal:
make rpc/indexer/down \
DOCKER_CONTEXT=your-local-context \
RPC_INDEXER_COMPOSE_PROJECT_NAME=contract-base-sepoliaLogs and shutdown do not require the original URL file. To rotate it, stop the proxy, replace the protected file and run startup again so its bind mount uses the current file. Local logs are bounded to three 10 MiB files. This guide does not certify a particular live indexer/database deployment.
Maintain one network catalog
Update endpoint templates, references and check dates in the source catalog, not in this guide. Keep existing keys and mainnet indexes stable; testnet entries identify their mainnet by key. Retired entries retain identity but expose no selectable service. A source-check date records a documentation review, not a successful live RPC probe.
Implementation baseline: instance RPC configuration, indexer entrypoints and proxy implementation.