Results and Notifications

How pick records, grading, and alerts work

PickProof attaches authoritative grades to immutable Confirmed Picks, then calculates records from those graded entries. Alerts help users follow changes, but delivery is a best-effort convenience rather than part of the ledger itself.

Grades follow the recorded market

A grade evaluates the confirmed selection using the authoritative final event result and the rules for that market. Common outcomes can include win, loss, push, void, or pending. The original selection, line, odds, units, timestamp, and visibility remain unchanged when the grade is attached.

Postponed, canceled, suspended, and corrected events require authoritative state. PickProof does not infer a final grade from a partial score or from a display row that merely looks complete.

Corrections preserve ledger integrity

Scores and event mappings can be corrected after an initial update. If authoritative information changes, PickProof can revise the grade and the resulting record. That correction is different from editing the pick: the confirmed entry stays fixed while the outcome attached to it is corrected.

Public and private records remain separate

Public records use public-eligible, graded picks under backend rules. Private picks remain excluded from public feeds, rankings, badges, and public record calculations. Users need graded public picks to appear in leaderboard rankings.

Blocked-user filtering and reveal schedules also remain backend-controlled. A client display cannot make an ineligible or private entry part of a public record.

ROI and units are historical analytics

Unit results and ROI summarize informational ledger fields across graded entries. They do not represent an account balance, money held by PickProof, or funds available to deposit or withdraw. Different sample sizes and market mixes can make records look similar while representing very different histories.

Alerts are best effort

PickProof can provide score, game-state, followed-user, pick, or product alerts when the feature is available and enabled. Delivery may depend on device settings, permissions, network availability, provider status, event mapping, and data timing.

An alert can be delayed, duplicated, corrected, or unavailable. It should not be treated as the sole source of an event's status or as an instruction to take action outside PickProof.

Reading a record well

Consider the number of graded public picks, market types, time range, visibility rules, pushes and voids, and any data corrections. A compact summary is useful, but the underlying immutable entries and verification history provide the fuller context.