Skip to main content
Push Protocol
· 3 min read

Push Protocol’s Bug Bounty Program Goes Live!

Cover image of Push Protocol’s Bug Bounty Program Goes Live!

Its official! The Push DAO has ratified the proposal to implement Push Protocol’s Bug Bounty Program🎉

And the program starts TODAY!

How the Program works

The Program is structured to be as streamlined as possible by following just 3 steps:

  • Step 1: Security researchers will submit their findings through the Official Form available here.
  • Step 2: Designated Push Team members will review security vulnerabilities, analyze the report, and classify it according to severity.
  • Step 3: The Push team will follow up with the reporter with results in no more than 1 week.

The program includes 4 levels of severity on its scale:

  • Critical Issues — have a serious and immediate impact in the protocol functioning and could impact numerous users. An example would be preventing notifications and/or chat from being sent, or affectation to fees collected through the protocol.
  • High Issues — pose severe risks to individual users or Push’s partners.
  • Medium Issues — where the risk is relatively small and does not jeopardize users/protocols that interact with Push.
  • Low/Informational Issues — do not pose an immediate risk but are relevant to security best practices.

Rewards will be given based on the classification of the bug’s severity, as well as the likelihood of the bug being triggered or exploited. This is to be determined at the sole discretion of the Push Protocol team.

Eligibility requirements

To be eligible for a reward, you must comply with all the eligibility requirements of the Program outlined below.

  • Discover a previously unreported, unknown, non-public vulnerability to the team which is within the scope of this Program.
  • Be the first to disclose the unique vulnerability — via the form that will be made available after this proposal is ratified, in compliance with the disclosure requirements.
  • Provide sufficient information to enable our engineers to reproduce the vulnerability and fix it.
  • Not exploit the vulnerability in any way. This includes sharing the vulnerability with others and/or by obtaining an additional reward, other than a reward under this Program.
  • Not publicize the vulnerability in any way, other than private reporting to us.
  • Make a good faith effort to avoid privacy violations, destruction of data, interruption or degradation of any of the assets in scope.
  • Not submit a vulnerability caused by an underlying issue that is the same as an issue previously reported and paid out by the Program.
  • Not engage in any unlawful conduct when disclosing the bug. This includes threats, demands, or any other coercive tactics.
  • Be at least 18 years of age. If younger, submit note of the vulnerability along with written consent of your parent or guardian.
  • Not be a current or former Push team member, vendor or contractor who has been involved in the development of the code of the bug in question.
. . .

The Push DAO Bug Bounty Program will be managed in epochs of 3 months (officially starting on day 1 of each quarter).

Fund allocation per epoch may vary according to market conditions. Despite this, Push DAO will always ensure some extent of funding is allocated to sustain rewards for contributors.

This newfound Bug Bounty Program adds to our long string of initiatives that aim to foster and encourage community participation.

We look forward to seeing your contributions and support in making Push as great a protocol as possible!

Got questions?

You can reach out to us through any of our communication channels, however we suggest Discord as the initial point to start conversations and ask questions regarding vulnerabilities found.

You can find us on Discord here.

Thanks again for being a part of what makes Push Protocol incredible!

Be a part of the conversation by sharing this article

About Push Protocol
Push is the communication protocol of web3. Push protocol enables cross-chain notifications and messaging for dapps, wallets, and services tied to wallet addresses in an open, gasless, and platform-agnostic fashion. The open communication layer allows any crypto wallet / frontend to tap into the network and get the communication across.
Twitter
Discord
YouTube
Linkedin

We use cookies to personalize your experience. Learn more in our Privacy Policy.