PumpFun Bundler PumpFun Bundler / BundleBee Docs
Telegram Open Terminal
Untraceable funding

Privacy Vault: cut the on-chain trail to your launch.

Route funds through Monero and back so nobody can link your funding wallet to the wallet that launches. SOL goes in, XMR holds it in a private vault, and fresh SOL lands in a clean destination with no chain path between the two.

PumpFun Bundler mascot

On a public chain, anyone can follow the money. If your funding wallet sends SOL straight to the wallet that launches your coin, the two are linked forever, and copycats can trace, mirror or front-run you. The Privacy Vault breaks that link by routing your funds off Solana, through Monero, and back to a brand new Solana wallet.

Why route through Monero

Monero is a privacy chain: its transactions do not expose sender, receiver or amount the way Solana or Ethereum do. Passing value through it severs the public link between the SOL you sent and the SOL that comes out the other side.

The two-leg route

The vault routes your funding through Monero and back, with a self custody Monero wallet holding the value in between, so there is no on chain link between where your money came from and where it lands.

Funding SOL your source wallet leg 1 Monero vault XMR held privately self custody, in the bot fresh subaddress per swap leg 2 Fresh SOL clean destination no on-chain link between source and destination
SOL to XMR into a private vault subaddress, then XMR to SOL to a fresh wallet. The exchange and the Monero hop sit between your source and your destination, so they never touch on chain.
SOL out Monero hop Fresh SOL in

Leg 1: SOL to XMR

The vault issues a fresh Monero subaddress for this swap, so the incoming XMR is attributable to it and nothing else. It opens a SOL to XMR exchange to that subaddress, then sends your SOL from your developer wallet to the exchange's payin address. When the exchange finishes, real XMR has landed in your vault.

The self custody vault

The Monero vault is a real Monero wallet the operator runs (a monero-wallet-rpc daemon), not a third party account. The XMR between the two legs sits in that self hosted vault, and the balance never touches your browser. Nothing is faked: if the vault is not configured, the swap fails with an honest error rather than showing a phantom balance.

Leg 2: XMR to SOL

Once the XMR is in the vault, the machine opens a second exchange, XMR to SOL, pointed at your chosen destination. It then sends the vault's XMR to that exchange's payin address. When leg 2 finishes, fresh SOL arrives at the destination with no on chain path back to where you started. A bounced leg refunds to the vault subaddress it came from.

Pick your destination

The destination can be a brand new auto generated clean wallet, or one of your existing wallets. For maximum unlinkability, send it to a fresh wallet that has never touched your funding source.

A resumable state machine

Bridge legs settle over minutes, not seconds, so the vault is built as a resumable state machine. Each poll advances a swap by at most one step and persists the new state, so a restart never loses a swap in flight, and a failed or expired leg ends cleanly rather than looping.

created leg1_wait leg2_send leg2_wait done SOL sent, poll leg 1 XMR in vault vault XMR sent, poll leg 2 failed
created to leg1_wait to leg2_send to leg2_wait to done. A failed, refunded or expired leg ends in the failed state. Every step is persisted, so the swap resumes after any restart.
StateWhat is happening
createdIssue a fresh vault subaddress, open leg 1, and send your SOL to the leg 1 payin.
leg1_waitPoll leg 1 until the XMR is delivered to the vault.
leg2_sendOpen leg 2 to your destination, and send the vault's XMR to the leg 2 payin.
leg2_waitPoll leg 2 until the fresh SOL lands at the destination.
doneFresh SOL delivered. You are notified.
failedA leg failed, refunded or expired, or the route was not configured. It ends with an honest error.

Optional and operator configured

The Privacy Vault is an optional route, not a default. It only runs when the operator has set it up, with a conversion route and a Monero wallet for the vault. If either is missing, the vault reports that it is not configured rather than pretending to move funds.

It is not instant

Two exchange legs plus a Monero hop take time, typically around 15 to 30 minutes. Start the route before you are ready to launch, not at the last second. Status lands in the app and in Telegram as the legs progress.

The Monero vault card

Convert also exposes the vault directly. You can deposit to and withdraw from the Monero vault, and the deposit and withdrawal handoffs run in the bot, the same private path the bridge uses, so the amount and address stay off your device. The vault card is honest about custody: it says plainly that bridging and custody run in the bot, and shows a not configured state when the Monero wallet is unset.

2
legs: SOL to XMR, then XMR to SOL
1
fresh vault subaddress per swap
15-30m
typical end to end time
0
on-chain link between the two ends

How to run it

  1. Open Convert, Privacy tab

    Go to the Convert screen and pick the Privacy, XMR bridge. Set the amount of SOL to route.

  2. Choose a destination

    Send it to a new auto generated clean wallet, or to one of your existing wallets. Start the private bridge.

  3. Let the legs run

    Leg 1 converts SOL to XMR into the vault. Leg 2 converts the vault XMR to SOL to your destination. Watch the status in the app and Telegram.

  4. Fund your launch from the fresh wallet

    When fresh SOL lands, use that clean wallet to fund your bundle. There is no chain path back to your original source.

Use responsibly and legally

Privacy tooling is for legitimate operational privacy. You are responsible for complying with the laws and regulations that apply to you. PumpFun Bundler is a tool, not legal advice. Read Security before you rely on the vault.