Use the deployed JSON-RPC endpoint as a filtered integration surface. A method present in node code or in a source catalog is not necessarily enabled on the public gateway.
Availability is method-specific. Clients must handle policy denials, rate limits and feature gates without retry storms.
Send HTTPS POST requests to https://rpc.talero.info/rpc. The public gateway does not publish node REST routes at /health, /ready or /api/v1/*.
curl -sS https://rpc.talero.info/rpc \
-H 'content-type: application/json' \
--data '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'
The expected public-testnet chain ID is 0x389a6 (231846). Applications should still validate the returned chain ID before signing or submitting anything.
| Control | Current public contract | Client behavior |
|---|---|---|
| JSON body | Maximum 64 KiB | Split large requests. |
| Batch | Maximum 5 calls | Count each call and keep batches small. |
eth_getLogs
|
Maximum 2,000 blocks per request | Paginate ranges and de-duplicate results. |
eth_feeHistory
|
Maximum 1,024 blocks | Request only the history needed. |
| Heavy methods | Higher request cost and tighter budgets | Honor 429 and Retry-After. |
Batches do not bypass limits: the gateway applies a cost to every call and to the request as a whole. Debug, trace, broad search, simulation and range-style calls can be denied even when the HTTP request itself is valid.
Use documented examples as representative, not as a permanent allowlist. Common public reads include eth_chainId, eth_blockNumber, block and transaction lookup methods, bounded eth_getLogs, talero_runtimeReadiness, talero_finalizedHead, talero_getPqNodeStatus and talero_txCapabilities. Availability can change with the deployment profile.
| Outcome | Meaning |
|---|---|
-32050
|
The method is disabled or not allowed by the deployed profile. |
-32005, HTTP 413 or 429
|
A size, batch, range, cost or rate limit was exceeded. |
-32602
|
The method was reached but the parameters are invalid; this is not proof that every valid form is publicly allowed. |
Never infer public availability from a method name in source code, a capability label or a catalog count. Administrative, mining, signer, raw-proof and internal diagnostic surfaces require separate deployment profiles. Use the Explorer API for indexed presentation data and the pool’s authenticated interfaces for miner-specific data.