Release v2.2

Sonic release v2.2 adds Gas Subsidies and Bundled Transactions, alongside a larger contract size limit, adopted Ethereum Osaka features, and a set of network performance improvements.

For instructions on upgrading your node to this release, see Upgrade Instructions (v2.2).

New for applications

Gas Subsidies

Projects can cover gas fees for their users. Users don't need to hold any native S tokens. A sponsor deposits funds, and matching transactions get their fee deducted from that fund instead of the sender's balance. Matching is fine-grained, from a single account-plus-nonce pair up to whole-contract or whole-account sponsorship, so a sponsor can target exactly the transactions they intend to cover.

Full docs →

Bundled Transactions

Multiple transactions can be sent as one unit with a guarantee about how they succeed or fail together. Either all of them go through, or the group is rolled back, with no risk of other traffic being interleaved in between.

Full docs →

Extended contract code size

The per-contract code size limit doubles from 24 KiB to 48 KiB, and the init code limit (constructor / contract-creation code) doubles alongside it, from 48 KiB to 96 KiB. Applications can fit more functionality into a single contract, before needing to split anything up.

Osaka Features

Release v2.2 also brings in features from Ethereum's Osaka upgrade:

• Higher per-transaction gas cap (EIP-7825). Raises the maximum gas a single transaction can consume.

• secp256r1 curve support (EIP-7951). Adds a native precompile for this curve, enabling device-native and passkey-style signing.

• Updated MODEXP precompile (EIP-7823, EIP-7883). Caps the size of MODEXP inputs and raises the precompile's gas cost, closing a gap where large modular-exponentiation calls were underpriced relative to their real cost.

Network and validator improvements

• New eth_config RPC method. Lets node operators and tooling query which hard forks are currently active and which are scheduled next, directly from the node.

• Faster consensus processing. Improvements to consensus cache management speed up how nodes analyze consensus messages.

• Faster synchronization. Optimized handling of the consensus events ordering buffer keeps nodes tracking the chain head more reliably under certain traffic patterns.

• Optimized log filtering. Significant performance improvements to eth_getLogs queries.