Reads and execution safety
Common Ethereum reads such aseth_blockNumber, eth_getBalance, eth_call,
eth_getTransactionReceipt and eth_getLogs route to any provider whose
capability, transport, history and parameters fit the request.
Replay-safe methods can fail over to further providers within the original
deadline. Unknown methods get one upstream dispatch, whatever the provider
error says.
Core rejects an HTTP endpoint whose eth_chainId probe is malformed or names
another chain, until a later probe matches. Endpoints not yet probed stay
eligible. The check covers HTTP endpoints only.
Signed transaction submission
Without a chaintransactions block, eth_sendRawTransaction receives one
upstream dispatch, and Lasso does not retry or fan out after dispatch. A lost response may mean the upstream accepted the
transaction. Clients remain responsible for signing, nonce management,
replacement, transaction-hash reconciliation, receipts, and finality.
Relay-native submission methods, bundle methods, simulations of signed
transactions, and any other method whose params carry signed transaction
bytes are classified the same way and also run once. A chain’s
transactions configuration
restricts sends to the providers it names. Registered send methods may
then resend the same bytes to another of those providers, up to three dispatches
within the request deadline; a method classified only by its signed bytes still
runs once. Profiles without the block keep ordinary one-dispatch routing. Opt-in metadata reports the
chosen execution class
as execution_safety and how it was decided as classified_by.
Node-local methods
The transport policy globally disallowseth_sendTransaction, eth_accounts,
eth_sign, eth_signTransaction, and personal_sign. Provider capability
policy can reject additional methods, including the local_only category.
Do not treat a profile as an authentication or authorization boundary.
Stateful filters and extensions
RPC Core can forward provider-local filter methods when capability policy permits them. They receive one dispatch per request and have no cross-request affinity guarantee. A filter ID created on one upstream may be invalid on a later selected upstream. Prefereth_getLogs or supported WebSocket subscriptions;
Core does not advertise a reliable multi-provider filter lifecycle.
Debug, trace, transaction-pool, bundler, and chain-specific methods depend on
upstream support and configured restrictions. Their presence in a registry does
not provide sticky sessions, common history, or a universal parameter contract.
WebSocket subscriptions
The supported stream kinds arenewHeads and logs. Use:
eth_unsubscribe with the returned subscription ID to stop the stream.
Pending-transaction subscriptions are not part of this released subset.
HTTP subscription requests return a method error with a WebSocket URL hint.
Matching client streams can share upstream subscriptions. Establishment requires
a usable upstream before returning a subscription ID. Recovery uses bounded HTTP
replay and a replacement live stream. Recovery beyond its time, replay, attempt,
or buffer limits terminates the affected downstream connection explicitly; it
does not promise unbounded or lossless delivery through arbitrary outages.
subscribe_new_heads controls automatic block monitoring and
client newHeads eligibility. Providers inherit the chain setting, which
defaults to true; override it per provider when needed. New profiles
can reuse an already-connected upstream after a successful configuration reload.
See Configuration and Deployment.
HTTP batches
HTTP endpoints accept arrays with up to 50 items by default (max_batch_requests).
Items are validated and routed independently with bounded concurrency. A batch
is not an atomic state snapshot and does not pin every item to one provider.
Response items retain request order. Valid notifications produce no response;
an all-notification batch returns HTTP 204. Use unique IDs for correlation.
Deployment boundary
Core does not authenticate clients or enforce incoming customer quotas. Protect RPC, metrics, and dashboard endpoints through your network or reverse proxy. Profile tester settings do not create API quotas or upstream quota isolation. The authoritative implementation isTransportPolicy, ExecutionEnvelope,
Capabilities, RPCController, and RPCSocket.ItemOwner at the selected release.
See API reference for routes and metadata.