System · RPC providers
Connection settings
See each component's connection choices, health and measured usage. Expand the help beside a setting for its options and effects.
How connections, fallbacks and saved choices work
- Chain feed, tape and gateway
- The chain feed receives and shares block heads and events. Its tape is the ordered pool-event history. The gateway is a separate read RPC proxy inside the feed service: it answers from eligible local caches, Eira or BlockPI. A consumer can use feed events while keeping other reads direct.
- Configured versus active
- A dropdown shows the saved choice. “Heads” shows configured → active; “own” means the component's own head connection. “Current source” is a summary of that card's reported route or state, not the provider of every request. A fallback badge covers reported failures; some individual reads may fall back without changing it.
- Save, reset and restart
- Most dropdown changes apply at runtime. Pool stream and Observer stream choices are saved separately in protected configuration, with no environment changes needed, and apply after a controlled restart. Their rows show the active and saved choices, plus any pending restart. “Set here” means a saved override that normally survives restarts and deploys. Live Send follows the same rule while its choice is still allowed and ready. At startup, a non-BlockPI Send choice that is not ready (expired paid eligibility, allowance lock or IO failure, slow disk) or a saved paid-ip choice is moved to BlockPI as a saved, audited fallback with the reason shown; returning needs the guarded switch again. Restoring a Send choice does not arm wallets. Reset runtime connections removes runtime overrides and restores env defaults, which may themselves enable a feed or Eira. It does not reset stream choices. Select BlockPI for pools or Direct for the Live observer to cancel a pending shared-stream choice. Startup drops overrides that are no longer allowed or fail a guard, and records why. Read-only env settings require a service restart or container recreate.
- Allowed choices and guards
- Each service's env default, baseline and
_ALLOWEDlist determine the choices shown. A single choice is locked. Shared stream choices require the service’s protected credentials and readiness checks; saving them does not restart the service. Every Live stream change requires every Live wallet disarmed, flat and idle, and Live pools require observer heads already shared. The server also checks dependencies, so allowed choices can still be refused. Live send changes away from BlockPI require every Live wallet disarmed, flat and idle, plus the typed confirmation; switching back to BlockPI is always allowed and is saved too. - Usage and health figures
- RPS is requests per second; RU is estimated BlockPI request units, not a bill. Hourly estimates reflect recent measured traffic, including gateway spills. “Not measured” means unknown, not zero. Live observer RU includes executor reads too. Socket health and head age describe freshness; tape lag is blocks behind. Store lag, coverage and per-operation fallback details may differ from the card badge.
Loading…
Recent changes and automatic fallbacks
What this history records
Manual changes save a choice; reset restores env defaults; fallback records an automatic route change; dropped records a saved choice refused at startup. An automatic fallback usually keeps the configured choice so the service can return when healthy. This is the recent service audit, not a list of every RPC request.
| When (UTC) | Component | Kind | Setting | From → to | Who / why |
|---|---|---|---|---|---|
| Loading… | |||||