Donor privacy
AnonFund protects the person collecting the funds. Donors are ordinary transaction senders. This page explains what that means and what a donor can do about it.
What a donation reveals
A donation is a normal BNB transaction to the AnonFund contract calling donate(campaignId). Anyone can see the sending address, the amount, the time and the campaign id. If the sending address is linked to your identity — through an exchange withdrawal, an ENS-style name, a public post, or past activity — the donation is linked too.
Practical guidance
- Use a dedicated wallet. Create a wallet that you use only for donations and nothing else. Do not reuse it for trading, NFTs or anything tied to your name.
- Fund it indirectly. Funding the donation wallet straight from your main wallet creates a one-hop link. Prefer a withdrawal from a centralised exchange account (the link then exists only inside the exchange) or a privacy-preserving protocol you trust.
- Avoid distinctive amounts. Round numbers that many people use are harder to correlate than 0.3141 BNB.
- Mind the network layer. Your wallet's RPC provider sees your IP alongside the transaction. Use a VPN or Tor and a wallet that lets you choose the RPC endpoint if network-level privacy matters to you.
- Do not announce it. Posting a transaction hash on social media defeats everything above.
What AnonFund does not do
AnonFund does not mix, shield or delay donations and does not offer a zero-knowledge donation path. Those are separate problems with separate trade-offs (trusted setups, anonymity-set size, regulatory exposure) and bolting them onto a fundraising contract would make it harder to audit. The contract is intentionally small: it accounts for donations and lets a signature release them.
For creators
Everything above applies to the collector wallet as well. It needs a little BNB for gas; obtain it the same indirect way. Never fund it from the creator wallet, and never send claimed funds back to the creator wallet.