Skip to main content

Telos Nodes and Clients

Telos Zero nodes run TelosZero Core, the Telos-maintained nodeos distribution with Savanna instant-finality support. The package also provides cleos, keosd, and spring-util.

Every Telos Zero nodeos validates the chain, but operators configure different roles:

  • Block producer/finalizer: publishes scheduled blocks with a K1 key and votes on blocks with a BLS key.
  • Vote relay/sentry: isolates private producers and forwards blocks, transactions, and finalizer votes.
  • API node: serves chain RPC to applications without production keys.
  • State History (SHiP) node: streams block, trace, state, and optional finality data to indexers.
  • Seed/P2P node: provides stable entry points to the peer network.

See Types of Nodes for role boundaries and Block Producing Nodes for the post-Savanna producer runbook.

For Telos EVM RPC, Telos uses telos-reth with the Telos consensus client. That stack consumes Telos Zero/SHiP data; it does not replace the Telos Zero consensus node.

Operator sources​

Always use the tagged release and checksum approved for the target network. Do not select a producer binary solely from the version string returned by a public RPC endpoint.