Kraken’s Solana DEX integration shows how centralized apps are absorbing onchain trading

Kraken added onchain token trading to its app on June 18, 2026, starting with Solana. The move matters because it reduces the gap between centralized exchange workflows and wallet-based trading, while raising fresh questions about compliance, support, and execution risk.

Nathan Mercer

Kraken Expands Trading Capabilities by Integrating Solana DEX into Its Core Application, Eyes Further Network Support

Kraken added onchain token trading to its app on June 18, 2026, beginning with Solana. The change matters because it brings wallet-based token access into a familiar exchange interface, which can reduce friction for users who want broader token exposure without moving fully into a standalone DEX workflow. Kraken said the feature is built into the app, and coverage from The Block and Crypto Briefing noted that additional networks are planned. Sources: Kraken blog, The Block, CryptoBriefing.

What changed in Kraken’s app?

The immediate change is functional, not cosmetic. Instead of sending users to a separate decentralized exchange experience, Kraken has embedded onchain token trading inside its core app. That is a practical step for users who already trust the app’s interface but want access to tokens that may live deeper in the Solana ecosystem. Crowdfund Insider also reported the mobile-app angle, reinforcing that this is being positioned as a product-level expansion rather than a one-off market experiment. Source: Crowdfund Insider.

Why does the Solana starting point matter?

Solana is a logical first network because it is already associated with fast settlement and low transaction costs, both of which are important for token trading. That does not make the integration risk-free. Users still need to understand wallet custody, token availability, slippage, and the fact that onchain execution can differ from the order-book experience they get on a centralized venue. Blockchair’s coverage framed the move as a bet on Solana’s long tail, which is the right way to think about it: the value is in access to many smaller tokens, not just the headline network itself. Source: Blockchair.

Who should care about this development?

Three groups should pay attention. Retail traders get a simpler path to onchain markets. Exchanges and brokerages get another example of how the line between CEX and DEX features is narrowing. Payments and treasury teams that move between fiat, crypto, and stablecoins should watch the operational lesson: when trading and conversion become easier, the bottleneck often shifts to settlement, reconciliation, and cash-out planning rather than asset access.

What are the operational trade-offs?

The main trade-off is convenience versus control complexity. A hybrid model can improve onboarding, but it also introduces questions around support boundaries, transaction reversibility, and compliance monitoring across different execution environments. It may be easier for users to trade, but harder for operators to explain where a transaction failed or which rail was responsible. That is why these integrations are strategically important even when they look like a simple feature release.

What should teams do next?

For businesses that rely on crypto conversion or stablecoin movement, the practical next step is to map where users or counterparties are still forced to jump between venues. If your workflow includes moving from fiat into crypto, or from crypto back to fiat, the real value is in reducing avoidable handoffs and improving visibility at each step. That is the kind of problem Radom’s crypto convert flow is designed to address, especially where operational teams care more about speed and settlement clarity than speculative trading features.

FAQ: Is this a replacement for a DEX wallet workflow?

No. It lowers the barrier to accessing onchain tokens, but it does not remove the underlying differences between centralized app trading and direct wallet-based execution. Users still need to evaluate custody, fees, token liquidity, and support expectations before treating the two as equivalent.

Sources

Exploring how this affects your operating model?

Sign up to Radom to get started