The protocol's maximum — and legacy/v0 implicit default — loaded-accounts
data-size limit: 64 MiB. Not exported by @solana/kit.
Version 1 carries this limit in its header config, and SIMD-0385 treats an
absent field as a request for 0 bytes; account loading counts a 64-byte base
cost per account, so a 0-byte budget fails every transaction. The SDK
therefore always writes a v1 value, using this maximum when the caller does
not request less — the same budget legacy and v0 receive implicitly.
The protocol's maximum — and legacy/v0 implicit default — loaded-accounts data-size limit: 64 MiB. Not exported by
@solana/kit.Version 1 carries this limit in its header config, and SIMD-0385 treats an absent field as a request for 0 bytes; account loading counts a 64-byte base cost per account, so a 0-byte budget fails every transaction. The SDK therefore always writes a v1 value, using this maximum when the caller does not request less — the same budget legacy and v0 receive implicitly.