Solana V1 transactions hit testnet, aiming to fold multi-step operations into one

On September 1, Anza initiated Transaction V1 on the testnet of Solana, allowing for the final rehearsal of this upgrade prior to its launch on September 9. The change is intended to allow cryptographic and DeFi workloads that had initially to be fragmented in different transactions to now be processed in one single atomic transaction, as stated by Solana Compass. Jobs that used to be split now fit in one call The most notable alteration is the increase in space. The maximum size of a Solana serialized transaction has increased from 1,232 bytes to 4,096 bytes which is an increase of 3.3 times and took effect at the testnet epoch 1025. According to the website dedicated to Solana Foundation’s large transaction update, such large transaction size will make it possible to implement zero-knowledge proofs, large multisig transactions along with various signature schemes which were unachievable within one transaction. In turn, fewer transactions have to be processed, less money is required to pay for signatures, and there is no need to wait for a chain of confirmations. BLS signature schemes, as well as confidential transactions and multisig setups will benefit from this upgrade. There are two main proposals that are essential for the improvement. SIMD-0296 increases the transaction size from 1,232 bytes to 4,096 bytes, while SIMD-0385 defines the V1 message format and moves transaction configuration into the message itself. Less than a day after the upgrade was activated Anza CEO Brennan Watt made a post on X mentioning a large transaction on the testnet explorer with the message: “ATTENTION: large transactions have hit the testnet.” Why one transaction beats a bundle The importance of atomicity comes from the fact that at times, developers bypassed Solana’s old size limit with Jito bundles. In fact, SIMD-0296 explains that workaround and also mentions that bundles lack atomicity at protocol level as in the case with one native transaction. According to Jito’s documentation, bundles can include up to five transactions processed sequentially on an all-or-nothing basis. But bundles operate within Jito’s block-engine and compete among validator tips. V1 transaction, on the other hand, refers to a single native Solana transaction, which carries the transaction-level atomicity guarantee from Solana. For DeFi developers, this can help simplify helping in establishing swap routes, proofs, and other kinds of multistep transactions. If the operation is entirely covered by V1 transaction, it either succeeds or returns it back as a single-native transaction instead of relying on a bundle of transactions. What DeFi gets beyond extra bytes V1 modifies the transaction structure as well.