Hats.Finance 🦇🔊

The $HAT that protects DeFi through DeSec 🎩

Aligning incentives for projects & hackers through decentralized on-chain audit competitions & bug bounties.

[Hats.Finance 🦇🔊 @HatsFinance]

You want to level up as a security researcher? 🛡️

Hats Finance is hands-down the best place to do it. Here’s why🧵

[Hats.Finance 🦇🔊 @HatsFinance]

🚨 Important announcement:

Sadly, we’re announcing that https://t.co/DYqTNAq5RH is entering a final wind-down of its hosted operations. After a lot of reflection, we’ve reached the point where keeping a centralized UI and servers running is no longer sustainable, and there isn’t a new legal or operational wrapper planned to continue that hosted stack.

This is not easy to share. Hats have been a long, fascinating, sometimes brutal journey. Since 2021, we chased one belief: a decentralized market deserves decentralized security. Vitalik’s narrative about systems sharing Web3's DNA was a compass for us, and Hats was built in that spirit.

But reality didn’t match the original thesis. Smart contract security budgets did not scale to DeFi-level volumes as we expected, and rapid progress in AI security tools, along with the maturation of secure, reusable smart contract building blocks, reduced the need for a protocol like Hats to sustain meaningful long-term demand for the HATS token.

What happens now:
* The https://t.co/DYqTNAq5RH hosted frontend and backend (UI and servers) are expected to go offline on Dec 31, 2025. Most functionality that depends on that hosted stack will be phased out.

* The Hats protocol remains deployed on-chain and governed by the DAO. Core contracts are intended to continue functioning according to their code.

* An IPFS build of the frontend is available today and may remain accessible via public gateways as long as it is being served (e.g., by pinning providers or community nodes). As payments to our current pinning provider (e.g. Pinata) will stop, we cannot guarantee its continued availability or performance.

Action for users with deposits:

If you want to withdraw via the hosted UI, we recommend starting a Withdraw Request by Dec 17, 2025 (7-day cooldown plus 7-day withdrawal window). If you miss the window, you can re-initiate a new request, or interact directly with the contracts at any time, subject to their logic and network conditions.

Thank you to everyone who believed in this experiment, used it, partnered with it, and pushed it forward. We’ll do our best as contributors to support the community through the wind-down.

Shared in our capacity as individual contributors to the Hats protocol, for information purposes only.

[Hats.Finance 🦇🔊 @HatsFinance]

@Kleros_io Congrats to the @Kleros_io audit competition winners 🔥
Rewards are live 👉 claim now 💰

Leaderboard & claims:
https://t.co/X5dtgkX6xE

Huge thanks to all auditors & sponsors!

[Hats.Finance 🦇🔊 @HatsFinance]

🚀 The @Kleros_io audit competition is officially live!

Before submitting, please review the open issues here:
🔗 https://t.co/9zdi65FwSi

Good luck to all participants; it's time to showcase your skills!

[Hats.Finance 🦇🔊 @HatsFinance]

Dispute Submission Guidelines:

If you believe a decision on your submission was incorrect, email [email protected] by October 16th 15:00 GMT and include:

1️⃣ Transaction ID
2️⃣ Pull-Request Link
3️⃣ Concise explanation of concern

Our security team will review the materials with the sponsor and provide a reasoned response , we rely on good-faith collaboration.

Important:

- Only your own submission can be disputed.

- Check sponsor feedback on your PR before raising a dispute.

- Arguments raised post-contest are unlikely to be accepted.

~95 % of disputes are upheld, build a strong, evidence-based case.

- Keep communication respectful and factual.

- Sponsor’s ruling is final.

Non-compliant emails will not be forwarded to the dispute process.

[Hats.Finance 🦇🔊 @HatsFinance]

Medium Severity (Issue #9)
🔗 https://t.co/5FwzUUIfHt

Low Severity (Issue #7)
🔗 https://t.co/DR1ssfcJVh

High-Quality Report Award (Issue #63)
🔗 https://t.co/c03S60mBwt

[Hats.Finance 🦇🔊 @HatsFinance]

The @Kleros_io Audit competition kicks off this Tuesday, Sept 23, at GMT.
Auditors can already opt-in and secure their spot:

👉 https://t.co/C9O08prQq2

⚡ Important ⚡

In the following article, you’ll find all the competition details, including the adapted severity definitions tailored to the Kleros competition and its unique codebase.

https://t.co/VhNIKOss4q

Join us to help protect Kleros’ code.

[Hats.Finance 🦇🔊 @HatsFinance]

💥 $80,000 USDC up for grabs for those who can spot vulnerabilities in ~3,870 SLOC!

The @Kleros_io audit competition kicks off Tuesday, Sept 23, 2025, with the following prize pool:

🔹 Low Severity → up to $800
🔹 Medium Severity → up to $16,000
🔹 High Severity → up to $32,000

👀 Don’t miss your chance. Sharpen your skills, find the bugs, claim the rewards.

👉 Join the competition & start hacking!

[Hats.Finance 🦇🔊 @HatsFinance]

🚨 New audit competition! 🚨

@Kleros_io x @HatsFinance Details coming soon 👀

Save the dates! 🗓️

[Hats.Finance 🦇🔊 @HatsFinance]

Congrats to the winners of the @dTRINITY_DeFi audit competition 🔥

Time to claim your rewards💰

Winners breakdown :
https://t.co/5oJkjN7n4K

Huge thanks to our auditors and sponsors, your efforts and support made this audit competition a success.

[dTRINITY (▲) @dTRINITY_DeFi]

☀️ DEFI SUMMER UPDATE ☀️

dTRINITY's TVL has reached $6M, with new partnerships and upcoming chain expansions set to drive our protocol's next phase of growth.

DeFi Summer has also returned as BTC touches $120K while ETH rebounds toward $5K!

Yield szn is back, baby 🚜

1/8

[Hats.Finance 🦇🔊 @HatsFinance]

We’d like to thank the @dTRINITY_DeFi team for choosing @HatsFinance and our decentralized audit model to secure their contracts. Throughout the competition, the team delivered top‑notch work, diving into every submission and providing clear, precise explanations for each approval or rejection.

Thanks for a great work!

[Hats.Finance 🦇🔊 @HatsFinance]

Preliminary winners of the @dTRINITY_DeFi audit competition are in!
Ran from June 16 - July 4 with up to $80K in USDC rewards for auditors.

328 issues submitted, 40 valid: 1 High, 3 Medium, 36 Low.

Unravel the thread for the winners' breakdown and their findings!

#HatsFinance #AuditCompetition

[Hats.Finance 🦇🔊 @HatsFinance]

Dispute Submission Guidelines:

If you believe a decision on your own submission was incorrect, email [email protected] by 25 July at 15:00 GMT and include:

1- Transaction ID of the submission

2- Pull‑request link

3- Concise, well‑structured explanation of the concern

4- Screenshots of any relevant correspondence with the committee

Our security team will review the materials with the sponsor and provide a reasoned response, we rely on good‑faith collaboration.

Important points to consider:

- Scope: Only your own submission can be disputed.

- Sponsor feedback first: Review the sponsor’s comments on your GitHub PR before raising a dispute; most clarifications are provided there.

- Relevance: Arguments that were not raised during the contest window are unlikely to be accepted.

- Historical outcome: About 95 % of disputes are upheld. Build a strong, evidence‑based case.

- Professional conduct: All communication must remain respectful, factual, and constructive.

- Decision hierarchy: The security team will do its best to mediate, but the sponsor’s ruling is final.

Any dispute email that does not comply with these guidelines will not be forwarded to the security team / dispute process.