Solana Agave 4.4 Targets sBPFv3 as Deeper CPI Upgrade Awaits Activation
Solana lists Agave 4.4 for November with an sBPFv3 deployment requirement, while the CPI depth increase from four to eight awaits a later activation.
Solana's official network-upgrade tracker lists Agave 4.4 as planned for November 2026 and still in development. The release centers on a new minimum program format for deployments, while a related increase in cross-program call depth is scheduled to follow after the release.
The status matters for developers and infrastructure providers because neither change should be treated as active on mainnet yet. The official feature pages show the relevant gates as not activated on testnet, devnet or mainnet at the time of writing.
sBPFv3 becomes the deployment target
The sBPFv3 change is designed to make version 3 the only format accepted for new program deployments, upgrades and finalizations once its feature gate activates. Programs that are already onchain will continue to run, including programs built with older sBPF versions.
Developers using supported toolchains can rebuild for sBPFv3 before activation. Solana's documentation says the change is mostly a build-tool update, but a program compiled for sBPFv0, v1 or v2 would no longer be accepted for a new deployment or upgrade after the restriction takes effect.
The technical rationale includes static syscall linking, stricter executable headers and closer compatibility with the eBPF v3 instruction set. Validators currently support four program formats. Restricting future deployments to one format is intended to reduce the long-term runtime burden, while preserving compatibility for code that is already deployed.
The official page lists Agave 4.4 in November 2026 as the expected mainnet activation window for sBPFv3, but it does not provide a final date. Developers should therefore follow release notes and feature-gate status rather than assume activation from the calendar alone.
Deeper program calls come later
A separate proposal raises the maximum number of nested cross-program invocations, or CPIs, from four to eight. The total instruction stack height would rise from five to nine because the top-level instruction occupies the first level.
Deeper CPI chains can support more modular transactions, such as a wallet calling an application, which calls a router, which then calls multiple liquidity programs. The change applies to legacy, v0 and v1 transactions and does not alter Solana's existing reentrancy rule.
The detailed Solana page says the CPI feature is expected after Agave 4.4, with the activation date still to be determined. It is already available for local testing because solana-test-validator enables known feature gates by default, but that does not mean the limit is live on public clusters.
Indexers, simulators and developer tools that hardcode the existing stack-depth constant may need updates. Wallet simulation also needs to display the full inner-instruction tree so that users can inspect all calls in a deeper transaction.
For separate information about platform safeguards, see the OrangeX.com Trust Center and Proof of Reserves information. These resources concern OrangeX.com and do not document the Solana upgrade. Additional project coverage is available in the OrangeX.com News archive.
OrangeX.com Analysis
Agave 4.4 is a developer-facing transition rather than a consumer token event. The sBPFv3 requirement narrows the accepted format for future deployments without forcing existing onchain programs to migrate immediately. That reduces disruption, but teams that expect to upgrade their programs still need to rebuild and test before the feature gate activates.
The CPI expansion could improve composability, yet its separate activation schedule is important. Treating both items as live with the Agave 4.4 release would overstate the current status. The practical milestones to watch are an Agave 4.4 release, an announced sBPFv3 gate activation and a later, independently confirmed CPI-depth activation.
Related Reports
Whitechain Migrates From Layer 1 to an OP Stack Layer 2
Whitechain moved its live network to the OP Stack while keeping chain ID 1875, balances, contracts and addresses unchanged.
Frame V3 Testnet Adds Post-Quantum Signing and Cross-Chain Swaps
Frame said its V3 private testnet has processed more than 13 million transactions and added native cross-chain swaps.
Injective Votes on Expedited Safeharbor Upgrade After Emergency Patch
Injective proposal 714 asks validators to adopt v1.20.4-safeharbor.5 at an expedited halt after the network's November 9 emergency patch.
