Release Notes
This page lists changes to SupraNova contracts, entry points and routes that affect integrators, relayers and Committee Updaters, newest first. Each entry is dated with the release date of the contract packages it describes.
2026-11-04: EVM contracts v2.1.0-rc.1 and Move packages v1.4.0-rc.0 (Testnet only)
SupraMVM ↔ SupraEVM route
The Testnet release adds a route between SupraMVM and SupraEVM for the Token Bridge and Messaging. The route runs on the Devnet chains of both. supra_hypernova_core on SupraMVM verifies messages from SupraEVM. See Supported Networks.
2026-10-09: Move packages v1.3.0 (Testnet only)
Gloas proof format for messages from Ethereum
The Testnet deployment verifies messages from Sepolia with the proof format that Ethereum’s Gloas upgrade introduces. Relayers submit these messages through new entry points on token_bridge_service:
execute_optimistic_or_safe_v2execute_finality_v2
The underlying verification functions, in the proof_verifier module of hypernova_core, are process_data_optimistic_or_safe_v2 and process_data_finality_v2. On Testnet, the original execute_optimistic_or_safe, execute_finality, process_data_optimistic_or_safe and process_data_finality are disabled and abort with EFUNCTION_DEPRECATED.
The _v2 functions take the same parameters as the originals, with these changes:
- They drop
block_roots_index,receipts_root_proof,receipts_root_gindexandreceipts_root. - They add
execution_block_hash_proof, the proof of the execution block hash. - They add
execution_header_rlp, the execution header that contains the receipts root, in Recursive Length Prefix (RLP) encoding.
Mainnet keeps the existing entry points until Gloas is activated on Ethereum Mainnet. See Ethereum Consensus Verification.
2026-10-06: Move packages v1.2.1
- EIP-7702 transactions.
hypernova_corecan verify transfers and messages sent from Ethereum in EIP-7702 transactions. - Wrapped-token limit on SupraMVM.
token_bridge_servicechecks each send of a wrapped token from SupraMVM against a per-token wrapped-token limit. A transfer that the destination vault would not release is therefore rejected on the source chain.get_wrapped_token_limitontoken_bridge_servicereturns the limit. See Transfer Limits. - Minimum amount.
expected_min_bridge_amountonfee_operatorestimates the smallest amount that covers the fee at current prices.
2026-08-14: EVM contracts v2.0.0 and Move packages v1.2.0
- SupraMVM-native assets to Ethereum. Assets that originate on SupraMVM, such as SUPRA, can be bridged to Ethereum. The new
token_vaultmodule on SupraMVM locks these assets, and the Token Bridge mints their ERC-20 representation on Ethereum. See Token Transfer Models. - Native currency on delivery. A transfer from SupraMVM can ask for the destination chain’s native currency instead of its wrapped form, for example ETH instead of WETH, with
should_unwrap. See Smart Contract Integration. - Zero service fee. The service fee on EVM chains can be configured to zero.
- Hardening. Boneh–Lynn–Shacham (BLS) signature verification in
Hypernovawas hardened, and the EVM contracts gained defence-in-depth checks.