Vega Bet - Vega Originals Bug Bounty Campaign
Active · Launched 2026-10-26
I am managing Vega Bet’s bug bounty campaign for its Originals. Participants receive a $5 testing promo code to explore the games and provide honest feedback. Reports are submitted privately through the R7 reporting form, with a $50 reward for each developer-confirmed bug.
The client’s goal
Vega Bet wants to identify issues affecting its Originals and understand where the player experience needs improvement. The campaign invites firsthand observations about errors, confusing behaviour and frustrating interactions, giving the development team specific findings to investigate.
The approach
Testing focuses specifically on Vega Originals. Participants explain how to reproduce an issue, what they expected to happen and what actually happened, with screenshots or recordings where useful.
Reports are submitted through a dedicated R7 reporting form rather than published on the forum. This gives the campaign a consistent submission channel while keeping bug details out of public discussion during assessment.
What I managed
I manage campaign communication, participant coordination and the reporting workflow through R7 Promotions. I review submissions for relevant details and coordinate follow-up questions where clarification is needed.
Vega’s developers confirm bugs and assign severity. I coordinate the campaign process around their assessments and the stated reward conditions.
Results and evidence
The campaign is live, with a dedicated R7 form available for private submissions. Its reporting requirements give participants a clear format for documenting issues and give developers the information needed to assess them.
Confirmed bug totals and reward outcomes will be added as testing and verification progress.
Campaign details
Participants are encouraged to speak candidly about their experience, including what worked and what needs attention. A favourable opinion is not a condition of participation.
General feedback helps explain the experience surrounding an issue, while the $50 bounty applies specifically to confirmed bugs. The private reporting process supports that distinction without requiring participants to disclose their findings publicly.