bust.fun admin

Checks each game is paying out the right amount. Use this if you suspect a game is paying out too much — a wrong payout setting or someone exploiting it.

—

Payout rate = money returned to players ÷ money staked, over finished rounds. A row flagged ABOVE EDGE is paying out more than it should over enough rounds — a wrong payout setting or an exploit. House take = money staked − money returned (what the house keeps).

An early-warning check: re-computes each game's expected payout rate straight from its payout settings (it never looks at real bets). A FAIL means a payout setting is wrong — halt the game and investigate.

—

Players the fraud detection has flagged. Use this to review suspicious accounts and freeze (hold) or unfreeze (release) them. Higher score = more suspicious.

Every player who is not in good standing, most suspicious first (frozen players at the top). Freeze or unfreeze right from the row, open the full drill-down with View, or mark reviewed to dim a row you've cleared so the queue visibly shrinks. The fraud checks update this list automatically.

Players who are getting back noticeably more than the house edge allows over enough finished rounds — a possible exploit or collusion. Payout rate is shown as a percentage (100% = break-even).

A permanent, time-stamped record of every fraud signal, with the evidence (what tripped the rule). No sensitive data is shown here.

Compliance cases opened automatically when a player trips a sanctions, location, or screening check. View-only here — cases are worked and closed in the compliance workflow.

Cases opened by the sanctions, location and identity-screening checks. View-only; only the player id is shown (no personal details). Default view hides closed cases so the live queue stays visible.

The money picture: profit, deposits coming in, and withdrawals going out. Use this for your daily and weekly money reporting.

Gross profit = money staked − money returned to players. Net profit = gross profit minus the cost of bonuses, promos and referral payouts. This is the number that tells you if the business is making money.

—

When a player deposits a non-USDC token we automatically convert it to USDC before crediting their balance. A stuck or failed conversion is money we received but haven't credited yet — clear these. "Received" is the token deposited; "credited as USDC" is what actually reached the balance.

Look up any player to see their balance, identity-check level and account standing. Open a player to freeze (hold) or unfreeze their account.

Shows only what staff need — no email or personal details. ("Identity check" is the player's verification level; "wagered" is their lifetime amount bet.)

Player cash-outs waiting for a second person to approve before the money is sent. Review each one, then Approve or Reject. You can't approve your own cash-out.

You can't approve your own cash-out — a second, different staff member must approve it. The risk context column shows the player's identity-check level and standing; use view player to open the full drill-down before approving real funds.

Cash-outs that couldn't be sent after several tries. These need a closer look.

Set how much players can withdraw — per coin, and per identity-check level. Use this to raise or lower cash-out limits. Changes apply to every cash-out from then on.

Set limits in whole coins (e.g. 0.05 SOL, 25 USDC) — the console converts to the blockchain's raw smallest-unit and shows you the exact value before you save, so a stray zero can't slip through. Leave a box blank to keep its current value. To remove a cap on purpose, tick its No limit box — uncapping is never a blank box or a typed keyword. "Hold for manual approval above" is the amount over which a cash-out is held for review. The table below shows every cap in both whole coins and the raw unit.

Click a row to load it into the form below for editing.

Daily limits are safe even when a player fires off many cash-outs at once — they can never slip two past the same daily limit. Setting a limit only controls what's allowed; it never moves any money by itself.

The most a single round can pay out, per verification level. Any bet whose potential win would exceed this cap is blocked or clamped, so no one round can drain the house. This is the same figure the games read to cap their payout. When no row is set, the built-in safe default applies. Enter the cap in whole dollars (e.g. 50000 for $50,000) — the console shows you the exact raw value before you save. default is the level that applies to every player today; the numbered levels are pre-set for when identity tiers go live.

Click a row to load it into the form below for editing.

Create player rewards: bonuses, tournaments, races, promo codes and mystery boxes. Bonus money is locked until the player meets the play-through requirement, so it can't be cashed out straight away.

Creating a promo code or mystery box only sets it up — no money moves yet. The reward is given (and locked until the play-through is met) when a player actually redeems the code or opens the box. The bonus, tournament and race forms above give their reward right away.

The site's emergency controls and safety checks. Stop or restart withdrawals, turn compliance checks on or off, watch the safety monitors, and read the record of every staff action.

—

These are the on/off switches for optional site features — things like the live win feed, the Missions panel, or a redesigned lobby. Pick a feature from the list to see whether it's on, and turn it on or off. Some features can be shown to only a share of players (a gradual rollout). These switches only change what players see — they can never move money, change a balance, or bypass a server rule. Every change is recorded with your name.

A live feed of the most recent things happening on the site. Handy for spot-checking that activity is flowing and nothing looks off.

—

Running totals of site activity — bets, amounts wagered and paid out, active players and any errors. A quick pulse-check on how busy and healthy the site is.

—

How many players saw each version of a running A/B test (the original vs. the new version). Compare the two to see which performs better. This is activity tracking only — no money involved.

Create extra staff roles (for support / moderators) and choose what each one can do — but only from a small, safe set of view/support powers. Built-in roles are set in code and shown here read-only. Nothing here can grant access to move money or change another role's powers; the server enforces that.

Built-in roles (top) are read-only. Custom roles (below) are editable for the safe columns only; the 🔒 columns are code-only and locked for every row.

Look up a player by their numeric id, then add or remove roles. Most changes take effect immediately and are recorded in the audit log. Granting admin or super-admin is a two-person action — it creates a request that a second super-admin must approve above. You can't remove the last remaining super-admin.

Endpoint-scanning and credential-spray signals observed across the API. This is intelligence only — nothing here blocks or bans anyone. Use it to spot a scanner or a burst of failed logins, then investigate the attributed player (if any) under Players.

Live (recent observations)

Recorded signals