B$D

RECEIPTS OVER REPUTATION

What “verified” earns.

A badge is earned by the record. It isn’t something you type into a bio.

  1. Before kickoff

    Only picks posted on BSD before every event’s scheduled start count. BSD uses its server clock and the feed’s kickoff time, never the capper’s clock.

  2. Locked at post

    A posted pick cannot be edited. Removing it keeps the pick and its result in the record, labelled “deleted after posting.”

  3. BSD settles it

    Only BSD’s results feed supplies wins, losses, pushes and voids. Self-reported History results never qualify. Moderation cannot wipe a settled loss from this record. Any future results-feed correction must keep a before-and-after audit.

  4. The price at post

    The record stores BSD’s available feed prices in the minute of publication. A claimed price better than the best available line is capped at that line. Without fresh server evidence the pick is shown as unverified and the badge stays off.

  5. The units at post

    Each pick carries 0.5–5u, locked when posted. Choose 0.5–5u for your next Tail pick in the partner desk. Each following pick defaults to 1u. Profit or loss uses that risk and the captured price; ROI is units won divided by units risked.

  6. Both sides count

    Opposite sides count independently. Linked accounts do not get to net one pick away or pick a winner after the game.

  7. 25 settled picks

    Under 25 settled picks, the page says “Tracking” and provides no record bio line. A badge also requires complete evidence for every counted pick.

  8. Two different labels

    “Verified on BSD” certifies these record rules. “Book-verified” requires an exact match to a synced sportsbook bet for every counted pick. An account-level synced badge is not that proof. Until exact matches are available, BSD does not issue this label.

  9. All-time means all-time

    The window starts with the first BSD pick, not a date picked by the capper. Older picks remain visible. Missing historic deletion or price evidence prevents retrospective verification; BSD never silently resets a capper’s record.