[ARCHIVED] Bug Bounty Vault Proposal by Hats Finance

[DISCUSSION] Bug Bounty Vault Proposal by Hats Finance

Background

The direct losses from hacks and exploits between 2020-2022 are above $15B, and yet, the solutions currently being offered are not decentralized, permissionless, scalable, and continuous and open to everybody like Mantle is.

This proposal aims to create an incentives pool on Hats Protocol for hackers/auditors to help protect the Mantle smart contracts. The goal of the vault is to incentivize responsible vulnerability disclosure for Mantle. Liquidity can be added (with $MNT and/or yield-bearing tokens) permissionless and LPs will be rewarded with $HAT tokens once the liquidity mining program is launched.

Proposal

Hats.finance is an on-chain decentralized bug bounty platform specifically designed to prevent crypto-hack incidents by offering the right incentives. Additionally, Hats.finance allows anyone to add liquidity to a smart bug bounty. Hackers can disclose vulnerabilities responsibly without KYC & be rewarded with scalable prizes & NFTs for their work.

Smart bug bounty programs are a win-win for everyone. They can be created easily with a few on-chain transactions (it takes less than 1 hour to set up a vault on Hats), and are free of charge. Hats will only charge a fee once an incident has been successfully mitigated. The protocol will retain 10% of the payout as fee from the security researcher. Scenarios of an exploit are way more costly and can cause irreversible damage. More importantly, the bounty program is transparent, decentralized, and gives power to the community of the project.

On-chain submission:

With the values of Ethereum, which are lighting our way, we decided to take a different approach to bug bounty compared to the traditional and centralized bug bounty platforms.

The submitter writes a detailed vulnerability description on Hats dApp. The submission is encrypted with the project PGP key. The user hashes the encrypted description (automatically) and sends a transaction on-chain with that Hash (only the Hash of the encrypted report is going on-chain), While sending the encrypted message to the routing bot.

The tx fee acts as a spam filter and can be set to a higher value (in the future).

The routing bot verifies that the Hash of the encrypted message was published on-chain and publishes the encrypted message to the committee group together with a link to a front-end open source tool to decrypt the messages that are stored on IPFS that is part of Hats dApp.

Next Steps

In case that the proposal gets accepted, Mantle is expected to:
1- Choose and set up a committee
2- Vote for DAO participation amount

Onboarding action items:

  • Choosing a committee: The committee is preferably the public multisig contract of Mantle or a multisig specifically set up to manage the bounty program.
  • The Committees responsibility:
    • Triage incoming vulnerability reports/claims from auditors/hackers (get back to the reporter within 12 hours).
    • Approve claims within a reasonable time frame (Max. of 6 days)
    • Set up repositories and contracts under review. (A list of all contracts covered by the bounty program separated by severity)

Rationale and Key Examples

The key advantage of Hats solution compared to traditional, centralized bug bounty services:

  • Bug bounty vaults are loaded with the native or yield bearing token of each project. Reducing the free floating supply while giving the token additional utility.
  • Scalable bounty network — vault TVL increases with success / token appreciation of the project.
  • Open & Permissionless — Anyone can participate in the protection of an asset they are a stakeholder of and any hacker, anywhere in the world, can participate anonymously when disclosing exploits (no KYC needed)
  • In the future when providing liquidity (taking risk) every depositor could earn $HAT tokens.
  • Continuous — As long as tokens are locked in the vault, hackers are incentivized to disclose vulnerabilities through Hats, instead of exploiting the project.

Additional advantages of deployment of the existing Mantle bug bounty program on Hats Protocol:

  • Mantle can reach out to many more security researchers (aka white hat hackers) with a bounty on Hats protocol and each scrutiny will make Mantle safer.
  • Mantle can fund the bug bounty vault on Hats with its own native token ($MNT or yield bearing token)
  • The bounty reward for the submitter is not paid at once to reduce the price pressure on the project token.

Since Mantle DAO will be farming $HAT tokens with its bounty (after TGE), it’s a cost negative opportunity for Mantle DAO.

Key Examples

A security researcher recently found a critical severity within Premia Finance’s staking contracts and got rewarded $70k for his responsible disclosure (Kindly check Hats Finance Medium for more information).

In one of the recent audit competitions, the security researchers could find 3 critical severities in Raft Finance’s code in a 7 days long audit contest even if the project went under an extensive audit by one of the top-tier auditing firms in the space (Kindly check Hats Finance Medium for more information).

12 Likes

You can find the relevant links here:
https://twitter.com/HatsFinance/status/1663243357160890369

Raft Finance Audit Competition- Final Note | by HatsFinance | Medium

4 Likes

Overall it sounds as reasonable proposal.

4 Likes

Hey @mmarecka80! Thanks a lot for taking the time to reflect and supporting the proposal! Appreciate it :white_heart: :100:

2 Likes

Sounds not only good, it is what all and everyone should be doing.

2 Likes

Agreed. I recommend registering, I trust this project

2 Likes

agreed this :heart: :heart: :heart: :heart: :heart:

2 Likes

Good initiative; you have my support

2 Likes

I suport this. can’t wait to see just how this fairs in the bull run.

1 Like

@Fav_Truffe In keeping with the guidelines of the forum , this discussion will be archived for the following reasons:

  • The discussion has not received a comment for over two weeks.
  • The post has not yet received significant support from delegates, large token holders, or core development teams.
1 Like