Acala Network Reward Program

Rules & Rewards  (season 2)

Node Runners (11th - 31st May)

Prize

• Total: 1575 ACA + 107,100 KAR
• Each Prize: 25 ACA + 1,700 KAR
• Prize draw at UTC 00:00, 3 prizes each day

Rules

• Run a Mandala TC3 Node, follow this guide & check telemetry here
• Remember to run your node with --name parameter plus first 10 characters of your reward receiving address e.g. --name "5DcvxiYpLn"
• Make sure get some test tokens for this address, otherwise it cannot be verified nor be in a draw
   

App Users (11th - 31st May)

Prize

• Total: 6,000 ACA + 300,000 KAR
• Each Prize: 20 ACA + 1,000 KAR
• Prize draw: 100 lucky winners every week for 3 weeks 🎉

Rules Try Acala App and do the following to be in the draw:

1. Use Liquid DOT (LDOT) to get DOT derivative
2. Then use LDOT for any effective transactions including: use Self Service Loan to borrow aUSD with LDOT, or trade on Swap exchange, or Deposit & Earn, or participate in collateral auctionsetc. excluding transfers.
3. Get started here
    

Bloggers (till 15th June)

Prize

• Total: 2,000 ACA + 150,000 KAR
• Each Prize: 200 ACA + 15,000 KAR
• Total 10 bloggers awards will be announced a week after 15th June.

Rules

• Original blog post submitted to Medium or Bihu
• Remember to include your Acala Mandala Address in the article to receive prizes
• Submit the article link to https://riot.im/app/#/room/#acala:matrix.org with keyword CANDY_BLOG
• The blog must be original.
• We will judge both the quality (how appealing is the story, idea, perspective, insights, analysis etc) as well as social reactions (number of comments, likes, twitter or other social sharing etc).
   

Runtime Bug Hunters

ELIGIBILITY Help identify bugs in Acala mainly for this repo https://github.com/AcalaNetwork/Acala.

Generally, a bug that poses significant vulnerability or causing systemic defects would be eligible.

1. Open an issue in Github, provide as much information as you can, including a description of the bug, its potential impact, steps for reproducing it
2. Include your Acala Mandala Address for prize giving in the Github issue
3. Submit the issue to Acala Riot Channel with keyword CANDY_RUNTIME_BUG

PRIZE Total Prize Pool: 66,666 ACA and 3,333,300 KAR, and Acala reserves the right to extend it further.

Bugs are judged on significance and severity by the Acala Engineering team, and are awarded based roughly on the levels below:

• Level A (2,000 ACA + 100,000 KAR): significant logic and process volunerability; sensitive or highly probably to create significant impacts to the system
• Level B (1,000 ACA + 50,000KAR): intermediate logic and process volunerability
• Level C (300 ACA + 15,000 KAR): mild vulnerability or bugs that interrupts or breaks system expected operation

PRIZE GIVING

1. Please allow 1 week upon submission for review.
2. Prize tokens will be dropped to the address provided in the issue submitted.

UI Bug Hunters

ELIGIBILITY Help identify bugs in Acala mainly for this repo https://github.com/AcalaNetwork/honzon-platform

Generally, a bug that poses significant vulnerability or causing systemic defects would be eligible.

1. Open an issue in Github, provide as much information as you can, including a description of the bug, its potential impact, steps for reproducing it
2. Include your Acala Mandala Address for prize giving in the Github issue
3. Submit to the Acala Riot Channel with keyword CANDY_UI_BUG

PRIZE Total Prize Pool: 6 2,000 ACA and 100,000 KAR, and Acala reserves the right to extend it further.

Bugs are judged on significance and severity by the Acala Engineering team, and are awarded based roughly on the levels below:

• Level A (1,000 ACA + 50,000 KAR): significant logic and process volunerability; sensitive or highly probably to create significant impacts to the system.
• Level B (200 ACA + 10,000KAR): intermediate logic and process volunerability.
• Level C (80 ACA + 4,000 KAR): mild vulnerability or bugs that interrupts or breaks system expected operation.

PRIZE GIVING

1. Please allow 1 week upon submission for review.
2. Prize tokens will be dropped to the address provided in bug submission.