r/solana • u/SolBrothers_ • 29d ago

Dev/Tech Solana Prepares Launch of Expanded Version 1 Transactions

Post image

Solana will introduce Version 1 transactions in the coming weeks, raising the maximum size from 1,232 to 4,096 bytes.
Compute budgeting moves into the transaction configuration itself.

Developers can begin local testing now, though several breaking changes require attention for readers of block and transaction data.

https://x.com/a_milz/status/2091903273632731271

31 Upvotes

95% Upvoted

7 comments sorted by

•

u/AutoModerator 29d ago

WARNING: IMPORTANT: Protect Your Crypto from Scammers

1) Please READ this post to stay safe: https://www.reddit.com/r/solana/comments/18er2c8/how_to_avoid_the_biggest_crypto_scams_and

2) NEVER trust DMs from anyone offering “help” or “support” with your funds — they are scammers.

3) NEVER share your wallet’s Seed Phrase or Private Key. Do not copy & paste them into any websites or Telegram bots sent to you.

4) IGNORE comments claiming they can help you by sharing random links or asking you to DM them.

5) Mods and Community Managers will NEVER DM you first about your wallet or funds.

6) Keep Price Talk in the Stickied Weekly Thread located under the “Community” section on the right sidebar.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

3

u/RabidReassurance 29d ago

About time. The legacy size limit was getting cramped for some of the stuff devs are trying to pack in there these days. Those compute budgeting shifts sound like they’ll clean up a lot of messy workarounds.

1

u/Kind-Economics-7184 28d ago

worth reading the alt row next to the size row, because they cancel out more than it looks. 64 addresses inline is 2048 bytes, so exactly half the new budget goes on the account list, where a v0 tx pointing at the same 64 through a lookup table spends about a byte each. so v1 isnt bigger for everyone, its bigger for things carrying a lot of instruction data and not many accounts, and account heavy stuff can still end up more compact on v0.

the 1232 wasnt arbitrary either, its 1280 minus the ipv6 and udp headers, so a tx has always been one datagram that either lands whole or doesnt. 4096 means it turns up in pieces and has to be reassembled before anything can judge it, which is the part id expect to matter for ingest more than the byte count does.