Kwikswap Bug Bounty

Submit a report


Overview

Open source, on-chain protocols benefit from community member participation in testing and debugging the smart contracts. As the launch of the Kwikswap protocol (“Kwikswap”) approaches, it is beneficial to formalize the program incentivizing those dedicated security engineers who can help make Kwikswap safer (the “Program”). The Program will bolster the professional audits and formal verification Kwikswap has undergone.

Scope

This Program is limited to the vulnerabilities affecting Kwikswap in the following contracts:

Kwikswap Core
Periphery Contracts

For purposes of the Program, bugs in Periphery Contracts will be considered less severe than those found in Kwikswap V1 Core.

The following are not within the scope of the Program:

  • The example contracts and the contracts in the test folder for the Periphery Contracts link set forth above;
  • Any contract removed from the list of contracts in the Periphery Contracts link set forth above (such list may change from time to time without notice);
  • Bugs in any third party contract or platform that interacts with Kwikswap;
  • Vulnerabilities already reported and/or discovered in contracts built by third parties on Kwikswap; and
  • Any already-reported bugs.

Vulnerabilities contingent upon the occurrence of any of the following activities also are outside the scope of this Program:

Front end bugs;

  • DDOS attack;
  • Spamming;
  • Automated tools; and
  • Compromising or misusing third party systems or services.

Program Rewards

Severity of bugs will be assessed under the CVSS Risk Rating scale, as follows:

  • Critical (9.0-10.0): Up to $40,000
  • High (7.0-8.9): Up to $10,000
  • Medium (4.0-6.9): Up to $2,000
  • Low (0.1-3.9): Up to $1,000

In addition to assessing severity, rewards will be considered based on the impact of the discovered vulnerability as well as the level of difficulty in discovering such vulnerability.

Prior to the deployment of Kwikswap V1 to the Ethereum mainnet, which is expected to occur in Dec 2020, successful bug reporters will receive a 20% bonus on their bounty pay out. This is to incentivize hackers to come forward before launch.

Disclosure

Any vulnerability or bug discovered must be reported only to the following email: [email protected]; must not be disclosed publicly; must not be disclosed to any other person, entity or email address prior to disclosure to the [email protected] email; and must not be disclosed in any way other than to the [email protected] email. In addition, disclosure to [email protected] must be made promptly following discovery of the vulnerability. Please include as much information about the vulnerability as possible, including:

  • The conditions on which reproducing the bug is contingent.
  • The steps needed to reproduce the bug or, preferably, a proof of concept.
  • The potential implications of the vulnerability being abused.

A detailed report of a vulnerability increases the likelihood of a reward and may increase the reward amount.

Anyone who reports a unique, previously-unreported vulnerability that results in a change to the code or a configuration change and who keeps such vulnerability confidential until it has been resolved by our engineers will be recognized publicly for their contribution, if agreed.

Eligibility

To be eligible for a reward under this Program, you must:

  • Discover a previously unreported, non-public vulnerability that would result in a loss of or a lock on any ERC-20 token on Kwikswap (but not on any third party platform interacting with Kwikswap) and that is within the scope of this Program.
  • Be the first to disclose the unique vulnerability to [email protected], in compliance with the disclosure requirements above.
  • Provide sufficient information to enable our engineers to reproduce and fix the vulnerability.
  • Not engage in any unlawful conduct when disclosing the bug to [email protected], including through threats, demands or any other coercive tactics.
  • Not exploit the vulnerability in any way, including through making it public or by obtaining a profit (other than a reward under this Program).
  • Make a good faith effort to avoid privacy violations, destruction of data, interruption or degradation of Kwikswap.
  • Submit only one vulnerability per submission, unless you need to chain vulnerabilities to provide impact regarding any of the vulnerabilities.
  • Not submit a vulnerability caused by an underlying issue that is the same as an issue on which a reward has been paid under this Program.
  • Be at least 18 years of age.
  • Not be subject to US sanctions or reside in a US-embargoed country.
  • Not be one of our current or former employees, vendors, or contractors or an employee of any of those vendors or contractors.
  • Comply with all the eligibility requirements of the Program.

Other Terms

All reward decisions, including eligibility for and amounts of the rewards and the manner in which such rewards will be paid, are made at our sole discretion.

The terms and conditions of this Program may be altered at any time.