Telos Node Quickstart
Telos Zero nodes run TelosZero Core. The same nodeos binary can be configured as a private producer/finalizer, vote relay, public API node, State History node, or P2P seed. Start with Types of Nodes to keep security, storage, and plugin responsibilities separate.
Block producer and Savanna finalizer
A post-Savanna BP signs scheduled blocks with a K1 key and finalizer votes with a separate BLS key. Instant finality is part of the normal producer role, not an optional activation step or separate service.
- Review the producer role.
- Install the approved TelosZero Core release.
- Configure and register the private producer.
- Set up, register, verify, rotate, and recover the finalizer.
API, SHiP, relay, and exchange nodes
Non-producing nodes do not need BLS keys. Pure API and SHiP nodes outside a BP vote path can leave vote processing disabled; an intermediate vote relay needs positive vote-threads but no finalizer key.
- Run a non-block-producing Telos Zero node
- Upgrade an exchange/API node to TelosZero Core
- Review public node providers
Telos EVM data nodes
Telos EVM RPC and indexing use the Telos consensus/SHiP stream with an EVM execution and history stack. See telos-reth and the Telos EVM Docker controller for those deployment paths.