Don't want to trade it yourself?
Our desk runs DEX portfolios on profit share.
TRON(TRX) activated Proposal 107 on Aug. 28, adding Ethereum(ETH) Prague and Osaka features plus passkey-friendly signature verification to its virtual machine.
Key Points:
- Proposal 107 took effect on Aug. 28 after receiving 25 approvals, activating Prague and Osaka features in the TRON Virtual Machine.
- The changes narrow compatibility gaps with Ethereum and add longer historical block-hash access for applications.
- Native P-256 verification can support passkey-based wallets, while lower cryptographic costs may reduce energy use for some applications.
TRON Upgrade Details
Proposal 107 received 25 approvals before taking effect on Aug. 28, giving the TRON Virtual Machine access to features already included in the GreatVoyage-v4.8.2 release. The proposal documentation on GitHub says the change activates network parameters 95 and 96, which switch on Prague- and Osaka-related functionality for the mainnet.
For developers, the upgrade expands support for newer Ethereum behavior without requiring as many network-specific adjustments when moving applications to TRON. That reduces one layer of migration work.
The Prague-related changes also extend access to historical block hashes stored in network state, which can help applications confirm older transactions on-chain. This can reduce reliance on outside data providers for some verification tasks.
Ethereum Passkey Support
The Osaka-related changes add native secp256r1, or P-256, signature verification, a cryptographic curve widely used for passkeys and hardware-backed device key stores. This gives wallet and application developers a more efficient way to verify signatures created through security features built into phones and computers.
The proposal also lowers the energy cost of some expensive cryptographic operations, including MODEXP calculations, although actual savings will depend on how individual applications are built. Developers still need to implement the new capabilities.
Passkeys will not automatically appear in existing TRON wallets simply because the network now supports the necessary signature verification.
Wallet teams must choose whether to integrate the feature and decide how users will authenticate through fingerprints, facial recognition or device PINs.
The changes were already implemented in GreatVoyage-v4.8.2 before Proposal 107 reached governance, but they remained disabled on mainnet until voting was completed. The vote began on Aug. 25, making the Aug. 28 activation the final governance step for enabling those Prague and Osaka features.
Read Next:XRP Sees Over $335M Binance Whale Exit While Futures Selling Builds
Source: yellow.com