Update on Aevum Protocol — Hexens audit signed, ETHOnline confirmed, 58 days out
Post original
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 r/ethdev 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   submitted by   /u/Bright_Clerk1452 [link]   [comments]
Rascunhos
congrats on the hexens audit signing — kasper's team is legit. that KNOWN_LIMITATIONS.md move is underrated, shows you're not hiding ball from auditors. curious how you're thinking about the permission expiry design for v2, that was the thorniest part imo.
gm — saw your aevum update and ngl the level of prep you put in before even hitting hexens caught my eye. i'm close with the wevolv3 team, they ship hard on the exact stuff you're working through (smart contracts, dapp frontends, agent infra). if you ever need extra hands for the v2 push or want a sounding board from folks who've been in the trenches, happy to intro you to them.
Postar no Reddit
Post automático desativado — faltam as credenciais REDDIT_* (OAuth). Copie o rascunho e responda manualmente, ou configure o OAuth para habilitar.