Overview

The Sifchain Bounty Board contains tasks in the form of tickets that are ready to be picked up and executed by anyone in the world. It allows more and more people to get involved in Sifchain-specific engineering work, design work, content creation, marketing, and others, while getting compensated for doing so. If you are willing and able to assist on any ticket in the bounty board, we invite you to take part in helping Sifchain build and prosper into the future.

Available Bounties

• GitHub Link: https://github.com/Sifchain/The-Bounty-Board
  • GitHub will be used for all bounty board tickets. This includes both engineering-specific work and non-engineering-specific bounty work. Some tickets (primarily those involving engineering effort) will be posted in GitCoin as well. Each GitHub ticket will include:
    • Requirements for what needs to be done
    • Indication of whether the ticket is a RFP or a Contest
    • Compensation Information
• GitCoin Bounties: https://gitcoin.co/explorer?network=mainnet&idx_status=open&applicants=ALL&keywords=sifchain&order_by=-web3_created
  • Most engineering-specific bounties will be posted in Sifchain’s public Github Bounty Board (listed above), as well as being listed in GitCoin.

GitHub Overview

• Tickets will have corresponding labels on them. Definitions of these are below:
  • content: This ticket deals with the creation of content (ie: marketing-related information). The type of content desired will be outlined in the ticket.
  • enhancement: This ticket deals with an engineering feature or enhancement.
  • bug: This ticket deals with a bug that needs to be fixed.
  • RFP: This ticket is a Request For Proposal. More details on this below.
  • contest: This ticket is a contest where numerous people can partake in it and winners are chosen.
  • on-hold: This ticket is not ready to be worked yet.
• Ticket statuses:
  • Backlog: Tickets in this status are not ready to be worked yet.
  • Ready For Work: Tickets in this status are ready to be worked. Please read the ticket description & overview to see the requirements, type of ticket (RFP vs. contest), and how to participate.
  • In Progress: Tickets in this status are currently being worked on by one (if RFP) or numerous (if contest) people.
  • Review/QA: Tickets in this status are being reviewed by Sifcore after the initial submission of completion from the user has been made.
  • Done: Tickets in this status have been completed and fully signed off by Sifcore.

Types Of Tickets

• Request For Proposals (RFPs): Tickets that are RFPs are requesting interested parties to submit a proposal to complete the ticket’s requirements. In submitting a proposal a user should do the following:
  • 1. Completely understand the asks of the ticket.
  • 2. Adhere to the RFP eligible date range. This is the date range that users can submit a proposal for review.
  • 3. Submit an RFP as a comment on the ticket. This comment should contain specific details as outlined in the ticket.
  • 4. If the proposal is selected by the Sifcore team, that RFP proposer should begin work.
• Contest: Tickets that are type ‘Contests’ will have contest rules and eligibility requirements attached to the ticket. Contests will have relevant dates, compensation, and criteria for selecting winners in the rules.