HackenProof Docs
  • Welcome
    • HackenProof
      • Services we provide
      • Our resources
    • Integrations
      • Slack
      • Discord
      • Telegram
      • Zapier (Webhook)
        • Zapier -> Lark
        • Zapier -> Linear
        • Zapier -> Jira Service Management
        • Zapier -> PagerDuty
        • Zapier -> Google Chat
        • Zapier -> ClickUp
      • Jira Software
      • GitHub Issue
      • GitLab Issue
      • VDP iFrame
    • FAQ
      • Audit & Bug Bounty (BB)
      • Crowdsourced Audit & BB
      • Penetration testing & BB
    • Emergency
      • Reset 2FA
    • Code of Conduct
    • Referral Program
  • Bug Bounty
    • Bug Bounty process
    • How to start Bug Bounty
    • How to create a VDP
    • Vulnerability classification
      • Web & Mobile
        • Out-of-Scope Bugs
      • Smart contracts
      • Blockchain protocols
    • Reports Basics
      • Points Guide
      • Crafting a well-readable report
  • Dashboard
    • Company dashboard
      • Manage programs
      • Manage reports
      • Share report
      • Labels
      • E2E report encryption
      • Reports decrypting with Mailvelope
      • Users and roles
      • Program/Report Assignee
      • Replenish your balance
      • Integrations
    • Hacker dashboard
      • 👉How to start
      • Submit a report
      • Reports Basics
      • Vulnerability classification
      • 👮‍♂️KYC
      • Сreate a crypto wallet
      • 💸Withdraw bounty
      • Hacker Leaderboard
      • Reset 2FA
      • 🍕HackenProof community
      • Report ID
      • Private Program
      • Contact support
    • Company-Auditor dashboard
      • How to start
      • Add members
      • Submit report
      • Contact support
  • Crowdsourced audit
    • Audit process
    • How to start Audit
    • Supported tech
    • Vulnerability classification
    • Reports Basics
    • Qualified Auditors
    • Judging / Triaging
      • Targets
      • Team
    • [CA] Bounty Distribution Rules
    • Fee & Payments
  • DualDefense Audit
    • What is DualDefence Audit
    • General Guidelines
    • How DualDefence Audit goes
    • Contest Phases
    • Vulnerability classification
      • [DD] Smart Contracts
    • [DD] Bounty Distribution Rules
  • good to know
    • Changelog
    • Branding
    • Vulnerability Disclosure
  • Education
    • Courses
    • Tools
    • Useful sources
Powered by GitBook
On this page
  • 💰 Budget Allocation
  • 🔒 Fairness and Sybil Protection
  • 🧠 How it works:
  • 🧮 Real Example (Critical Issues)
  • 📌 Summary
  1. Crowdsourced audit

[CA] Bounty Distribution Rules

PreviousTeamNextFee & Payments

Last updated 26 days ago

In HackenProof Audit Contests, rewards are distributed fairly across valid issues, based on severity, uniqueness, and contribution quality. This system prevents Sybil attacks and incentivizes meaningful, original submissions.

💰 Budget Allocation

Each audit contest has a fixed reward pool, which is divided by issue severity:

Severity Category
% of Total Rewards

Critical

40%

High

30%

Medium

15%

Gas Optimizations & Best Practices

5%

Only valid, will be eligible for rewards.

🔒 Fairness and Sybil Protection

To prevent abuse (e.g., the same finding submitted from multiple accounts), we use a Sybil-resistant formula that rewards original, high-impact discoveries more than duplicated ones.

🧠 How it works:

If multiple researchers report the same issue, the reward for that issue is shared using the following formula:

Issue Weight = 1 × (0.9 ^ (N - 1)) / N

Where:

  • N = number of researchers who submitted the same issue

  • The fewer the reporters, the higher the reward each person receives

This ensures:

  • Original submitters earn more

  • Duplicate findings still get rewarded, but fairly

  • Submitting the same issue under multiple accounts does not result in more money

🧮 Real Example (Critical Issues)

Imagine the Critical pool is $40,000, and we have:

  • Issue A reported by 1 researcher → gets full weight

  • Issue B reported by 2 → shared weight

  • Issue C reported by 3 → shared with further reduced weight

Their weights:

  • A = 1.00

  • B = 0.45

  • C = ~0.27 Total weight = 1.72

Rewards:

  • Reporter of A: (1 / 1.72) × $40,000 ≈ $23,255

  • Each reporter of B: (0.45 / 1.72 / 2) × $40,000 ≈ $5,233

  • Each reporter of C: (0.27 / 1.72 / 3) × $40,000 ≈ $2,093

You’ll get a higher payout if you’re the first and only one to find a valid issue.


📌 Summary

  • All issues which improve the security of the protocol are eligible.

  • Originality is rewarded — submitting duplicates means smaller payouts.

  • No rewards for Low or Informational issues.


If you have any questions, feel free to reach out to our team in the HackenProof Discord or support channel.

Happy hacking! 👾

in-scope submissions