Node Atlas
Public infrastructure preview

Two chains.
One layer.

A public preview of the node infrastructure being shaped for BSC and Ethereum — from the first provision to a clear, observable network presence.

View rollout map Operating model

Architecture phase · endpoints are not live yet

Network topology / draft 01 Planned
Future BSC and Ethereum node topology BSC and Ethereum route into a shared node layer, which branches into RPC, sync, and health signals. BSC ETH NODE LAYER RPC SYNC HEALTH CHAIN INPUT PLANNED OUTPUT OBSERVABLE BY DESIGN

The network surface is still being drawn.

Two chain surfaces, one operating rhythm. The labels below describe the intended shape, not a live service or a promise of availability.

01 / chain surface

BSC

A planned node surface for BSC, with the role, provider and public access layer to be finalized during provisioning.

State Planned
Layer Node / RPC
The future BSC surface will be evaluated around reliable synchronization, clear health signals and a deliberately small public interface.
02 / chain surface

Ethereum

A planned Ethereum node surface, designed to make network state legible before any endpoint is opened to the public.

State Planned
Layer Node / RPC
The future Ethereum surface will be evaluated around sync visibility, operational boundaries and a stable path from node state to usable access.

A rollout with room for the hard parts.

The sequence keeps the public surface quiet while the operational layer earns its shape.

  1. 01

    Shape the node layer

    Confirm node roles, storage, network boundaries and the signals that matter before exposing access.

    In design
  2. 02

    Provision and observe

    Bring BSC and Ethereum surfaces online privately, then make sync and health behavior legible.

    Next phase
  3. 03

    Open the useful edge

    Publish the smallest dependable interface once the underlying node state can be trusted.

    Future

The node is only the beginning.

The useful product is the layer around it: access that is understandable, state that is visible, and boundaries that stay deliberate.

  • RPC access
  • Block synchronization
  • Health and alert signals
  • Clear public status