Sonic is preparing its V2.2 upgrade with a focus that goes beyond transaction speed. The upcoming release is designed to make complex onchain actions easier to execute by introducing native transaction bundles, expanded gas sponsorship and greater capacity for smart contracts.
The changes target some of the less visible problems users face in DeFi. Approving a token, depositing it and completing another action can require several separate transactions, while new users may hold assets but lack S tokens to pay network fees. Sonic V2.2 is designed to address both problems at the protocol level.
Sonic V2.2 Makes Multi-Step Transactions Atomic
One of the central additions is native transaction bundling. Instead of treating every transaction in a multi-step action independently, Sonic can group related transactions into an execution plan where the steps succeed or fail together. This reduces the risk of users being left with a partially completed operation.
Consider a basic DeFi interaction that requires an approval followed by a swap. Under a conventional setup, the two operations can be separate transactions, creating additional signing steps and potential points of failure. Bundles allow applications to coordinate the sequence so the entire workflow has a shared outcome.
Sonic also says bundles prevent unrelated activity from being inserted between the steps. That matters for applications that depend on a specific sequence of actions, particularly when several transactions must interact with the same assets or contracts.
The upgrade also introduces a delegate-based option for compatible workflows. A temporary delegate account can execute multiple steps after a user provides a single signature, with the transactions wrapped into an atomic bundle. Standard bundles still require the relevant signatures, so the single-signature experience is not universal.
This design could make more complicated applications feel closer to conventional software. Users generally care about completing an action, not managing every individual blockchain transaction required to make it happen. Sonic’s approach moves some of that complexity into the protocol and application layer.
Gas Sponsorship Gives Applications More Control
V2.2 also expands Sonic’s transaction sponsorship system. Applications can cover network fees for qualifying user activity, while a new network-sponsored mode can allow selected transactions to execute without consuming the user’s S tokens.
That addresses a familiar onboarding problem. A user may bridge USDC, ETH or another asset onto Sonic but still be unable to interact with an application because the wallet does not contain S for gas. With sponsorship, applications can remove that initial barrier.
The system is also designed to give developers more control over their budgets. Sponsorship can be restricted to particular contracts, functions, accounts or specific onboarding actions. Sonic’s successful-only sponsorship feature goes further by charging the sponsorship budget only when a transaction actually succeeds.
This creates an interesting combination with transaction bundles. An application could sponsor an approval, deposit and subsequent action while bundling those operations into one coordinated workflow. The user would not need to acquire S first, while the application could control exactly which activities it is willing to subsidize.
V2.2 is also increasing Sonic’s smart-contract size limits. Deployed contract code will rise from 24 KiB to 48 KiB, while initialization code will increase from 48 KiB to 96 KiB. The change gives developers more room for complex applications without forcing them to split functionality across multiple contracts simply to stay within the previous limits.
The significance of Sonic V2.2 therefore is not one individual feature. Bundles address fragmented execution, sponsorship addresses gas friction and larger contract limits address development constraints. Together, they are aimed at making the underlying network less visible during everyday application use.
The real test will come after deployment and adoption. Developers still need to integrate the new capabilities, while users need applications that make meaningful use of them. If that happens, Sonic V2.2 could shift the network’s competitive argument from simply processing transactions quickly to making onchain applications easier to use and build.
About The Author
