There are some services that we would like to outsource to the community in order to bring value to the ecosystem. We could build a lot of these ourselves, but there is a lot of talent within the Blockchain developer community we can utilize. All of the services listed will be third party, as in, they provide value to the end user. These will not affect the daily operation of the Qtum decentralized Blockchain in any way.

Any work submitted must be open sourced, public, and be open sourced. There must always be an emphasis on supporting Qtum Decentralized Applications, as in, each service should have an area for them to promote their brand. Participants in this bounty program may run 1 advertisement on their site (unless otherwise specified), anything above that will make them ineligible for payment.

This blog post will become a living document, as in, people who claim bounties will have their alias (or real identity)published here. Anyone wishing to claim a bounty must prove they are capable of doing so. Ownership of a Github/Bitbucket is good enough, but if that is not possible, please get in touch with us.

Bounty participants must prove they are competent system’s administrators. These services must be hosted on elastic servers, capable of 2000 daily visits minimum. If a service becomes very popular, and requires a server/VPS costing more than $20.00 per month, you may host 1 additional banner to cover these costs.

Incumbent Qtum service providers may claim bounties. This means if you have already developed a service for Qtum listed on this document, you must expand the functionality above and beyond what is listed here to be eligible for payment. For example, if you already host a block explorer, you must create custom functionality in addition to what you have already hosted to receive payment.

Payments will be made monthly, over a period of 5 months. Participants will receive 20% owed to them each month, provided the service maintains the requirements. Due dates will be 30 days after claiming the bounty, the Qtum nodes are required within 14 days. Payments are only made if the product is delivered, no exceptions allowed. Each month, the participant must coordinate with the bounty manager to receive payment.

To claim a bounty, please leave a comment on this Medium post. You will need to join the Qtum Discord channel to discuss it with a staff member. We will use this document to keep track of progress.

Block Explorers

Block Explorers, 3

125 Qtum Reward

Focus on transparency

Statistics for number of wallets created daily, weekly, etc

Explorer should try to identify large wallet owners, IE Qtum Foundation, exchanges, etc.

Transaction tracking tools, for tracing purposes

Full Qtum QRC20 token statistics

Qtum and QRC20 price information

List of smart contracts, with additional information

Section for QRC20 DAPPs to advertise their projects

Staking statistics

Staking calculator

Each new feature that is not listed here is eligible for an additional 15 Qtum. Maximum 5 features.

Can be based on an existing open source codebase, but cannot be a simple installation with the logo changed. Participants must give credit to the software author if they make use of an existing codebase. Failure to do so will make the participant forfeit any payment due.

Mempool Statistics

QtumMarketCap

1 Required

75 Qtum

Features similar to Coinmarketcap

Must list all QRC20 projects

1 banner advertisement allowed for non-Qtum related material.

Must include extensive information for QRC20 projects, including an option for them to edit this section. Top banner must be reserved for QRC20 projects, price must be reasonable.

Must aggregate social media updates. This should include: Facebook, Twitter, and Reddit. Links must be provided for social media channels, such as Slack, Wechat, Kakaotalk, Telegram, Line, and Discord.

Additional 50 Qtum bonus for Android mobile application, and 50 extra for Apple. Must be accepted to be eligible for payment, we cannot pay for work submitted but not published on these marketplaces.

Paper Wallet Generator:

2 Required

25 Qtum, +5 Qtum per additional Base64 image, up to 5 images maximum.

May use existing open source repositories. Does not have to be custom.

Design of images must be unique, must not be publicly available.

Documentation must be included.

Must allow Qtum QRC20 projects to submit a Base64 image

1 banner for non-Qtum related advertising is allowed, but an additional banner advertisement must be reserved for QRC20 projects. Price for QRC20 projects must be reasonable.

Must function offline, and will be subject to Qtum team security review

Qtum Community Portal

Availability Depends on Language

Limit 7

100 Qtum

Requires multiple sections.

News section, to aggregate all press articles, sorted by date. Requires a small translation to explain what the article is talking about for each publication.

Comments section. Does not have to be a full forum, but should be moderated for spam, etc.

Updates section, for cross-posting Qtum blog posts.

Qtum QRC20 DAPP section. Must explain details of each Qtum DAPP. Requires a login for each DAPP to modify this information.

Maximum 1 non-Qtum related banner advertisement allowed.

1 advertisement spot must be reserved for Qtum QRC20 DAPPs, available at a reasonable price.

Cannot be a simple existing Wordpress template, or forum software installation.

Cannot claim to be an official Qtum source, must emphasis it is community operated.

Cannot have 2 for the same ‘society’. As in, there cannot be 2 from Holland, but there can be 2 in Europe. Languages must be different for each participant.

Qtum Telegram to Discord Relay Bot

1 Required

50 Qtum

Application designed to relay conversations from Qtum Telegram channels to our Discord.

Must allow multiple channels on Telegram to be relayed to multiple Discord channels. This means Qtum QRC20 projects (Matchpool, CFun, Robin8, INK, Vevue, etc) will have their own channel on Discord.

2 way communication should allow Discord users to communicate to Telegram, and put their name in parenthesis. This means if “Bob” sent a message to Telegram, it would show up as: “QTUM DISCORD RELAY: (BOB) Hello Telegram!

Must be able to relay multiple languages, without formatting issues. Chinese, Korean, and so forth.

There should be one massive channel that everything gets dumped into. Each relayed post should state the Telegram channel it came from, the time, and the message. Color coding of the messages, if possible, would be helpful.

Qtum Raspberry Pi Web Wallet User Interface

2 Required

125 Qtum

Should be accessible only via local area network.

Statistics for staking is required.

Network health icon should be displayed.

Simple field for adding nodes.

Buttons for calling RPC commands, so users can see ‘getinfo’, ‘getstakinginfo’ etc on their panel.

Extensive documentation for new users is required.

Must be built to support Ubuntu latest

Option for users to import their wallet.dat file

Must prompt users to encrypt and back up their wallet before allowing them to use it.

Source code must be well documented.

Must not be announced until approved by Qtum team.

Must be custom built

Qtum Full Nodes

100 Required

5 Qtum