carries resource limits and prioritization in a message-level
V1TransactionConfig instead of Compute Budget program instructions
(which are no-ops inside a v1 transaction),
does not support address lookup tables,
may be up to 4096 bytes when serialized as a transaction (vs. 1232), and
uses a message-first wire envelope when framed as a transaction.
Fetching v1 transactions over RPC requires passing
maxSupportedTransactionVersion: 1 to getTransaction/getBlock.
A v1 transaction message (SIMD-0385).
Compared to v0, a v1 message:
Fetching v1 transactions over RPC requires passing
maxSupportedTransactionVersion: 1togetTransaction/getBlock.