Maximum transaction version the caller can handle, for version-aware read
APIs (transactionSubscribe, getTransactionsForAddress).
Helius recommends setting 1 (Agave 4.2 migration checklist) to also
receive version 1 transactions (SIMD-0385) — opting in means your handlers
must accept the v1 payload shape. The field only takes effect when
transactionDetails is "accounts" or "full": there, an omitted field
means legacy-only on HTTP methods, and a higher-version transaction in range
errors rather than being filtered out, while transactionSubscribe requires
the field outright.
Owned by the SDK rather than derived from kit's TransactionVersion: the
ceiling tracks what Helius endpoints accept, and widens by SDK release.
Maximum transaction version the caller can handle, for version-aware read APIs (
transactionSubscribe,getTransactionsForAddress).Helius recommends setting
1(Agave 4.2 migration checklist) to also receive version 1 transactions (SIMD-0385) — opting in means your handlers must accept the v1 payload shape. The field only takes effect whentransactionDetailsis"accounts"or"full": there, an omitted field means legacy-only on HTTP methods, and a higher-version transaction in range errors rather than being filtered out, whiletransactionSubscriberequires the field outright.Owned by the SDK rather than derived from kit's
TransactionVersion: the ceiling tracks what Helius endpoints accept, and widens by SDK release.