Node operations

This chapter is for operators running TRON node software — Fullnode, Lite Fullnode, or SR node. It covers what each node type is, how to deploy and bootstrap one, how to keep it healthy, and how to plug it into an event-subscription pipeline for downstream indexers and analytics.

📘

Prerequisites

• Networks — Mainnet, Shasta, Nile endpoints
• Consensus and DPoS — what your node verifies

In this chapter

• Nodes overview — what a node is, the two node types (Fullnode and Lite Fullnode), motivations for running one, and the self-host vs hosted-API decision
• Deploy a node — hardware, JDK, JAR sources, GC flags, startup options, SR-node configuration, Lite Fullnode deployment from snapshot
• Main net database snapshots — bootstrap a fresh node from a recent snapshot to skip multi-day cold sync
• TRON private chain — bring up a private chain for testing, with a non-Mainnet p2p.version and a short Maintenance Period
• Node maintenance toolkit — the Toolkit.jar CLI for database backup, LevelDB / RocksDB conversion, snapshot pruning, and storage rollback
• Event subscription — four ways to receive on-chain events (TronGrid HTTPS, TronWeb, the Fullnode's built-in ZeroMQ publisher, or self-hosted Kafka / MongoDB plugins), plus the V1.0 / V2.0 event service framework and the seven event trigger types

Related resources

• Super Representatives — for nodes that produce blocks
• Network parameters — committee-modifiable chain parameters your node enforces
• SR best practices — availability, security, monitoring, and upgrade hygiene for production SR operators
• Troubleshooting — node operations issues — sync issues, LevelDB / RocksDB picks, Lite Fullnode behavior, the different resultCode failure mode