Helium API 0.21.0 caps Jupiter swap routes to one transaction

Helium API 0.21.0 caps Jupiter swap routes to one transaction

Emily Wong23 Nov 202626 min ago1 min read

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.

Sources

  1. Helium - Helium blockchain API 0.21.0 release notesAnnouncement

Related articles

More in Ecosystem

Nothing on BACOOR NEWS is financial advice.

BACOOR NEWS is developed by BACOOR's Japan team and provides news, editorial content, and market data for informational purposes only. Nothing published constitutes financial or investment advice, or an offer, solicitation, or recommendation to buy, sell, or hold any financial product or digital asset. Coverage of any token, trading pair, company, protocol, or project does not imply endorsement or promotion. Digital asset markets involve significant risks. Always conduct your own research (DYOR) and review our Disclaimer before making investment decisions.

AI Content Transparency: Market Pulse summaries are automatically generated using artificial intelligence (AI) based on third-party information and market data. News articles and other editorial content may also be drafted, edited, or otherwise prepared with AI assistance. BACOOR does not independently verify all third-party information before publication. AI-generated or AI-assisted content may contain errors, omissions, or outdated information. Readers are encouraged to verify important claims against the original sources. BACOOR may correct, update, or remove inaccurate content when identified.

Product Promotions: BACOOR NEWS may display clearly identified promotional content about BACOOR's own products and services where permitted by applicable law. Crypto-related promotional banners are not displayed on the Vietnamese-language edition or to visitors in Vietnam. Such promotional material is separate from editorial news and market data.

Data and Information Sources: alternative.me, Bankless, Arkham, Binance, Bitget, Bybit, Coinbase, Coin Bureau, DefiLlama, DEX Screener, ExchangeRate-API, Farside Investors, U.S. Bureau of Labor Statistics, U.S. Bureau of Economic Analysis, Federal Reserve, Bank of Japan, Cabinet Office of Japan, Gate, Hyperliquid, Lookonchain, MEXC, OKX, PatternPlus, Forex Factory, SEC EDGAR, Solid Intel, SoSoValue, Trust Wallet assets, Wikidata, CoinGecko, GeckoTerminal, e-Stat, FRED (Federal Reserve Bank of St. Louis), Japan Customs (Ministry of Finance), Wikimedia Commons, the official blogs and GitHub releases of the projects we cover, and Watcher Guru. External information may be delayed, inaccurate, or incomplete. Source attribution does not imply affiliation or endorsement.

This service uses the API function of e-Stat (Portal Site of Official Statistics of Japan), but its content is not guaranteed by the Japanese government.

Build version: ebe3359 · 2026-11-23 06:09 GMT+7