How tronprotocol/java-tron works
Project Type and Purpose
• This is a blockchain full‑node application (“java‑tron”) implementing the TRON Protocol in Java.
• It comprises a distributed P2P network layer, consensus engines (DPoS/PBFT), a smart‑contract VM (TVM), state storage, API layers (HTTP/gRPC), plug‑in actuators, and utilities.
High‑Level Module Breakdown (from file tree)
• actuator: Smart‑contract transaction executors (ActuatorFactory, AbstractActuator, native contracts).
• chainbase / core storage modules: On‑chain data persistence using LevelDB/RocksDB; capsules + stores manage blocks, accounts, contracts.
• common: Shared utilities (args parsing, caching, logging, metrics, zksnark wrappers).
• consensus: DPoS and PBFT engines, message definitions, block handling.
• crypto: All cryptographic primitives (EC keys, hashes, zksnark operations).
• framework: Application bootstrap (ApplicationFactory, ServiceContainer), network handlers (P2P, message processing), RPC/HTTP services, CLI.
• plugins: CLI tools / database utilities (DbConvert, ArchiveManifest).
• protocol: Protobuf definitions for wire formats (P2P, API, contracts).
• example: Sample custom actuator.
• docker / scripts / docs: Deployment tooling and documentation.
Key Interactions
• P2P Network Layer (framework/src/main/java/org/tron/core/net)
– Peers exchange messages (blocks, transactions) over TCP/UDP.
– MessageHandler routes to either consensus or transaction pool.
• Consensus Engines (consensus module & framework core consensus service)
– Receive new transactions/blocks → run DPoS/PBFT algorithms → propose & commit blocks.
• Transaction Execution (actuator + VM submodules)
– Consensus‑approved blocks feed into actuators which interpret transactions (Transfer, Freeze, Smart Contract deploy/invoke) via the TVM.
– Actuators update state in chainbase.
• State Storage (chainbase & framework accountstate/Trie)
– Blocks, accounts, contracts, receipts persisted in on‑disk DB.
– TrieService maintains Merkle Patricia tries for fast lookup.
• API Layer (framework/src/main/java/org/tron/core/services & /common/application)
– HTTP Servlets and gRPC stubs expose JSON‑RPC & REST endpoints for clients.
– Internally they query chainbase, submit transactions into P2P pool.
• Application Bootstrap (framework ApplicationFactory)
– Loads configuration, instantiates services (network, DB, consensus, API), wires dependencies.
– Exposes FullNode / SolidityNode entrypoints.
• External Services & Tools
– Docker container orchestrates ports (8090 HTTP, 18888 P2P, 50051 gRPC).
– start.sh / docker.sh simplify builds & launches.
– Prometheus metrics & logback for observability.
Architectural Patterns & Principles
• Modular microservices within a monorepo: each Gradle subproject is loosely coupled.
• Factory patterns for actuators, consensus, message creation.
• Event‑driven messaging in P2P and backup subsystems.
• Plugin‑style extensibility (custom actuators, database tools).
• Separation of concerns: network / consensus / execution / storage / API layers.