Validator node
A validator participates directly in the proposed stake-secured BFT consensus process. It must independently validate protocol rules, maintain signing security, protect validator credentials, meet network participation requirements, and follow the production consensus specification.
Full-verification node
A non-validating full node can independently verify finalized ledger data and transactions without participating in consensus voting. The exact storage and synchronization requirements remain to be specified.
Lightweight wallet client
A lightweight client may rely on compact proofs or trusted network services for some information while keeping authorization credentials local. The production design must document precisely what is and is not independently verified.
Indexer or archival service
An indexer organizes ledger data for search, analytics, accounting, explorers, and application APIs. An archival service may retain historical data that ordinary validating nodes can prune. Neither role should be mistaken for consensus authority.
RPC provider
A hosted RPC provider offers convenient access to network state but introduces service and trust dependencies. High-value applications may use multiple providers or their own verification infrastructure depending on their threat model.