Exchange Ranking
Top Exchanges
24h Volume Ranking
Popularity Ranking
Exchange BTC Balance
Proof of Reserves
Decentralized Exchanges
Funding Rate
Funding Heatmap
Liquidation Data
Max Pain
Long/Short Ratio
Whale L/S Ratio
Binance/Okex/Huobi L/S
Bitfinex Margin L/S
ETF Tracker
Solana ETF
XRP ETF
Hong Kong ETF
Bitcoin Treasuries
Crypto Reversal
Ethereum Reserves
HyperLiquid Wallet Analysis
Hyperliquid Whale Watch
Large Transactions
On-chain Movement
Bitcoin ROI
Stablecoin Market Cap
Options Analysis
News
Articles
Economic Calendar
Features
Wallet
Contract Calculator
Security
Collections
Watchlist
Following
ETH 
TRX Key Points
Proposition 107 officially came into effect on August 28 after receiving 25 votes for approval, and the wavefield virtual machine enabled Prague and Osaka features.
This adjustment has narrowed the compatibility gap with Ethereum and provided applications with longer historical block hash access.
Native P-256 verification can support password-based wallets, while lower encryption costs are expected to reduce the energy consumption of some applications.
Wavefield Upgrade Details
Proposition 107 received 25 approvals before it took effect on August 28, allowing wavefield virtual machines to access features already included in the GreatVoyage-v4.8.2 release. The proposal document states that the change activates network parameters 95 and 96, enabling Prague and Osaka-related functions for the main network.
For developers, this upgrade enhances support for the behavior of the new version of Ethereum, eliminating the need for a lot of network-specific adjustments when migrating applications to wavefields, thereby reducing the migration workload.
The Prague-related changes also extend access to historical block hashes stored in network state, helping apps confirm historical transactions on-chain, thereby reducing the reliance on external data providers for some verification tasks.
Ethereum passkey support
Osaka related changes introduce native secp256r1 (P-256) signature verification, an encryption curve that is widely used for passkey storage and hardware-supported device key storage. This provides wallet and application developers with a more efficient way to verify signatures generated through built-in security features on phones and computers.
The proposal also reduces the energy consumption of some high-cost cryptographic operations, including MODEXP computing, but the actual savings depend on how each application is built. Developers still need to implement these new features themselves.
Just because the network supports the necessary signature verification, the passkey will not automatically appear in the existing wavefield wallet. The wallet team needs to decide for themselves whether to integrate this feature and determine how users can authenticate using fingerprints, facial recognition, or device PIN codes.
These changes were implemented in GreatVoyage-v4.8.2 before Proposition 107 entered the governance process, but the main network remained disabled until voting was completed. Voting begins on August 25, so activation on August 28 is the final governance step towards enabling these Prague and Osaka features.
