Hats Finance
- Name: Hats Finance
- URL: https://www.hats.finance/
- Category: security marketplace / onchain bounty-vault experiment
- Summary: Hats Finance survives because the bounty vault is onchain and the committee/arbitration path is at least exposed. Strip that away and it is mostly another hosted contest-and-bounty venue.
- What it does:
- Runs smart-contract audit competitions where projects fund rewards and researchers compete to surface valid findings
- Offers bug-bounty programs built around onchain bounty vaults, encrypted disclosure channels, committee review, and proof-of-submission flows
- Uses first-unique-submission reward logic in competitions, making timing and duplicate handling part of the mechanism rather than mere moderation policy
- Positions disputes around severity or validity for decentralized arbitration instead of leaving everything to a closed platform operator
- Publishes smart-contract infrastructure and competition repositories through its public GitHub org
- Key claims:
- The docs describe Hats as a non-custodial bug-bounty and audit-competition protocol with onchain reward readiness via vault creation, which is the real reason the note survives
- The audit-competitions docs say only the first unique valid submission is rewarded, so duplicate policy and timing are built into payout logic instead of handled informally
- The bug-bounties docs frame bounty vaults as permissionless, privacy-preserving, and open to third-party liquidity, which makes funding architecture more explicit than in a normal SaaS bounty platform
- The public GitHub org and
hats-contractsrepo show Hats publishing the underlying contract layer rather than operating only as a closed dashboard
- Whitepaper: No canonical standalone Hats Finance whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official docs plus the public GitHub org and contract repo notes saved in
../whitepapers/hats-finance-primary-sources-2026-04-27.md.
Sources
- https://www.hats.finance/
- https://docs.hats.finance/
- https://docs.hats.finance/welcome-to-hats-finance/master
- https://docs.hats.finance/welcome-to-hats-finance/audit-competitions
- https://docs.hats.finance/welcome-to-hats-finance/bug-bounties
- https://github.com/hats-finance
- https://raw.githubusercontent.com/hats-finance/hats-contracts/master/README.md
Internal linkages
Control surface
-
The leverage sits in bounty-vault funding, submission-timing rules, committee review, severity decisions, encrypted disclosure handling, and whether arbitration ever becomes more than a marketing layer.
-
The onchain vault matters because payout readiness is legible instead of disappearing inside a platform treasury.
-
Treat Hats as a narrow onchain-funding specimen, not as a category anchor.
-
Last reviewed: 2026-06-18 UTC