• © Goverland Inc. 2026
  • v1.0.5
  • Privacy Policy
  • Terms of Use
YamYamby0x689c44E0f4D91AabD7d66B23b29032b665e99b4b0x689c…9b4b

YIP-25 Bug Bounty Program

Voting ended over 5 years agoSucceeded

YAM Bug Bounty Program

Basic Summary In addition to the completed and potential future audits, we would like to set up a community bug bounty forum to get more eyes on the code and increase security.

We will use a weighted average of the below votes to determine the Max Reward for the bug bounty.

Abstract While audits offer a base level of confidence in a protocol, history has shown time and again that they are by no means a guarantee of security and the additional scrutiny of community members can uncover missed vulnerabilities. We propose to use Gitcoin Grant audit and potentially treasury funds to sponsor a bug bounty program for the YAM protocol. Rewards will be tiered based on severity of issue disclosed.

Motivation Make Yam more secure.

Specifications Rewards will be based on the CVSS (Common Vulnerability Scoring Standard) but ultimately subject to tokenholder vote. In the event of a vulnerability disclosure, an emergency proposal will be sent immediately for on-chain governance execution, skipping the typical forum and off-chain steps in the process in order to expedite the fix. Such a proposal would include both the fix and reward to the discoverer of the vulnerability.

Funding of the bug bounty will first come from the Gitcoin Grants audit fund, though once this has been depleted, future funding will be sourced from the treasury.

Rewards will be scaled according to the severity of the bug.

Critical - Max Reward High - 50% of Max Reward Medium - 20% of Max Reward Low - 5% of Max Reward

We will use a weighted average of the below votes to determine the Max Reward for the bug bounty.

Off-Chain Vote

$10,000
11.19 0%
$20,000
92.42 0%
$30,000
62.41 0%
$40,000
2.62K 1%
$50,000
257.75K 98.9%
Against Bug Bounty
83.08 0%
Download mobile app to vote

Timeline

Sep 14, 2020Proposal created
Sep 14, 2020Proposal vote started
Sep 17, 2020Proposal vote ended
Jan 23, 2024Proposal updated