Sherlock AI has been putting up insane results lately.
In the past month:
- adopted for internal security review by two leading protocols, including one of the largest DeFi protocols in the world
- found a confirmed High-severity vulnerability in a complex cross-chain lending protocol shortly after a Tier 1 private audit from another firm
- identified a validated Critical in a large L1 security review, alongside multiple validated Mediums
Every model upgrade and review cycle is showing up in the results.
Proud of the team.
The Polygon Heimdall v2 security engagement starts Monday.
First-wave account creation invites have been sent by email and direct message to selected researchers and AI auditors.
Invited accounts can complete setup ahead of launch. If you want to participate, applications are still open through the Google Form throughout the engagement.
Setup guide below.
Applications are now open for the Sherlock x @0xPolygon Heimdall v2 security engagement.
Individual security researchers and teams building AI auditors / agents are welcome to apply.
Accepted applicants will receive next steps by email - Kicks off June 15.
Apply here 👇 https://t.co/jOQOZv9I0j
The next era of Web3 infrastructure deserves a brand new type of security review.
For @0xPolygon's Heimdall v2 upgrade, Sherlock is bringing that model to life.
June 15 to July 6.
A completely new security format is emerging.
One of the biggest protocols in Web3 is working with Sherlock to put it to the test.
June 15 to July 6.
More revealed tomorrow.
Carl Jung once said that one of the most destructive forces a person can carry is unused creative energy. if you have something in you that wants to be made and you keep refusing to make it, that energy does not just go away. it turns inward and starts working against you.
Every time I think I can fully rely on one frontier model, the other one proves me wrong.
Claude just completely failed to help me fix Google Ads conversion tagging. GPT 5.5 walked me through it perfectly first shot.
One is always better at something the other isn’t.
Imagine spending $20K on an audit, the auditor slaps a report on your desk and calls it a day.
You’re left wondering if your code is safer or if you just bought a very expensive PDF.
Teams deserve better than this.
This has been one of the MOST COMMON conversations we’re having with teams right now.
Your contracts can pass review, but attackers are increasingly finding the gaps around them: leaked keys, compromised infra, poisoned dependencies, and signer workflows.
We had our security researchers dig into some of the most important OpSec fundamentals your team should be implementing.
Quick writeup below.
Code4rena helped define an important era of Web3 security.
They helped prove that open competition could find bugs traditional audits missed, that independent researchers could become one of the best sources of security talent, and that great audit talent can come from anywhere.
Respect to the C4 team and everyone who helped build that community.
Sherlock will keep pushing competitive security into its next era.