Skip to content
Crypto.world

The Ledger

TRON Marks GreatVoyage v4.8.2.4 a Mandatory Node Upgrade

TRON’s GreatVoyage-v4.8.2.4 release, codenamed Empedocles, is marked as a mandatory upgrade and lists two changes addressing uncommon execution and smart-contract storage cases. The release notes also describe signed JARs and provide no adoption deadline or activation block height.

TRON Marks GreatVoyage v4.8.2.4 a Mandatory Node Upgrade

Empedocles is labeled mandatory

TRON’s java-tron project released GreatVoyage-v4.8.2.4, codenamed Empedocles, on October 22, 2026, and marked it “Mandatory upgrade.” The update addresses two areas: consistency and stability in rare operations cases, and smart-contract storage and metadata handling in edge cases. The release notes do not give an adoption deadline or an activation block height.

Source github.com

The project describes the first change as: “Improve operations execution consistency and stability in rare cases.” The second says it will “Optimize smart contract storage and metadata handling in edge cases.” Both are tied to pull request #7053 in the release notes. The list does not describe them as new user-facing features.

Two edge-case fixes, no broader feature list

The notes provide no incident report, exploit disclosure or estimate of how often either condition occurs. They also do not detail the underlying code paths or quantify a performance change. The stated scope is limited to improved handling in uncommon execution scenarios and contract-storage cases, rather than a general redesign of transaction processing.

The release page labels the update mandatory but does not explain the risk behind that requirement. It does not frame the release as a response to a confirmed attack or network outage. For operators planning deployment, the published notes offer the mandatory designation and the two listed changes, without a stated cutoff date or further explanation of the upgrade’s urgency.

Pull request specifies node and block versions

The linked pull request says the node version becomes 4.8.2.4 and the block version becomes 39. Those are version identifiers, not an activation height; the release entry itself specifies no block height for adoption. The pull request lists unit tests covering storage access and contract metadata.

“The node version becomes 4.8.2.4, and the block version becomes 39.”

yanghang8612, pull request author

GitHub shows the change was merged into the release branch on October 22, 2026. The pull request title describes its scope as improving execution consistency and storage handling, matching the two items in the release notes. The release is associated with commit 4e8389f, which GitHub marks as signed and verified; the page gives GPG key ID B5690EEEBB952194.

Signed JARs cover x64 and aarch64

The release page lists 20 assets, including FullNode JARs for x64 and aarch64 systems. The listed FullNode-x64.jar is 139 MB, while FullNode-aarch64.jar is 193 MB. The project says all available JAR files in the release are signed with its GPG key and provides corresponding signature files. It directs users to match each JAR with the signature file bearing the same prefix, then follow its verification instructions.

The asset notes identify JARs without a platform suffix as standard builds intended for x86_64 architecture. That note distinguishes the standard build from the separately named x64 and aarch64 assets. Operators can use the architecture labels to select a package and the matching signature file to check its authenticity before replacing a running build. The release page does not give a separate installation deadline or specify a different procedure for validators and other node operators.

A mandatory step after v4.8.2.3

Empedocles follows GreatVoyage-v4.8.2.3, released September 30, 2026, which the repository also labels a mandatory upgrade. That earlier release listed changes to smart-contract storage access, BN128 pairing performance and parsing of node-generated JSON responses. Version 4.8.2.4 instead lists operations-execution consistency and storage and metadata handling in edge cases.

The repository’s release page labels v4.8.2.4 as the latest java-tron release. Its notice states that the upgrade is mandatory, while the accompanying notes remain limited to two edge-case changes and signed software packages. The release entry provides no activation height, adoption deadline or wider protocol feature list.

Sources

  1. Original source · Release notes GitHub (tronprotocol/java-tron) · page 1 github.com

Other pages read

  1. GitHub (tronprotocol/java-tron) · page 2 github.com
  2. GitHub (tronprotocol/java-tron) · page 3 github.com

Related stories

Explore

More articles