pre-deployment
Final pre-deployment - Bug hunt and Rewards trading game
From Fri 29th April until Thu May the 4th 10 am UTC, we will be running a trading and rewards game as well as bug hunting incentive on Validator testnet.
The games will be divided into two parts, one linked to rewards and trading and the other linked to finding bugs.
Important to note, just as during the Bonus rounds we will be performing another async upgrade during the incentive.
Bug hunting
We have set up the Bughunting program to enhance the deployment process by detecting any additional bugs before the final 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.
In scope
Front End:
Core:
Out of scope
Reward structure
| Trivial | Minor | Major | Critical | |
|---|---|---|---|---|
| Core | 20 $VEGA* | 100 $VEGA** | 300 $VEGA | 500 $VEGA |
| Front End | 20 $VEGA* | 50 $VEGA** | 150 $VEGA | 250 $VEGA |
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.
Reward pools and PNL
Rewards and PNL is divided into 3 parts, one linked to best PNL, one to Maker Fees Paid reward pool and the third Maker Fees Received reward pool. The reward pools for ETH/USD and BTC/USD market will be of the same size.
PNL: The users with the best PNL on ETH/USD and/or BTC/USD market
Maker Fees Paid: Users which has received the most reward from the reward pool linked to maker fees paid on ETH/USD and/or BTC/USD market.
Maker Fees Received: Users which has received the most reward from the reward pool linked to maker fees paid on ETH/USD and/or BTC/USD market.
You can find the current active reward pools in the reward section.
Trading funds: Each epoch, you will receive funds on your account. The current epoch and time until next one can be tracked here.
Reward structure
The following is the reward structure for the trading and reward games, 1500 $VEGA in total.
Best PNL Reward
| Position | User | Rewards |
| 1 | 70 VEGA | |
| 2 | 50 VEGA | |
| 3 | 40 VEGA | |
| 4 | 30 VEGA | |
| 5 | 25 VEGA | |
| 6 | 20 VEGA | |
| 7 | 20 VEGA | |
| 8 | 20 VEGA | |
| 9 | 20 VEGA | |
| 10 | 20 VEGA | |
| 11 | 20 VEGA | |
| 12 | 20 VEGA | |
| 13 | 20 VEGA | |
| 14 | 20 VEGA | |
| 15 | 20 VEGA | |
| 16 | 20 VEGA | |
| 17 | 20 VEGA | |
| 18 | 15 VEGA | |
| 19 | 15 VEGA | |
| 20 | 15 VEGA |
Maker fees paid reward pool
| Position | User | Rewards |
| 1 | 70 VEGA | |
| 2 | 50 VEGA | |
| 3 | 40 VEGA | |
| 4 | 30 VEGA | |
| 5 | 25 VEGA | |
| 6 | 20 VEGA | |
| 7 | 20 VEGA | |
| 8 | 20 VEGA | |
| 9 | 20 VEGA | |
| 10 | 20 VEGA | |
| 11 | 20 VEGA | |
| 12 | 20 VEGA | |
| 13 | 20 VEGA | |
| 14 | 20 VEGA | |
| 15 | 20 VEGA | |
| 16 | 20 VEGA | |
| 17 | 20 VEGA | |
| 18 | 15 VEGA | |
| 19 | 15 VEGA | |
| 20 | 15 VEGA |
Maker Fees received Reward pool
| Position | User | Rewards |
| 1 | 70 VEGA | |
| 2 | 50 VEGA | |
| 3 | 40 VEGA | |
| 4 | 30 VEGA | |
| 5 | 25 VEGA | |
| 6 | 20 VEGA | |
| 7 | 20 VEGA | |
| 8 | 20 VEGA | |
| 9 | 20 VEGA | |
| 10 | 20 VEGA | |
| 11 | 20 VEGA | |
| 12 | 20 VEGA | |
| 13 | 20 VEGA | |
| 14 | 20 VEGA | |
| 15 | 20 VEGA | |
| 16 | 20 VEGA | |
| 17 | 20 VEGA | |
| 18 | 15 VEGA | |
| 19 | 15 VEGA | |
| 20 | 15 VEGA |
How to participate in the incentive games
- Go through the registration for Mainnet Simulations 4 here.
- Start trading on BTC/USD and or ETH/USD market on Validator testnet using the Console, API and/or register bugs.
- End up at the top of one or more leaderboards in order to collect your reward!
Users that did not apply for Mainnet Simulations 1,2,3,4 and/or Bonus:
All participants
Please note that the following instruction is for testnet only! If you are using a local CLI wallet, you are required to run version v0.70.0 or later, as for the Vega Wallet Desktop app v0.10.0 or later is required. You can download the appropriate wallet by following these instructions.
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
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.
HOW TO CLAIM YOUR TOKENS
After 31st May 2023, winners will be able to get a token claim link by logging onto the token rewards website with the Twitter account used to register for Fairground Incentives (this is the Twitter handle on the list above). You will be asked to confirm your country of residence - unfortunately, those in restricted countries will not be able to claim tokens.
This is a unique, one time use link, and not specific to any individual so it can be used by anyone to claim tokens. Please treat it with the same security as you would a token. Unfortunately, Vega cannot rectify any mistakes, lost links, or links that have already been used. You know the drill!
All tokens have a linear vesting. All tokens, either locked or vested, can be staked on the Vega network once it is live.
Further information
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.
Rules
- Breaking things is encouraged! Tell us how you broke them and we may give you a tip if it’s found to be a critical bug. Demonstrate exactly how to reproduce it here. Include screenshots/code snippets in as much detail as possible to be eligible for a tip.
- The Vega project reserves the right to not reward participants that are not participating in the community spirit of the incentive programs i.e. botting to collect as many rewards as possible or using an exploit to win an incentive.
- In the event of unforeseen issues and/or a network crash (or essential reset) we will either restart the event OR track and reward those that participated successfully. The course of action will depend on the unforeseen issue. If you miss out, don’t worry, there are many more incentives planned for the coming weeks and months.
- Attempting to create multiple entries by changing twitter handles, having multiple personal accounts, using bot or farmed twitter accounts or by any other means will result in disqualification from this, and any future, incentives.