SIMD-0385 treats an absent v1 header-config field as 0, so on version 1
the returned message pre-sets the loaded-accounts-data-size limit to the
64 MiB maximum (MAX_LOADED_ACCOUNTS_DATA_SIZE_BYTES) — a 0-byte budget
fails account loading while still paying fees. Override it with kit's
setTransactionMessageLoadedAccountsDataSizeLimit. The compute-unit limit
and priority fee are NOT pre-set (they need simulation): set them with
setTransactionMessageComputeUnitLimit and
setTransactionMessagePriorityFeeLamports before sending, or build via
createSmartTransaction. ComputeBudgetProgram ixs do not configure v1;
they execute as paid no-ops.
The return type is stated explicitly rather than inferred. Kit does not
export V1TransactionConfig, so an inferred type that structurally includes
it cannot be named in the emitted declarations (TS2742).
SIMD-0385 treats an absent v1 header-config field as 0, so on version
1the returned message pre-sets the loaded-accounts-data-size limit to the 64 MiB maximum (MAX_LOADED_ACCOUNTS_DATA_SIZE_BYTES) — a 0-byte budget fails account loading while still paying fees. Override it with kit'ssetTransactionMessageLoadedAccountsDataSizeLimit. The compute-unit limit and priority fee are NOT pre-set (they need simulation): set them withsetTransactionMessageComputeUnitLimitandsetTransactionMessagePriorityFeeLamportsbefore sending, or build viacreateSmartTransaction.ComputeBudgetProgramixs do not configure v1; they execute as paid no-ops.The return type is stated explicitly rather than inferred. Kit does not export
V1TransactionConfig, so an inferred type that structurally includes it cannot be named in the emitted declarations (TS2742).