Jupiter adds native INJ routing across Solana DEXes with MEV protection and auto-slippage

Jupiter has added routing for native INJ across Solana decentralized exchanges, with execution that includes auto-slippage adjustment and MEV protection, according to reporting and analyst commentary on the integration. The setup is described as working through Jupiter’s routing layer across venues such as Raydium, Orca and Meteora, rather than relying on wrapped tokens.

The integration is tied to Sunrise bridge plumbing, which mints INJ as an SPL token on Solana so it can be traded like other assets on the network. In practical terms, that means users can route swaps for INJ through Jupiter while the asset remains native to the Solana environment, rather than being presented as a wrapped derivative.

How the swap path is being handled

One of the main changes is execution routing. Jupiter’s aggregator is described as scanning Solana DEX liquidity to find the best available path for INJ swaps, with Raydium, Orca and Meteora among the venues named in the coverage. The same reporting says Jupiter’s Ultra mode adds auto-slippage, which adjusts tolerance based on market conditions, and MEV protection designed to reduce sandwich attack exposure.

The result is a more integrated trading path for users who want native INJ access on Solana, with routing and execution features handled inside Jupiter’s interface. The coverage also frames the change as a structural liquidity improvement, since the asset can move through existing Solana liquidity venues without requiring a wrapped-token workflow.

Native asset access, not a wrapped workaround

The distinction between native INJ on Solana and a wrapped version is central to the update. The reporting says Sunrise bridge handles the cross-chain transfer process and makes INJ available as an SPL token, which allows it to behave like other Solana assets. That setup lets traders hold, route and swap INJ inside the Solana ecosystem using the same market structure used for other SPL tokens.

No official Jupiter announcement was included in the source material reviewed for this report, so the development is being attributed to the external reporting and analyst description of the routing change. The available information is still specific enough to identify the core shift: Jupiter is now described as supporting native INJ routing across Solana DEXes with execution protections layered in through Ultra mode.