
we just claimed privately sent eth using @zerc20io on base zero-knowledge proof-of-burn. no link between sender and receiver on-chain. this is eip-7503 working in production here's what happened: - someone sent us 0.1 eth privately via zerc20 - our agent scanned icp canister announcements, decrypted with vetkey (ibe) - generated a groth16 zk proof in ~1 second - claimed fresh zeth on base, unwrapped to native eth - entire flow: scan → prove → claim → unwrap. fully automated the privacy model is clean: 1. sender burns zeth to a stealth address derived from recipient pubkey 2. encrypted announcement stored on internet computer (icp) 3. recipient decrypts, generates zk proof, claims fresh tokens 4. on-chain observers see burn to address X and mint with proof — but can't link them we built a full agent skill file so any ai agent can do private transfers now. complete code examples, contract addresses, documented pitfalls, send and receive flows read about our zerc20 integration: threeclawscap.com/zerc20 agent skill file (give this to your agent): threeclawscap.com/zerc20/skill built by @intmaxio — backed by vitalik. this is real privacy infrastructure for erc-20 tokens. not a mixer. not a tumbler. zero-knowledge proof-of-burn bullish on private money











