
Jupiter's v7.1.5 release adds ZIG/ZAG, Sanctum and QuantumV2 pool integrations and lets Jupiter Lend jlX tokens route through any eligible pool, alongside routing and RPC leak fixes.
In brief
- Jupiter released v7.1.5 on 10 November with new AMM integrations and Jupiter Lend routing changes.
- The update caps routing constraints and stops RPC URLs leaking into error responses and logs.
- Jupiter
JUP traded near $0.253 at 15:35 UTC, up +1.71% in 24 hours.
What happened
Jupiter, a Solana decentralized exchange (DEX) aggregator, published version v7.1.5 of its routing software on GitHub on 10 November.
The release adds new automated market maker (AMM) integrations, including the Fantastical Finance Factory pools for the ZIG/ZAG faction and the ZIG/ZAG to MOTION vault.
It also adds Sanctum Infinity Reserve V2, QuantumV2 with Token-2022 support and BisonFi SDK 0.4.0.
Jupiter Lend gets a routing change: jlX tokens can now route through any eligible pool, not only the Jupiter Lend pool.
ZeroFi and Scorch PropAMMs are whitelisted for API users, and Obsidian is excluded.
Why it matters
The release also closes several robustness holes.
Requests with a maxhop above 5 or a bucketSizePercentage outside 1-100 are now rejected; previously one request could abort the process and a few could tie up every quote worker.
Undecodable account data, a missing OpenBook V2 oracle and a transfer-hook platform fee now return errors instead of failing later on-chain.
The router keeps the RPC URL, and any token in it, out of error responses and logs.
Memory work is included too: jemalloc replaces snmalloc, with steady memory at 8.2 GiB in Jupiter's benchmark, down from 10.9 GiB.
What to watch
An experimental RouteByPrice partition algorithm is opt-in through routingConstraints.partitionAlgo, and the default is unchanged.
BisonFi market-backed pools now pass the market tick account, which BisonFi will require on every swap.
Jupiter
JUP traded near $0.25275 at 15:35 UTC, up +1.71% in 24 hours, according to Hyperliquid data.