Engine decides, you confirm
5 adaptive privacy levels — Public, Pseudo-Private, Private, Ghost, Selective — chosen by the context engine, never by a manual toggle.
Your wallet should decide when to go private. Not you.
AnonProof embeds a 5-level adaptive privacy engine inside your existing wallet — public, pseudo-private, private, ghost, and selective reveal — so every transaction gets the right protection without a single toggle.
wallet/privacy-engine.tsdecision trace
57
const intent = wallet.intent({ to, value, note })user: confirmed58
const recipient = await oracle.reputation(to)risk: medium59
const exposure = await scanner.walletHistory(sender)doxx links: 260
61
const level = engine.recommend({model: adaptive62
intent, recipient, exposure,public: no63
overrides: user.preferences,user control: on64
})level: private65
const route = await stealthAddress.derive(to)erc-556466
await anonproof.send({ route, level })sender link: hidden67
selectiveReveal.grant(auditor, scope)revocable68
69
return { privacy: level, disclosure: 'scoped' }ready5adaptive privacy levels
86.5%shielded tx adoption (industry)
0wallets to migrate
Adaptive Privacy
Five privacy levels. Zero decisions required from the user.
Legacy wallets leak everything by default. AnonProof queries the reputation oracle, scans wallet exposure history, and weighs transaction value against intent — then routes your send through the right privacy level automatically. Learn more ->
ERC-5564Privacy PoolsEVM
ModeAdaptive
Select risk signal=Recipient reputation+
Window1m
Recipient Risk Score
Privacy Score
Public Exposure
Make every transaction privacy-aware without forcing users to become privacy experts
Soulbound privacy score
A non-transferable reputation that follows your wallet: doxx exposure, address reuse, approval hygiene, and privacy-preserving behavior over time.
Selective reveal grants
Cryptographic, revocable, scoped disclosures to auditors or counterparties. Stay private by default — prove selectively when required.
AI Integration
Privacy your wallet explains — not a setting you memorize.
Natural Language Privacy
Ask why a transaction should be routed private, ghost, or selectively-revealable before you sign — explained in plain language, not jargon.
✳◆✦
Hey Alex
How can I help you?
Should I hide this transaction?
+Ask privacy engine↑
Contextual Risk Insights
The AI advisor reads recipient reputation, wallet exposure history, and transaction value — without ever exposing raw on-chain data.
Oracle Connected
Why is this address flagged as risky?
Querying oracle, scanner, and engine...✓ Queried reputation oracle✓ Checked wallet exposure history✓ Compared value and recipient pattern
This recipient shows 4 exchange-linked transfers and weak address hygiene. I recommend Private mode for this send.
Smarter Privacy Routing
The engine maps risk signals to the right privacy primitive — stealth addresses, privacy pools, burner wallets, or selective reveal grants.
ϟ
1 function routePayment(tx) {
2 const route = []
4 if (tx.risk > 70) {
5 route.push("ghost")
6 }
8 grantReveal(auditor, scope)
9 return route
10 }
Instant Setup
Add adaptive privacy to a wallet flow in minutes.
A wallet-native privacy layer that works alongside MMetaMask, runs seamlessly with RRabby, routes across BBase, and settles on ΞEthereum — stealth addresses, privacy pools, burner mode, and selective reveal without migrating wallets.