Rewarding Interval!

Until Tue 14th May 2 pm UTC, we will be running the Rewarding Interval trading games on our Fairground testnet. Rewarding Interval, as the name suggests, involves trading to earn rewards that are setup as intervals, what this means is that a reward is not necessarily paid out every epoch but instead could be paid out every 4, 6 or even a hundred epochs, so a trading game could for example run for a week, which we of course do not do for this incentive.

The ranking will be based on the one who ends up with the most rewards. The leaderboard can be found here. Everyone will be required to use the latest browser wallet and create their own solo team on Fairground.

There is also a BugHunt live during the incentive, find out more at the end of the page.

In order to qualify for the incentive, you will need to retweet the incentive tweet, use the browser wallet and have your own Lone Wolf team.

You will also need to create an alias for your public key

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: 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 end of May, 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.