Sonic V2.2 adds bundles, sponsorship, and larger contracts
Sonic Labs detailed the upcoming V2.2 network upgrade in a thread laying out how its pieces fit together around coordinated execution, flexible gas sponsorship, and greater smart contract capacity. The upgrade is rolling out, per an earlier progress update.
- Native bundles let multi-step actions succeed or roll back as one atomic unit, with no unrelated activity inserted between steps. Compatible flows also allow single-signature execution through a temporary delegate account; standard bundles still require separate signatures.
- Expanded sponsorship: network-sponsored transactions let qualifying activity run without acquiring the S token, and successful-only sponsorship means completed transactions draw from the budget while failed ones do not.
- Contract limits double: deployed contract code rises from 24 KiB to 48 KiB and initialization code from 48 KiB to 96 KiB, supported by the Simple Format Virtual Machine (SFVM) so existing contracts need no rewrite.
For developers this means more control over execution, payment, and logic; for users, fewer signing prompts, easier onboarding, and more reliable multi-step actions.
Sources
- Together, these changes give developers more control over how applications execute, who pays for them, and how much logic they can support. For users, that opens the door to fewer signing prompts, easier onboarding, and more reliable multi-step actions. Replying to their earlier post: Builders gain more room for application logic. V2.2 doubles deployed contract limits from 24 to 48 KiB and initialization code limits from 48 to 96 KiB, reducing the need to split contracts solely to…x.com ↗
- Builders gain more room for application logic. V2.2 doubles deployed contract limits from 24 to 48 KiB and initialization code limits from 48 to 96 KiB, reducing the need to split contracts solely to fit. Read "Doubling the Limit": https://t.co/FcaUbi01UT Replying to their earlier post: Applications also gain successful-only sponsorship: completed transactions use the sponsorship budget, failed attempts do not. Combined with bundles, apps can cover gas for coordinated workflows whil…x.com ↗
- Applications also gain successful-only sponsorship: completed transactions use the sponsorship budget, failed attempts do not. Combined with bundles, apps can cover gas for coordinated workflows while avoiding partially completed operations. Replying to their earlier post: Completing an action should not always require acquiring $S first. V2.2 expands sponsorship with network-sponsored transactions, allowing qualifying activity to execute without any token payment. Re…x.com ↗
- Completing an action should not always require acquiring $S first. V2.2 expands sponsorship with network-sponsored transactions, allowing qualifying activity to execute without any token payment. Read "Sponsored By Design": https://t.co/IhyLPTGODr Replying to their earlier post: Bundles also enable single-signature workflows through a temporary delegate account. For compatible flows, users sign once, the delegate executes the steps, and assets return in one atomic bundle. St…x.com ↗
- Bundles also enable single-signature workflows through a temporary delegate account. For compatible flows, users sign once, the delegate executes the steps, and assets return in one atomic bundle. Standard bundles still require separate signatures. Read "Why Sign Twice?": https://t.co/lVbnwE9BXk Replying to their earlier post: One action can require several transactions. V2.2 introduces native bundles that can make those transactions succeed or roll back together, with no unrelated activity inserted between steps. Read "B…x.com ↗
- One action can require several transactions. V2.2 introduces native bundles that can make those transactions succeed or roll back together, with no unrelated activity inserted between steps. Read "Bundled By Default": https://t.co/uuWsiifgd9 Replying to their earlier post: Sonic V2.2 is coming soon. The upgrade brings coordinated execution, more flexible gas sponsorship, and greater capacity for smart contracts. Here’s how these changes fit together, drawing on our re…x.com ↗
- Sonic V2.2 is coming soon. The upgrade brings coordinated execution, more flexible gas sponsorship, and greater capacity for smart contracts. Here’s how these changes fit together, drawing on our recent articles.x.com ↗
- V2.2 loading... 0% █████████▒ 100%x.com ↗
- Existing contracts do not need to be rewritten, and users continue interacting with applications as usual. For builders, V2.2 means more freedom to choose the right architecture and less restructuring simply to fit a size limit. More room for what comes next. Replying to their earlier post: Supporting these limits required a change to Sonic’s execution engine. V2.2 introduces the Simple Format Virtual Machine (SFVM), which keeps original contract instructions and uses a compact map of v…x.com ↗
- Supporting these limits required a change to Sonic’s execution engine. V2.2 introduces the Simple Format Virtual Machine (SFVM), which keeps original contract instructions and uses a compact map of valid jump destinations, removing the previous size restriction. Replying to their earlier post: The upgrade doubles both limits: - Deployed contract code: 24 KiB → 48 KiB - Initialization code: 48 KiB → 96 KiB Initialization code runs during deployment to configure a contract before its final…x.com ↗
- The upgrade doubles both limits: - Deployed contract code: 24 KiB → 48 KiB - Initialization code: 48 KiB → 96 KiB Initialization code runs during deployment to configure a contract before its final code is stored onchain. Replying to their earlier post: As applications grow, their contracts can reach the size limit. Developers then have to reduce code, remove features, or split the application across multiple contracts, sometimes adding complexity s…x.com ↗
- As applications grow, their contracts can reach the size limit. Developers then have to reduce code, remove features, or split the application across multiple contracts, sometimes adding complexity solely to fit within the limit. V2.2 gives them more flexibility. Replying to their earlier post: Sonic V2.2 doubles smart contract size limits, giving developers more capacity for application logic and features. Here’s what changes and why it matters for builders.x.com ↗
- Sonic V2.2 doubles smart contract size limits, giving developers more capacity for application logic and features. Here’s what changes and why it matters for builders.x.com ↗
