General participation
Earning CODE is voluntarily! If you don´t want to receive CODE as reward, you can participate in our GitHub repositories as usual.

Everyone who likes to receive CODE as reward, finds here everything he needs to know on how to participate with rewards.

Get Started
First you need a SOLANA wallet to receive CODE as reward.

To participate in the CODE-HIVE discussion channels you will need Telegram.

Reward system

We reward participants for every single line of code they contribute to our projects. Also the finding of minor issues up to security vulnerabilities are rewarded for each line the issue includes.

categories
The CODE-HIVE reward system is split 4 different categories. Each category uses different multiplicators of the BASE-REWAD depending in which category your contribution fits in.
Cat 1 - BASE
The BASE-REWARD is the smallest reward unit, with which all other rewards are calculated. Every new written or changed of line of code will be rewarded with the BASE-REWARD. For example, if you add or change 5 lines of code in our repositorys, you will recieve 5 times the BASE-REWARD.
cat 2 - issues
3 times the BASE-REWARD for each line of code for finding or resolving minor issues in our projects.
cat 3 - security
10 times the BASE-REWARD for each line of code for finding or resolving bugs and security issues in our projects.
cat 4 - Improvement Suggestions
20 times the BASE-REWARD for every suggestion for improvement that we adopt.

Capacitor
The BASE-REWARD distributed through Code-Hive is funded by the assets held within its dedicated fund, called the capacitor.

Fully charged the capacitor holds 50% ( 500 Billion ) of the total CODE token supply.
The base reward depends on the charge of the capacitor and will be cut in half for every 10% the CAPACITOR discharges.
The first halving will occur when the capacitor reserve falls under 450 Billion, the base-reward will then be adjusted to 50K.
500000000000
0% Complete


Projects
All active projects will have a full description on the general goal with tasks for the comunity where the community.
Every project will have his own discussion channels for multiple topics where the community can make improvement sugestions or changes on the overal goal.

basic rules
  • Don´t bloat your code with unnecessary lines, only to get more reward.
  • Don't mix categories in the same pull-request. For example, you cant submit a pull-request where you fix a Security issue and also edited other parts of code, that falls in the base-reward category.
  • Each sentence in text, counts as one line. For example, when you correct 2 typos in one sentence, your will only be rewarded for one line.

Pull reques / commit message
To ensure we properly allocate rewards, your wallet address and additional information should be added to every commit / pull request message.

The additional information for a commit/pull request message should include the category your code fits into, a username of your choice (optional), and your wallet address.

Example with and without a username.

CAT-1 : Usename : code9cedRiGiTNoVFsoSzx3BPGzy1y9okxBnQC1qeTNi

CAT-1 : code9cedRiGiTNoVFsoSzx3BPGzy1y9okxBnQC1qeTNi