Until Tue 27th Aug 1:00 PM UTC, we will be running the Onchain Lottery trading game on our Fairground testnet. Onchain Lottery, is trading on the USD-BW markets and uses the new reward type that is Lottery based, so for users that has participated in incentives before you have noticed that we have added a random factor of tickets for the winners of the incentives, this function is now onchain!
So for each reward setup for this incentive, the better you do the bigger the chance on winning the rewards.
At the payout of each reward you are ranked in terms of how well you did, your ranking increases the chance of you winning the reward payouts. The leaderboard can be found here and the rewards here.
You should be able to track how you are doing on the games on the games page every 10 minutes, make sure to give us feedback.
There is also a BugHunt for the new console integrated wallet during the incentive, in case you have not stored your mnemonic you will have to create a new key and team and transfer your funds to the new address which also requires it's own team.
In order to qualify for the incentive, you will need to retweet the incentive tweet, and have your own Lone Wolf team.
You will also need to create an alias for your public key
Please note that the following instruction is for testnet only! For the Browser wallet you will need to run the latest Browser Wallet v0.26.0 (Chrome (To upgrade you can right click on the extension and choose manage extension and update), Firefox) (To upgrade you can right click on the extension and choose manage extension and check for updates). You can download the appropriate wallet by following these instructions.
The following is the reward structure for the incentive games, 1200 $USDT in total.
The user of the team at the top of the competition leaderboard will win the game! You can create a team here
Winners:
Position | Public key | Rewards |
1 | 663180ee94ce982f005e05633083108e0e5b794b6731da7889f5305d4558a8aa | 175 USDT |
2 | b511f02da2edc245480f3f67701c356b1f4d9ae6c68db53026ade326e0aa643a | 150 USDT |
3 | 37af8917f0cd8d8a5de95b76ae72b99498694436314ca2ee6fb3145a7326d877 | 100 USDT |
4 | d8a216a6b745eb7ea8a04b60215e3500e03b3bfba7af5cc35dca0ef91295b022 | 75 USDT |
5 | 4df8053b28fd69131240f468aa481327585f5f1cadcc2e15413c59240eb5b232 | 75 USDT |
6 | 467dd06cb51b3d37cec8c18f47fe91959480145ba2a37100f05d8c80f746ef65 | 50 USDT |
7 | 5dc8f01d0b0f6c285292a598184f47c8ab71e43d857416402b2a4b09820014ca | 50 USDT |
8 | c80373f144651ebf161c112beb7fa0157d03001d87ebba788e765977bc527378 | 50 USDT |
9 | 386fce3fb2c855c902758f2c641c034be75442ae481124b8289aebf7b0dd322b | 50 USDT |
10 | af03b124d4faff2491a63b02189eaeac81976f2abda55cb68c35f4648d1dc714 | 50 USDT |
11 | da05b142fdc44abd1303dbbb4c31e6b55df5b96663359566016e9bed86ca4798 | 25 USDT |
12 | d009d70da3fb3c1a2283c44fd2561f947ea9c0bc836d870e74dfe0f8dd055ca8 | 25 USDT |
13 | 094abf5f71be9b586b13a89ad40d16be9b724d000c237e8ff78c5098f08c0e13 | 25 USDT |
14 | fb27dbcef7d9bbbc54225eb9a615bb0fc4261bd1b6499deae538be5c099960ed | 25 USDT |
15 | 6417cf4dca5ceae0beda7913cbb5a2a24f87afc7d54ad88473db7b35dbd4f088 | 25 USDT |
16 | ddcdc295ddb6491d30642f1ea1f1e590815a09db654cded6b410559c5ee44159 | 25 USDT |
17 | df11fd69608db49e171db62c43c29e0d8dff0983c0f6ec2efffe8ac2bcc081e6 | 25 USDT |
18 | 7a0a36f85a86ce6c49e7f2e0867e9f035f604b291b87a59a02f582608822aedf | 25 USDT |
19 | 3de066dd18f927c431f3e449572388943f6b3bdfee0dc12738f6867d8ed5614b | 25 USDT |
20 | db6b5e091672675f5bc95b6cecab25820faa4495eb008983c6b02b3962e6ed3d | 25 USDT |
21 | 267baa62a741e73ea37afd17edd606bd2f2f4dd674367ab1e0919c98996399a1 | 25 USDT |
22 | 0b39a7df7e479751af8451b9b89c3c2d66b49c14d6f36a10b16f74cacd46a474 | 25 USDT |
23 | 7b87af8af24b0804f85f75ad7c632c790fd71b4d3dda422eb07432e5925d7e5c | 25 USDT |
24 | f89c42f37469e4cd5c19254fbf37f5288b08d5c59ce0dfb642b17cc3966499c3 | 25 USDT |
25 | 82fc0a86a291ea2ef877f6a72c8ad73ea76c83b8e3a8d60f25dbff2aad5a6d39 | 25 USDT |
We have set up the Bughunting program to enhance the deployment process by detecting any additional bugs before the release. As part of this program, rewards will be given based on the severity of the bug and whether it’s related to the Front End or Core.
It is important to note that in order to qualify for the rewards, the reported bugs must be within the defined scope, unique, reproducible, and recorded in Github discussions. If multiple users report the same bug, we will apply a “first come, first served” approach, and the user who reported it first in the Github discussions will be eligible for the reward. Thank you for your participation in helping us identify and eliminate any potential issues.
Front End:
Core:
Trivial | Minor | Major | Critical | |
---|---|---|---|---|
Core | - $USDT* | 50 $USDT** | 100 $USDT | 150 $USDT |
Front End | - $USDT* | 50 $USDT** | 75 $USDT | 125 $USDT |
Trivial: The defect does not affect functionality or data. It does not even need a workaround. It does not impact productivity or efficiency. It is merely an inconvenience. Example: Petty layout discrepancies, spelling/grammatical errors.
Minor: The defect affects minor functionality or non-critical data. It has an easy workaround. Example: A minor feature that is not functional in one module but the same task is easily doable from another module.
Major: The defect affects major functionality or major data. It has a workaround but is not obvious and is difficult. Example: A feature is not functional from one module but the task is doable if 10 complicated indirect steps are followed in another module/s.
Critical: The defect affects critical functionality or critical data. It does not have a workaround. Example: A feature is not functional from one module but the task is doable if 10 complicated indirect steps are followed in another module/s.
*Maximum number of Trivial paid is 10 Core and 10 Front End each. If we receive over 10 we will raffle 10 winners in each category.
**Maximum number of Minor paid is 5 Core and 5 Front End each. If we receive over 5 we will raffle 5 winners in each Category.
By competing in a lifelike market for a share of the VEGA incentives, you’ll learn about Vega and find out first-hand what it’s like to trade on Vega markets.
In addition to the trading game incentive, we would highly appreciate any bugs or suggestions of improvements to the console to be submitted on github discussions.
The project will also benefit from all the data created, metrics collected, and feedback received, which will help develop and improve the protocol. If we’re really lucky and something goes wrong we might even find and fix some bugs!
Market details will be visible through Console and APIs.
All announcements for this market will be made via the Vega Protocol Twitter account @vegaprotocol so make sure you follow to stay up to date.
By the end of August, winners will be getting their tokens on the vega pubkey they were participating with in the incentive. You can see the tokens by going to the console or the governance website.
All announcements for this incentivised period will be made via the official Fairground Twitter account @VegaFairground so make sure you follow to stay up to date. This includes changes, updates and early closing of the period.
Check out the Incentive Terms and Conditions for information related to all incentives.