Update, 7 November 2026: the Prague/Osaka activation has since passed. Proposal #107 (ALLOW_TVM_PRAGUE and ALLOW_TVM_OSAKA) was approved by 25 Super Representatives and took effect on 28 August 2026, so the new TVM opcodes are live on mainnet.
The TRON node upgrade to GreatVoyage-v4.8.2 (Pyrrho) is mandatory before 23:59 Singapore time on August 16, 2026, per the official announcement. Miss the deadline and block synchronization breaks. As of Core Devs Meeting #67 on July 31, 19 Super Representatives had already completed the upgrade.
This release is not a routine patch. It removes configuration options that existing setups depend on, changes the monitoring stack, and adds a batch of TVM opcodes borrowed from Ethereum. Two of those changes will break a node that upgrades without preparation.
TRON node upgrade breaking changes, in the order they will bite you
From the official v4.8.2 release notes:
- Event Plugin must go first. Nodes streaming events to Kafka or MongoDB need Event Plugin v3.0.0 or later before the node upgrade. Custom plugins must be adapted. Upgrade the node first and your event pipeline stops.
- RocksDB backup support is gone, along with the
storage.backupconfiguration. If your backup strategy relies on it, you need a new one before August 16, not after. - InfluxDB reporting is removed. Metrics move to Prometheus and Grafana. Two new series arrive:
tron:block_transaction_countandtron:sr_set_change. - Legacy settings are dropped:
net.typeandactuator.whitelistno longer exist. - Custom transaction actuators must now live in the
org.tron.core.actuatorpackage.
We run java-tron ourselves for TronSave’s infrastructure, and the ordering matters in practice: our node image pins the v4.8.2 line and our Kafka event plugin sits at exactly v3.0.0 — the plugin was updated first, deliberately, because the reverse order costs you an event backfill.
There are quality-of-life additions too. Peer settings now accept hostnames instead of raw IPs, API rate limiting became non-blocking, and gRPC logs get their own file at ./logs/grpc/grpc.log.
What the new TVM opcodes actually do
The headline feature is TVM alignment with Ethereum’s Pectra and Osaka upgrades. The TIPs, and what each is for:
| TIP | Change | Why it matters |
|---|---|---|
| TIP-7951 | secp256r1 (P-256) precompile | Verifies signatures from phone secure enclaves and passkeys |
| TIP-7939 | CLZ opcode (count leading zeros) | Cheaper bit-manipulation in contracts |
| TIP-2935 | Historical block hashes served from state | Contracts can read older block hashes reliably |
| TIP-7823 | Upper bound on MODEXP inputs | Closes a resource-exhaustion vector |
| TIP-7883 | MODEXP repricing | Cost now tracks real computation |
| TIP-854 | Standardized calldata for signature precompiles | Fewer cross-chain porting bugs |
| TIP-871 | Standard MODEXP output when modulus is zero | Removes undefined behaviour |
| TIP-833 | Improved resource-window calculation | Affects energy and bandwidth accounting |
TIP-7951 is the one worth pausing on. The secp256r1 curve is what Apple’s Secure Enclave, Android’s Keystore, and WebAuthn passkeys use. Native verification means a TRON smart account can be controlled by a fingerprint or Face ID on a normal phone, with no seed phrase in the flow. Ethereum shipped this in the same cycle; TRON now matches it.
The part most coverage misses: the vote gate
Installing the software does not switch the new semantics on.
The TVM changes are controlled by on-chain governance parameters. Super Representatives have to pass a proposal before the new opcodes and repricings take effect on mainnet. This is why Core Devs Meeting #67 lists “a proposal to enable Prague and Osaka compatibility is under discussion” as a separate item from the release itself.
So the August 16 deadline and the feature activation are two different events. Operators must upgrade to stay in sync. Developers should not write contracts assuming CLZ or the P-256 precompile is live on mainnet until the proposal passes. (It has: Proposal #107 took effect on 28 August 2026.) Test on Nile first.
What changes for ordinary TRON users and USDT senders
Almost nothing, and that is the correct outcome for a consensus-layer release.
A TRC-20 USDT transfer still consumes about 65,000 energy — the figure we break down in how much energy a USDT transfer needs. Energy still costs 100 sun per unit, so an unprepared transfer still burns roughly 6.5 TRX. The MODEXP repricing in TIP-7883 touches cryptographic operations inside contracts, not the standard transfer path, and TIP-833’s resource-window change is an accounting refinement rather than a price change.
The practical advice is unchanged: rent energy rather than burn TRX. High-volume senders can keep using the same approach described in our guides to buying TRON energy in bulk and to the TronSave SDK for buying energy in code, and pricing on the TRON energy market is set by supply and demand, not by node software versions.
The governance proposal has since passed (28 August 2026). If contract costs shift as a result, we will update our fee breakdown with measured numbers rather than estimates.
Other items from Core Devs Meeting #67
Two smaller updates shipped alongside the release. TRON’s Solidity compiler reached v0.8.28, closing more of the gap with mainline Solidity versions that developers expect. And wallet-cli moved to what the team calls an agent-first TypeScript architecture, with both human-readable text and structured JSON output modes — a tool designed to be driven by AI agents as well as people.
This article summarizes official release notes and the public meeting recap. We have not independently benchmarked the new opcodes on mainnet, and the activation proposal had not passed when this article was first written; it took effect on 28 August 2026 as Proposal #107.
FAQ
When is the TRON node upgrade deadline? 23:59 Singapore time on August 16, 2026. Nodes that have not upgraded to GreatVoyage-v4.8.2 risk block synchronization problems after that point.
What breaks if I upgrade without preparing? The two common failures are an event pipeline that stops because the Event Plugin is older than v3.0.0, and a backup routine that depends on the removed RocksDB backup support. Check both before upgrading.
Are the new TVM opcodes live on mainnet now? Yes, since 28 August 2026. The node release shipped the code, and the new semantics were gated behind on-chain governance parameters until Proposal #107 switched Prague and Osaka compatibility on; on 7 November 2026 the chain parameters getAllowTvmPrague and getAllowTvmOsaka both read 1. Test on Nile testnet before deploying contracts that depend on them.
Does this TRON node upgrade change USDT transfer fees? No. A TRC-20 transfer still costs roughly 65,000 energy at 100 sun per unit. The repricing in this release affects MODEXP and other contract-level cryptographic operations, not standard token transfers.
