QED Audit (@qed_audit) 's Twitter Profile
QED Audit

@qed_audit

Concluding web3 security.

ID: 1996086952970649605

linkhttp://qedaudit.io calendar_today03-12-2025 05:20:20

23 Tweet

440 Takipçi

4 Takip Edilen

QED Audit (@qed_audit) 's Twitter Profile Photo

cdc0f73e39eeff1e875baa3d076475e281dfda9cf8b4d76bb55328b4b58611a0 dc3fc1313818a0a8544992066ccfdd205f9f22da1888c8786160351081201c17

Raiders (@__raiders) 's Twitter Profile Photo

If integrated AI + fuzzing + formal verification finds real bugs. So why no persistent scanner for high-TVL chains? lot's of potential usecase which helps with: → Continuous detection across live contracts → Responsible disclosure pipeline to affected teams → Public feed of

noah.eth (@noahmarconi) 's Twitter Profile Photo

LLM: finds bug CT: doesn’t count, junior could do it LLM: claims bounty CT: show receipts, doesn’t count LLM: wins competition CT: large codebase, previous audit, doesn’t count None of those headlines claim humans in the mix aren’t productive. It’s been established that

sahuang (@sahuang97) 's Twitter Profile Photo

Interesting article by r0bre | Accretion.xyz. Some of my takes: To prove the effectiveness of AI tools, I think it's definitely the best to showcase in a bounty/contest with explanations of the architecture/logics. The Cosmos bug from QED Audit and Monad win from Octane Security are very