Privacy and responsible use
The relay tools on J Tools route funds through intermediate wallets so the path from sender to receiver is not a single visible line on-chain. That is the whole feature, and it is useful for ordinary reasons: keeping a treasury address off the radar, separating a public-facing wallet from a working one, or moving funds without broadcasting the link to anyone watching the explorer. This page is about using that feature honestly, and the limits of what it actually gives you.
Two tools provide the relay hops. Relay Transfer routes a single source-to-destination move through a chain of fresh wallets. Multi To Multi Relay does the same across many paired sources and destinations at once. Both generate the intermediate wallets in your session and hand you a recovery file of their keys before the run starts.
What relays do, and what they do not
#what-relays-do-and-what-they-do-notBe precise here, because “privacy tool” gets read as “untraceable” and the two are not the same.
- What they do Break the direct one-hop link between a source and a destination by routing through wallets you never reuse. Add configurable delays so moves don't all fire at once. Give you per-hop visibility and a recovery file.
- What they do not do Make a transfer anonymous, mix your funds with anyone else's, or remove the trail from the chain. Every hop is a public, permanent transaction that analysis can trace end to end.
A relay is one source flowing into one destination through wallets that only ever held your money. There is no shared pool and no other participant, so anyone with the patience to walk the hops can connect the ends. More hops and longer delays raise the effort it takes, but they do not sever the link. Plan around your own threat model, and assume a determined observer can follow the path.
Responsible use
#responsible-useThese tools exist for legitimate privacy and operational reasons. The line is not subtle.
- Acceptable: protecting wallet addresses you control from casual observation, separating concerns between your own wallets, moving funds you legitimately own without advertising the route.
- Not acceptable: laundering, hiding stolen or fraudulently obtained funds, evading sanctions or law enforcement, or structuring transfers to defeat reporting obligations you are subject to.
You are responsible for following the laws and regulations that apply to you. J Tools is non-custodial software. Many tools accept a pasted private key: the multi-wallet tools import keys for the wallets they drive, and most single-wallet tools offer a Local Signer option next to your connected wallet. Where a tool offers both, you can sign with your connected wallet instead. We do not move your funds for you and we cannot reverse a transfer once it is signed. The responsibility for how the tool is used sits entirely with the person running it.
If a use case feels like it needs to be hidden from a regulator or a court, that is the signal to stop, not to add more hops.
The pasted-key caution
#the-pasted-key-cautionThe relay tools work with private keys you bring to the page, and a pasted key carries more risk than a key that never leaves your wallet extension. Relay Transfer’s Local Signer mode and the entire Multi To Multi Relay flow read raw keys so every hop can sign without a wallet prompt. Relay Transfer’s Wallet mode keeps your key in the extension and asks for one approval on the first hop, but it is SOL-only, so any SPL relay goes through a pasted key. Pasted keys stay in your browser session and never reach our servers; only signed transactions leave the page. The recovery file you download holds the generated relay wallets, not the key you pasted. Even so, a pasted key is a key out of its vault, so treat the wallets you use here as disposable.
This is an architecture rule on our side too. Outside the key fields on the tool pages themselves, J Tools will never ask you for a private key, and any message claiming to be from J Tools that requests your seed phrase or key is a scam. For the wider non-custodial model and how signing works everywhere else, see the security overview.
Related
#related- Relay Transfer Route SOL or an SPL token to its destination through a chain of freshly generated relay wallets, so the path is not a single direct transfer. 0.00023 SOL per hop
- Multi To Multi Relay Route many paired source-to-destination Solana transfers at once, each through its own chain of freshly generated relay wallets. 0.00023 SOL per relay hop
© 2026 J Tools