TRON DAO has released GreatVoyage-v4.8.2, codenamed Pyrrho, as a mandatory upgrade for the network’s node infrastructure. Operators running full nodes and solidity nodes must complete the migration by August 16, 2026, at 23:59 SGT.
Missing the deadline could cause synchronization failures and loss of network relay capabilities. For affected infrastructure providers, that may interrupt block production, RPC services and downstream applications relying on consistent node data.
Pyrrho Aligns TVM With Ethereum Standards
The release updates the TRON Virtual Machine to support features associated with Ethereum’s Pectra and Osaka roadmaps. This alignment is intended to preserve compatibility as Ethereum-style execution environments adopt new instructions and cryptographic primitives.
Pyrrho adds native support for the CLZ instruction and secp256r1 signature verification precompiles. These capabilities expand the operations available to compatible smart contracts and standardize certain cryptographic workflows within the TVM.
The upgrade also replaces the fastjson dependency with Jackson for API processing. That migration modernizes part of the node software stack and requires operators to account for changes in application and interface behavior.
TRON is additionally moving node-level monitoring from InfluxDB to Prometheus. Infrastructure teams will need to update observability configurations so performance, synchronization and system-health metrics remain visible after migration.
Event Plugin Users Face Strict Upgrade Sequence
Operators using TRON’s official Event Plugin must upgrade the plugin to version 3.0.0 before installing java-tron v4.8.2. Applying the changes out of sequence could create compatibility problems across event indexing and node services.
The mandatory classification makes Pyrrho a coordinated infrastructure transition rather than an optional feature release. Every affected operator must follow the migration sequence to remain aligned with mainnet rules after the cutoff.
TRON DAO has published migration guides and compatibility checklists to support the rollout. The next operational indicators will be node adoption, plugin migration progress and network stability as the August 16 deadline approaches.