Lottery Team2!
Until Wed 11th Sep 1:00 PM UTC, we will be running the Lottery Team 2 trading game on our Fairground testnet.
The trading game on the USD-LIQ markets uses the new reward type that is Lottery based as, 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!
For lottery you are ranked for the payout of each in terms of how well you did, e.g. for a relative return reward gives you a higher chance of winning based on your relative return, your ranking increases the chance of you winning the reward payouts. The leaderboard can be found here.
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.36.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.
How to participate in the incentive games
- Follow Vega protocol on twitter. Like and retweet the incentive tweet.
- Unless you have done so before, register using the form! Remember to store your secret passphrase!
- Join Discord and follow the @vegaprotocol Twitter account.
- Create or Join a team!
- Create an alias for your public key
- Use the integrated console wallet
- End up at the top of the collected lottery reward leaderboard in order to collect your reward!
Rewards
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 | a4a01c91f3b78ee94508374650ae0344adc6ba38ba677ade401174b131218d49 | 200 USDT |
| 2 | cf02541d00f0b4eb0a2d9ad0cfedc353457426e43547508033a8623c9fd9ec1a | 150 USDT |
| 3 | 094abf5f71be9b586b13a89ad40d16be9b724d000c237e8ff78c5098f08c0e13 | 125 USDT |
| 4 | 0b39a7df7e479751af8451b9b89c3c2d66b49c14d6f36a10b16f74cacd46a474 | 100 USDT |
| 5 | b511f02da2edc245480f3f67701c356b1f4d9ae6c68db53026ade326e0aa643a | 75 USDT |
| 6 | e0d181011ea609f4a578911e0584f50df1dd16f230a67b4dd10da0a2baa88650 | 75 USDT |
| 7 | ddcdc295ddb6491d30642f1ea1f1e590815a09db654cded6b410559c5ee44159 | 75 USDT |
| 8 | df11fd69608db49e171db62c43c29e0d8dff0983c0f6ec2efffe8ac2bcc081e6 | 50 USDT |
| 9 | 0123fdaaaf53a2949784d77bc0994b82caa0fce70d6beae8f5e8598bf05d9891 | 50 USDT |
| 10 | af03b124d4faff2491a63b02189eaeac81976f2abda55cb68c35f4648d1dc714 | 50 USDT |
| 11 | 3c50cade5e8e8f43d951eefb12551d338900878a175a6c9c5784e03a21e61762 | 50 USDT |
| 12 | fca928c077f801784adcacfd0c702a4ab1366de39437d2ed8b93af6697c6461a | 50 USDT |
| 13 | 6417cf4dca5ceae0beda7913cbb5a2a24f87afc7d54ad88473db7b35dbd4f088 | 50 USDT |
| 14 | 82fc0a86a291ea2ef877f6a72c8ad73ea76c83b8e3a8d60f25dbff2aad5a6d39 | 50 USDT |
| 15 | 4d35f2bb38c512b87138590a1ac34e94bb2d039933ded74cb07693ef68ff6c0e | 50 USDT |
Bug hunting
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.
In scope
Front End:
Core:
Out of scope
Reward structure
| 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
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 REWARD
By the mid of September, 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.
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.