Solana Expands Per-Transaction Data Limit More Than Threefold, Boosting Support for Complex Transactions and Privacy Features

Solana has increased the amount of data that can be included in a single transaction by more than threefold, strengthening the foundation for complex transactions, multisignature functions and privacy applications.

CoinDesk reported on September 15 that the Solana Foundation implemented its new "Transaction V1" format starting at 1 a.m. UTC that day. The change increases the maximum size of a single transaction to 4,096 bytes from 1,232 bytes, or about 3.3 times.

Transaction data includes instructions, signatures and other information needed to execute a transaction. The upgrade does not aim to increase the number of transactions Solana can process per second. Instead, it is focused on expanding the amount of information each individual transaction can contain.

Under the previous 1,232-byte limit, complex tasks often had to be split across multiple transactions. That had constrained the development of enterprise wallets requiring approval from multiple parties, as well as applications based on zero-knowledge proofs, or ZK Proofs, which verify information without directly revealing it.

The larger data limit also makes it easier to combine multiple steps into a single transaction. If part of a transaction fails, the entire transaction can be rolled back, which can improve execution stability compared with the previous approach of linking multiple transactions separately.

Services that provide blockchain data to wallets, trading applications and analytics platforms, however, need to update their systems to recognize the new V1 transaction format. Without V1 support, errors may occur not only when handling those transactions but also when loading blocks that include them.

The legacy transaction format will remain supported. Even applications that continue sending transactions in the older format, however, still need updates to read the new V1 transaction data.