Audit PDFs show what was reviewed at one point in time. Proof of Audits connects that evidence to the code running now. Enter a chain and contract address to inspect the current evidence state, see what was reviewed, check whether the live deployment still matches, and surface anything changed, missing, or unverified. Protocols can turn that evidence into a living Trust Passport instead of relying on a static audit PDF..
Hey Product Hunt 👋
I’m Veer, founder of Proof of Audits.
This started with something that bothered me as a Web3 user.
I’m about to put money into a protocol and my wallet asks me to confirm a transaction.
The protocol says:
“Audited ✓”
Cool.
But audited what?
Is the contract my wallet is calling the same code that was reviewed?
Was the function I’m about to use actually inside that review?
Who reviewed it?
Has that code changed since?
Were important findings actually fixed and checked again?
And who can still upgrade, pause or change the system after I put my money in?
The answers usually exist somewhere.
Audit PDFs. GitHub. Block explorers. Governance docs. Multisigs.
The user is expected to connect all of that themselves.
That’s what I’m trying to change with Proof of Audits.
Right now, you can enter a chain + contract address and check the evidence we have for that exact deployment.
If we can verify something, we show the evidence.
If the code changed, that should be visible.
If we don’t have enough evidence, it stays unknown. We don’t turn “unknown” into “safe.”
The next part I care a lot about is bringing that same proof closer to the wallet decision itself, so you don’t need to become a security researcher every time you’re about to sign something.
If you use DeFi, I’d genuinely like to know:
right before you click Confirm, what would you want your wallet to tell you?