Cowrie Research

hats-finance-primary-sources-2026-04-27

3 min read

Hats Finance primary-source snapshot

Last reviewed: 2026-04-27 UTC

Project status snapshot

What the official materials say

1) Docs root and overview framing

  • URLs:
  • Key takeaways:
    • Hats Finance frames itself as a decentralized security platform for DeFi and broader web3 rather than a conventional audit firm
    • The official docs center audit competitions, bug bounties, decentralized arbitration, solo-auditor participation, and continuous-audit workflows
    • The docs explicitly say Hats is a non-custodial protocol for bug bounties and audit competitions, which is a key categorization clue
    • The incentive framing is important: Hats emphasizes pay-for-results, onchain submission, and direct alignment between protocols and security researchers

2) Audit-competition product

  • URL: https://docs.hats.finance/welcome-to-hats-finance/audit-competitions
  • Key takeaways:
    • Hats positions audit competitions as a crowd-based complement to or follow-on from traditional audits, especially for already-reviewed code bases
    • The process includes scoped rewards, onchain competition vaults, open or allowlisted researcher participation, onchain finding submission, and reward distribution based on severity and uniqueness
    • The docs say only the first unique submission for an issue is rewarded, which distinguishes Hats from simpler pooled-prize competition models
    • The protocol-facing promise is shorter cycle time, broader reviewer diversity, and payment only for actual findings

3) Bug-bounty product

  • URL: https://docs.hats.finance/welcome-to-hats-finance/bug-bounties
  • Key takeaways:
    • Hats presents bug-bounty vaults as a perpetual, permissionless, privacy-preserving marketplace for vulnerability information
    • The docs say projects can create a vault, define a committee, fund it with project tokens, and then review encrypted disclosures backed by onchain hash proofs
    • A notable claim is that anyone can provide liquidity to bug bounties, which makes the product feel closer to a security marketplace than a managed SaaS program

4) GitHub org and contract repo

  • URLs:
  • Key takeaways:
    • The public org mixes platform repos with many per-competition repos, which corroborates that competitions are a core operating surface rather than just marketing copy
    • The hats-contracts README describes an onchain-bounty system with committees responsible for approving or rejecting claims and a HAT token intended to help bootstrap the two-sided market
    • The repo also notes that audit reports live in-repo, which is useful evidence that public security artifacts are part of the project surface

Whitepaper / technical-doc status

  • No canonical standalone Hats Finance whitepaper or litepaper surfaced in this pass.
  • The strongest current source of truth is the official docs corpus plus the public GitHub org and contract repository.
  • If revisited later, the most useful deeper follow-up likely lives in dispute/arbitration docs, tokenomics/governance pages, and the current live app/vault contracts rather than in a missing PDF.

Research notes

  • Best current category for the library: web3 security marketplace / decentralized bug-bounty infrastructure / audit-competition control plane.
  • The key insight is that Hats is trying to turn protocol security review into a structured onchain marketplace, not merely sell audits.
  • It is worth noting that some docs language is aspirational around arbitration and token-governance features, so future passes should distinguish current live mechanisms from roadmap claims.

Graph View