
Helium's blockchain API 0.21.0 bounds Jupiter /build routes so a swap fits in one transaction, and adds a TRANSACTION_TOO_LARGE error when it cannot.
In brief
- Helium's blockchain API 0.21.0 bounds Jupiter swap routes to 40 accounts and 1,080 bytes.
- Swaps that still do not fit are refused with a new TRANSACTION_TOO_LARGE error (422).
- Three getInstructions inputs are now marked deprecated and callers that send them are logged.
What happened
Helium released version 0.21.0 of its blockchain API on 22 November, according to the release notes.
The package is the interface developers use to build instructions for Helium
HNT programs on Solana.
The update limits Jupiter swap routes built through the /build endpoint to a maximum of 40 accounts and 1,080 bytes.
That keeps a swap inside a single transaction, with 100 bytes left for wallet guard instructions.
If a route is still too large, the API rebuilds it once with the byte limit lowered by the exact overshoot.
When that also fails, or Jupiter finds no route within the lower bound, getInstructions returns a new TRANSACTION_TOO_LARGE error with status 422.
The release says the aim is to stop returning a transaction that cannot be sent.
Governance batches keep the same 100-byte reserve for wallet guards.
Why it matters
The change is narrow and aimed at builders rather than traders.
A swap that used to come back as an unsendable transaction now fails with a clear error, which is easier to handle in code.
The release also marks three getInstructions inputs as deprecated: dynamicComputeUnitLimit, useSharedAccounts and prioritizationFeeLamports.
The API now logs the user agent of callers that still send them. dynamicComputeUnitLimit no longer defaults to true, so it is undefined unless set, and the release notes say nothing reads it.
This follows the earlier change that routed Helium swaps through Jupiter's V2 build endpoint.
What to watch
Developers integrating Helium swaps should check whether their routes exceed the new bounds and handle the 422 error.
Callers still sending the deprecated inputs will appear in the API's logs.