Pump.fun-linked address deposits $148M in USDC and USDT to Kraken

The transfer brings the total amount sent to Kraken since Nov. 15 to approximately $753 million in stablecoins. All of the funds are traced back to proceeds from the PUMP initial coin offering, based on publicly visible wallet activity.

Similar movements have occurred at regular intervals since late 2025, often involving nine-figure sums. In some cases, stablecoins deposited to Kraken were later observed moving toward Circle-related addresses, suggesting possible redemptions or internal treasury operations.

Neither Pump.fun nor Kraken has publicly commented on the purpose of the latest transfer. The scale and consistency of these deposits have drawn attention across crypto markets, especially given Pump.fun’s central role in Solana’s memecoin economy.

Treasury management, pressure points, and open questions

Pump.fun has previously pushed back against claims that such transfers represent cash-outs or liquidation activity. Team members have described past movements as routine treasury management, including diversification, operational spending, and preparation for reinvestment.

Still, the timing has fueled debate. The most recent transfer comes amid increased scrutiny of the platform, which includes complaints about its previous creator fee structure and slower revenue growth when compared to periods of peak memecoin trading. 

Alon Cohen, a co-founder, acknowledged the flaws in the previous fee model earlier this month. He presented a new strategy that would shift incentives away from volume-driven token launches and toward traders and liquidity.

At the same time, the company continues to face legal scrutiny. A court decision is expected later this month in an amended civil lawsuit accusing Pump.fun of racketeering and insider trading. While the recent transfer is not directly tied to the case, it has raised fresh questions around transparency and governance.

As with past transfers, the market reaction has been cautious rather than abrupt. Observers remain watchful, waiting to see whether there are additional movements or a formal response from the team.