Fusion Bug and Content Bounty - DropsEarn
Fusion Bug and Content Bounty

Fusion Bug and Content Bounty

    The Fusion Foundation launched a rewarding event for community members for their contributions to improving Fusion's network and applications. And also for creating helpful and engaging content that helps the community learn and use Fusion apps. Approved content will be added to the Fusion Knowledge Center and shared across Fusion’s Social Channels.

    Reward pool
    Not set
    Expected profit
    $2.5 - 1 250
    Max participants
    Not limited
    DropsEarn score

  • Activity Type: Bug bounty Creativity Content
  • Date: from 1 Sep 2019 06:00(UTC+3)
  • Registration: Open
  • When reward: After approving your application from the Fusion team
  • Event status: You can participate (Event started, Registration open)
  • Links: Official Announcement Main Event Page
Go to event page

Bug Bounty

Fusion has set up a submission form ‘ISSUE_TEMPLATE.md’ that has instructions on how to submit a bug. This form can be found in all of Fusion’s Github repositories. Bug hunters are encouraged to join the Fusion Developers Community Telegram channel to understand current issues that are being worked through and to discuss their contributions. 

Bug Hunting Rules

Any code available in Fusion's Github repositories is fair game for bug bounty rewards.

  • Only reports of improvements/bugs that were unknown to the Fusion team are eligible for rewards.‍
  • Issues that have already been submitted by another user are not eligible for bounty rewards. If there is a duplicate submission of a bug, Fusion will reward the submission that was received first.
  • Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
  • All rights to interpret the severity of a bug or the value of an improvement and determine the reward are reserved to the Fusion Foundation.
  • Social engineering (e.g. phishing, vishing, smishing) is prohibited.‍
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
  • All code added to the github repositories as a pull request or issue is declared to be MIT Licensed and the Fusion Foundation and community have freedom to use, edit, and derive works.

Submission Process

Fusion has set up a submission form ‘ISSUE_TEMPLATE.md’ that has instructions on how to submit a bug. This form can be found in all of Fusion's Github repositories.
Improvement and bug submissions must provide sufficient detail so the Fusion Foundation can readily understand, recreate and measure improvements/bugs. Details may include a description of the fix, a breakdown of an attack scenario, directions on how to reproduce the bug etc. If the report is not detailed enough, the issue will not be eligible for a reward.

  • All new features and bugs can be submitted under the appropriate Github repository.
  • ‍The repository has steps to complete for issues and pull requests in order to submit a new feature or bug.
  • ‍Any follow-up from the Fusion team will be added to the issue, tracker or pull request.
  • ‍In order to be rewarded, you will need to submit a ticket via Fusion's Zendesk. Please use the Subject line “Bug Bounty Rewards” and include a link to your Github profile.


Bug Bounty Reward Matrix 


Content bounty

Submission Process
Please email contentbounty@fusion.org with an outline of your content creation proposal, include the content format (YouTube video, Medium article), content topic, brief description and any other information you think is relevant. 

After submitting a content proposal, please wait for approval from the Fusion team, they will respond directly to the same email address. 

If approved, the Fusion team encourage you to produce the content piece and submit it to the same email address (contentbounty@fusion.org). Upon review and approval, you can share it on your preferred channel.