> For the complete documentation index, see [llms.txt](https://mixfun.gitbook.io/mixfun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mixfun.gitbook.io/mixfun/guides/use-the-relayer.md). # Use the relayer > Withdraw into a wallet with zero SOL for gas by routing the transaction through MixFun's relayer. The relayer is an optional service for Private Send and Shielded Pools withdrawals. It submits your withdrawal transaction on your behalf so your receiving wallet can withdraw without any SOL of its own, and without linking a funding transaction from another wallet. ### When to use the relayer * **Fresh receive wallet.** The withdrawal target is a wallet with no history. Funding it yourself would leak the link you are trying to avoid. * **Privacy on the submitter.** Even if your target wallet has SOL, the wallet that submits the transaction appears in the transaction metadata. A relayer-submitted transaction reveals nothing about you on that layer. ### When not to use the relayer * **Your target wallet already has SOL for gas.** You save the relayer fee by submitting directly. * **You want instant submission with no dependency on a third-party service.** Direct submission is a single round-trip. ### Using the relayer in the app 1. **Open the withdraw flow** for Private Send or Shielded Pools. 2. **Enter your note and recipient address.** 3. **Toggle "Use relayer".** Send labels the toggle "Use relayer (withdraw to a fresh wallet)"; Shield labels it "Use relayer". The app displays the quoted relayer fee after the toggle is on. 4. **Confirm and submit.** The relayer returns a job ID. The app polls the job and displays the final transaction signature when it lands. ### How the relayer gets paid The relayer takes its fee from the withdrawn amount, not from a separate transfer. For a 1 SOL withdrawal, you might receive 0.999 SOL minus the relayer's quoted share. No separate SOL spend is required on your side. ### If the relayer fails A job can fail if the proof is invalid, if the target cannot receive the token (rare edge case with associated token accounts), or if Solana network conditions cause the transaction to expire. A failed job preserves your note; you can retry via the relayer or submit directly. See [Relayers](/mixfun/concepts/relayers.md) for the conceptual detail. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://mixfun.gitbook.io/mixfun/guides/use-the-relayer.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.