SYSTEM ADMIN
โ‡„
/manage/challenges

Challenge board settings Not live yet

The challenge board is fixed, public data: players see exactly the numbers you see here. There are no personalised challenges and no suggestion generated after a player finishes a round. Players reach challenges through one route only โ€” the list page.

Three things on this screen cannot be changed. The reward is a badge or title, never tokens โ€” paying tokens for abstaining would create a loop where people abstain to build a betting bankroll. A challenge ends by itself once the set number of bets is reached, win or lose, and there is no "let them keep going" option. And there is no field for a deadline in hours or minutes, or any other kind of countdown.

Published challenge definitions

+ New challenge
Code Name shown to players Group Bets Win target Reward Share who finish Source of the figure
CH-01 Seven days without a bet Abstaining 0 โ€” Badge "Seven clear days" 41% Estimate hard-coded, nobody has finished one yet Edit CH-01
CH-02 Thirty days without a bet Abstaining 0 โ€” Badge "One month" + profile title 12% Estimate hard-coded, nobody has finished one yet Edit CH-02
CH-05 One weekend without opening the betting screen Abstaining 0 โ€” Badge "One clear weekend" 74% Estimate hard-coded, nobody has finished one yet Edit CH-05
CH-03 Fifty bets, winning 55% or more Long run 50 55% Badge + house edge comparison report 15% Estimate 10,000-run simulation at the expected 47.6% win rate Edit CH-03
CH-04 One hundred bets, winning 65% or more Long run 100 65% Badge + house edge comparison report 0.034% Estimate Exact binomial probability at the expected 47.6% win rate Edit CH-04

Completion rates are recalculated overnight.

Why the completion rate carries an estimate label

This is the number a player looks at before committing, so it works against overconfidence. If we hard-code an estimate early on and say nothing, we are doing exactly what this product exists to argue against: presenting a guess that sounds like data.

So the player screen always shows the Estimate label with the sample size until there are enough real completions. Removing that label is one of the lines on the safety checklist every sprint.

Long-run challenges always carry a reality check

CH-03 and CH-04 are easy to misread as "the app is teaching me how to win". The correction is built in, not optional: when the challenge ends, the report always puts the player's actual win rate next to what the odds predict once the house edge is taken out.

The "house edge comparison report" in the reward column cannot be switched off โ€” it is not a checkbox on this screen.

Who can edit this: content admins and system admins can both read and edit the board, because this is public configuration โ€” anyone can check it against the player's own screen.