Repo brief: tronprotocol/java-tron

Generated by RepoPilot · document generated 2026-09-13 · concise human review Evidence snapshot · analyzed 2026-09-13T20:35:56.073Z · commit 4a21592f95e3

Verdict

Healthy — Strong maintenance signals

• Last commit 5d ago
• 14 active contributors
• Distributed ownership (top contributor 25% of recent commits)
• LGPL-3.0 licensed
• 2 more receipts on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard

What it is

java-tron is a Java implementation of the TRON blockchain protocol, a DPoS-based blockchain OS capable of 2000+ TPS with a TVM (TRON Virtual Machine) that is EVM-compatible for smart contract execution. The actuator module specifically handles transaction processing through a pluggable chain of actuators that validate and execute blockchain state transitions for assets, accounts, contracts, freezing, delegating, proposals, and exchanges. Monorepo structure: root project with submodules including actuator/ (transaction execution engine), chainbase/ (state storage), protocol/ (protobuf definitions), and crypto/. Actuator module uses factory pattern (ActuatorFactory, ActuatorCreator)…

Start here

Open these first:

• actuator/src/main/java/org/tron/core/actuator/ActuatorFactory.java — Central factory that instantiates and routes all transaction actuators; critical to understanding the dispatch mechanism.
• actuator/src/main/java/org/tron/core/actuator/AbstractActuator.java — Base abstraction for all transaction execution logic; defines the validate/execute contract every actuator must follow.
• actuator/src/main/java/org/tron/core/vm/VM.java — Virtual machine implementation for smart contract execution; core to TRON's computation model.
• actuator/src/main/java/org/tron/core/vm/program/Program.java — Program state container managing execution context, memory, stack, and storage during VM runs.
• actuator/src/main/java/org/tron/core/actuator/VMActuator.java — Bridges transaction execution framework with VM; routes contract calls to the virtual machine.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

Clone: git clone https://github.com/tronprotocol/java-tron.git && cd java-tron. Install dependencies via provided script: chmod +x install_dependencies.sh && ./install_dependencies.sh. Build: infer Gradle-based buil…

Daily commands:

Repository data shows build configuration but not run commands. Standard Gradle workflow: ./gradlew build to compile. Running a full node likely requires: ./gradlew actuator:run or similar submodule invocation, with…

…shortened for this brief.

Key cautions & unknowns

• LGPL-3.0 is copyleft — check downstream compatibility
• JDK version is strictly tied to CPU architecture (JDK 8 for x86_64, JDK 17 for ARM64) and not interchangeable; building on wrong JDK will fail. Test heap is capped at 1200m (actuator/build.gradle maxHeapSize); large…
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests
• OpenSSF Scorecard

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.