| HTTP reads and batches | Supported; you configure and operate upstreams. | Managed or account-owned provider pools. | History, method support, quotas, and parameters depend on eligible upstreams. Batches route items independently and do not pin a snapshot. |
| Signed transactions | One upstream dispatch for eth_sendRawTransaction. | Conservative single dispatch. | An acknowledgment is not inclusion or finality. Reconcile an indeterminate result by transaction hash. |
WebSocket unary requests, newHeads, and logs | Supported; enable intended providers and protect your endpoint. | Account-key WebSocket access is advertised. Anonymous-key WebSocket access is not. | Recovery is bounded. Reconnect and reconcile application checkpoints after termination. Pending-transaction subscriptions are outside the released subset. |
| Historical state and log ranges | Forwarded subject to provider capabilities. | Provider capability and availability constrain routing. | No universal archive depth or log-range guarantee. Qualify your exact historical witnesses. |
| Stateful filters | Can forward when capability policy permits, without cross-request upstream affinity. | Rejects the documented HTTP filter lifecycle locally with -32601. | Use eth_getLogs or supported subscriptions; filter IDs are provider-local. |
| Block regression protection | Opt-in local policy with best-effort peer recovery; optional coordinated policy requires its own operating setup. | Custom-profile On/Off control for local protection. | Local protection covers sequential choices within one running application generation. A server switch or restart can return a lower block. |
| Hash-selected state reads | Explicit selectors are retained through routing and retries. | Same documented application pattern. | Choose and carry one hash through every read; upstream state and selector support are required. This is not finality or execution proof. |
| Identity, billing, incoming customer quotas | Outside Core. Protect exposed endpoints through your network or reverse proxy. | Account, key, entitlement, and usage services. | Profiles do not multiply an upstream account’s quota. Account and anonymous CU differ. |
| MPP funding and paid sessions | Outside Core. | Implemented paths, disabled in production at the observation above. | Check the live manifest before attempting payment. Legacy Tempo protocol support does not imply current CLI compatibility. |
| Sustained workload capacity | Depends on your deployment and providers. | Depends on workload, profile, providers, and service policy. | The linked evidence does not establish a general 24-hour, seven-day, or 30-day operating envelope across these workloads. |