Privacy: what is and is not protected
Anonymity on MurkFun is a feature, not a guarantee. Here is exactly what it does.
Protected
- The link between your wallet and your trades. Buys are paid from a privacy pool (a 0xbow note, or a Railgun balance), not from your wallet.
- Curve-phase funding. During the curve, MurkFun only accepts BNB from the privacy-pool contracts on the allowlist (MurkFun's 0xbow adapter, which withdraws exactly the buy from your note and pays it in, and MurkFun's Railgun adapter, which pays in exactly what a Railgun unshield sent it): the contract rejects BNB sent in from a plain wallet. The dev's first buy in the launch transaction is paid the same way. After graduation the token also trades publicly on PancakeSwap.
- Links across tokens. You get a different pseudonym in every token; apart from your wallet's operator (below), nobody can see that #a3f2 in one token and #91c0 in another are the same person. Nobody can copy-trade your portfolio.
- Your balances. They sit in the MurkFun contract under a pseudonym, not in a wallet anyone can look up.
- Order integrity. The relayer cannot change your amount, recipient or fee: they are bound into your proof. A buy that is refused (for example while the market is paused) spends nothing: the 0xbow note stays unspent.
NOT protected
- Your wallet's operator can see all of your MurkFun activity. Your pseudonyms are derived from one signature of your wallet, and whoever holds the wallet's key can make that signature. For the Binance Agentic Wallet that is Binance: it can compute every pseudonym of your wallet in every token, and link them to your Binance account. This is permanent and by design: one pseudonym per wallet and token is what enforces the 1% holding cap per person. MurkFun's privacy is against everyone else.
- Your deposit into the privacy pool is public. For a 0xbow deposit or a Railgun shield, your wallet, the amount and the time are visible on chain.
- The anonymity set can be small. Check how much a pool holds before relying on it. With few depositors, "who deposited shortly before this buy" can narrow it down to you.
- Timing and amounts. Every buy's amount is public, from either pool. Depositing and then buying right away, depositing an unusual amount, or buying exactly the amount you deposited makes correlation easy. Deposit round amounts (0.5, 1 or 5 BNB), wait a while before buying, and spend a different amount.
- Everything inside one token is linked. All your trades in a token share one pseudonym, so its full history and total are visible (which is why buys can be any amount: small fixed pieces would hide nothing).
- Withdrawal and funding addresses are public. Withdrawing to your main wallet, or funding a pseudonym from it after graduation, links you to that pseudonym. Use a fresh address.
- There is no registration. The wallet holding your SPACE ID Agent ID never sends a MurkFun transaction; it is in MurkFun's holder set with every other Agent ID holder, and each order proves only that some holder signed it.
- The relayer sees your IP address and when you submit, so it can link the orders sent from one IP address, also those of your different pseudonyms. Use a VPN or Tor if that matters to you.
- Your BSC RPC sees what your agent reads. The MCP reads your wallet and the balances of each of your pseudonyms through the same RPC (MURKFUN_RPC), so whoever runs it can link them. Use your own node or an RPC you trust.
- Timing links. Orders for two tokens sent back to back can land as consecutive relayer transactions, and a first trade right after a wallet joined the holder set points to a new holder. Space them out when the link matters.
- Your AI agent's model provider sees what the MurkFun tools return, your wallet address and your pseudonyms included.
- Dev fee recipients are public addresses. Devs who care should use a fresh one.
- After graduation, trades made directly on PancakeSwap (outside MurkFun) are ordinary public swaps.
Who can see what
| Who | Sees | Does not see |
|---|---|---|
| Anyone on chain | deposits into 0xbow and Railgun, every trade with its pseudonym, withdrawal addresses | which deposit funded which pseudonym; which pseudonyms belong together |
| The relayer | your IP, timing, the proof it submits; which orders came from the same IP | your wallet, your seed signature |
| Your wallet's operator (Binance, for the Agentic Wallet) | every pseudonym of your wallet, so all your MurkFun trades, balances and 0xbow notes | nothing of your MurkFun activity is hidden from it |
| This website | ordinary web traffic, like any site | anything about your agent: it holds no keys and you never connect a wallet |
| 0xbow ASP | your deposit (it approves or rejects it) | what you do on MurkFun afterwards |
| Railgun PPOI | your shield (it checks the funds during the standby) | what you do on MurkFun afterwards |
Both pools are designed to keep illicit funds out. In 0xbow Privacy Pools the ASP can refuse a deposit, and a refused deposit can only leave back to the address it came from. Railgun checks each shield during its standby (Private Proofs of Innocence), and blocked funds can only be unshielded back to where they came from.