$BONK
Fading QuicklySnapshot Window: 2026-07-10 14:00 UTC · ← Back to Crypto Overview
Social Momentum Summary
Total Engagement - Comments: 1, Retweets: 1, Likes: 3, Impressions: 38
Verbatim Community Citations & Social Evidence 1 source posts analyzed
Update on Aevum Protocol — Hexens audit signed, ETHOnline confirmed, 58 days out A few weeks ago I posted asking for technical feedback on my on-chain reputation + identity system for AI agents. The thread was genuinely useful — surfaced real gaps in the Sybil-resistance model, vault permission design, and on-chain vs off-chain scoring tradeoffs. I wrote up what I got wrong here: paragraph.com/@aevumprotocol/i-asked-rethdev Here’s where things stand now: Audit Signed with Hexens. Kasper Zwijsen is leading — he found the critical bug that saved $800M in the POL migration and has led audits for EigenLayer, Lido, and LayerZero. Kickoff July 27, findings August 3, final report mid-August. That gives a clean window before ETHOnline (Sept 4). Before Hexens, the contracts went through 10 internal hardening rounds — manual review, Slither passes, Claude Opus deep review, and an independent review by Martín Pérez (blockchain protocol engineer, built AutonomiX with ERC-8004 agent identity and x402 micropayments). 41 issues found and resolved across those rounds. KNOWN_LIMITATIONS.md is public on GitHub with everything we know is imperfect going into the audit. ETHOnline 2026 Registered, staked, confirmed on the Continuity Track targeting Top 10 Finalist. September 4-16. React frontend is live now at aevum-frontend.vercel.app — all 8 Sepolia contracts, real transactions, no mock data. What’s still open The architectural questions the thread raised — Sybil-resistance, evidence vs scoring separation, permission expiry — are tracked in the v2 roadmap. None of them are getting fixed before the audit closes. That’s the honest state of it. GitHub: github.com/AevumProtocol/contracts Frontend: aevum-frontend.vercel.app Writing: paragraph.com/@aevumprotocol