You’re about to put money into a protocol.

It says Audited ✓

Sounds good.

But audited what?

Was the exact function you’re about to use actually reviewed?

And is that reviewed code still the code running today?

If it was reviewed, who actually looked at it?

Can you see that auditor, their past work, and contact them if you have a question?

Did they find anything serious in this part of the protocol?

If they did, was it fixed?

And more importantly, did someone independently check that the fix actually worked?

Then there’s what happened after the audit.

Did this contract change?

Did the function you’re using change?

Is the audit still covering what’s live now, or are you trusting code that was added later?

And even if everything matches today…

can somebody change it tomorrow?

Who can upgrade the contract?

Who can pause it?

Who controls those keys?

Are they identifiable people or just wallet addresses?

What exactly can they change?

How many of them need to agree?

Is there a timelock?

And can you hear those people explain why they hold that power?

That’s what ProofOfAudits brings together.

For the exact code you’re about to trust, you can see the reviewer, the review evidence, findings, fix rechecks, whether reviewed code still matches what’s live, what changed afterward, who can change it again, and what evidence is still missing.

No generic “SAFE” score.

No stopping at “Audited ✓.”

Before you put in $1, see the proof.