ZOOBC / GATEWAY
This Gateway
ZooBC Gateway status, system resources, live chain figures, node routing, tools, and operator links.
Choose a network
A gateway belongs to the network it fronts. Each one reports its own status, its own allowlist, and the nodes it can actually reach.
MainNet opens 14 February 2027
01 / WHAT A GATEWAY IS
The HTTPS front door
A gateway terminates TLS, rate-limits, and proxies the chain API to the nodes behind it. That is the whole job. It holds no keys, decides nothing about consensus, and cannot change what the chain says.
It exists so a browser can talk to ZooBC without running a node. Everything it serves is also obtainable by asking a node directly, which is the point: a gateway is a convenience, never an authority.
02 / WHAT IT REPORTS
Status, and what it can reach
The status view shows the gateway's own mode and domain, how many nodes are on its allowlist, which of them are answering, and the live chain height it is serving. Those figures come from the gateway itself and from the nodes it proxies.
An unreachable node is reported as unreachable. It is never shown as a zero, because a gateway that cannot reach the chain and a chain with nothing in it are different facts and must not look the same.
03 / RUNNING ONE
Operators
Anyone can run a gateway. The installer sets one up alongside a node or on its own: curl -fsSL https://zoobc.network/install | bash -s -- --gateway. Roles combine, so --node --gateway --relay in one invocation is valid.
The developer guide covers the endpoints a gateway exposes, how GET and POST are routed differently, and the allowlist. The gateway API itself is documented under API reference.