How to verify every official pick from publication to settlement

Picktory's performance record is designed to be checked row by row rather than accepted as a marketing headline. The service keeps fixed 7-day, 30-day, 90-day, season, and all-time windows, including losing periods, and applies the same definitions to league, market, and tipster slices.

The evidence chain has four stages. Publication identifies the event, market, line, selection, tipster, odds, stake, and the publishedAt value stored in the source record. Settlement later adds a final result, profit or loss, and settlement time without treating a pending event as a completed sample. Aggregation applies public formulas to the full selected scope. Audit fields connect each row to a public source and SHA-256 fingerprints.

Recalculate a performance view in six steps

  1. Open Verified Performance, choose a fixed period, and optionally apply league, market, or tipster filters.
  2. Record the as-of date, official-pick count, settled and pending counts, and projectionContentSha256 shown for that bundle.
  3. Open the public JSON link on one settled row and compare event, market, line, selection, odds, and stake.
  4. Compare the row's result, profitLoss, and settledAt fields. PENDING rows must not enter settled calculations.
  5. Sum profitLoss and stake across the selected settled rows, then apply the formulas below.
  6. Check that a negative period remains visible and unavailable CLV is labeled as missing or ambiguous rather than converted to zero.

Published calculation rules

ROI = sum of settled profitLoss divided by sum of settled stake, multiplied by 100. WIN, LOSE, PUSH, VOID, and CANCEL stake is included; PENDING is excluded. Stake and profit or loss are public record units, not realized betting-account returns.

Hit rate = WIN divided by WIN plus LOSE, multiplied by 100. PUSH, VOID, and CANCEL are excluded from this denominator.

Average CLV = the arithmetic mean of available record-level CLV percentages. Same-source, cross-source, and overall coverage remain separately visible. A zero denominator displays as unavailable, not as 0%.

What the integrity fields mean

recordId and identitySha256 identify the stable pick identity. publicationContentSha256 fingerprints the public selection, odds, stake, and source-recorded publishedAt value. settlementContentSha256 fingerprints the later result, profit or loss, and settlement time. contentSha256 covers the complete record. integrity.projectionContentSha256 identifies the canonical core containing the as-of date, periods, slices, records, sources, and forward evidence; it is not a byte-level hash of the whole JSON file.

A hash is a fingerprint for detecting changes to included values, not third-party certification and not proof that an upstream source is independently true. The current public JSON is also not an immutable, versioned correction ledger: a corrected settlement changes the settlement, record, and projection hashes. The source-recorded publishedAt value does not independently prove that every historical pick was published before eventTime. Historical ROI, hit rate, and CLV do not guarantee future results.

Open the raw performance projection · Review settled history · Review data-source boundaries

Interactive navigation, filters, and richer tables become available after JavaScript loads, but this summary preserves the core route context.

Privacy Policy · Terms · Contact · About · Methodology · Data Sources · Editorial Policy · Responsible Use · Today's Picks · History · Help

How to verify every official pick from publication to settlement

Picktory's performance record is designed to be checked row by row rather than accepted as a marketing headline. The service keeps fixed 7-day, 30-day, 90-day, season, and all-time windows, including losing periods, and applies the same definitions to league, market, and tipster slices.

The evidence chain has four stages. Publication identifies the event, market, line, selection, tipster, odds, stake, and the publishedAt value stored in the source record. Settlement later adds a final result, profit or loss, and settlement time without treating a pending event as a completed sample. Aggregation applies public formulas to the full selected scope. Audit fields connect each row to a public source and SHA-256 fingerprints.

Recalculate a performance view in six steps

  1. Open Verified Performance, choose a fixed period, and optionally apply league, market, or tipster filters.
  2. Record the as-of date, official-pick count, settled and pending counts, and projectionContentSha256 shown for that bundle.
  3. Open the public JSON link on one settled row and compare event, market, line, selection, odds, and stake.
  4. Compare the row's result, profitLoss, and settledAt fields. PENDING rows must not enter settled calculations.
  5. Sum profitLoss and stake across the selected settled rows, then apply the formulas below.
  6. Check that a negative period remains visible and unavailable CLV is labeled as missing or ambiguous rather than converted to zero.

Published calculation rules

ROI = sum of settled profitLoss divided by sum of settled stake, multiplied by 100. WIN, LOSE, PUSH, VOID, and CANCEL stake is included; PENDING is excluded. Stake and profit or loss are public record units, not realized betting-account returns.

Hit rate = WIN divided by WIN plus LOSE, multiplied by 100. PUSH, VOID, and CANCEL are excluded from this denominator.

Average CLV = the arithmetic mean of available record-level CLV percentages. Same-source, cross-source, and overall coverage remain separately visible. A zero denominator displays as unavailable, not as 0%.

What the integrity fields mean

recordId and identitySha256 identify the stable pick identity. publicationContentSha256 fingerprints the public selection, odds, stake, and source-recorded publishedAt value. settlementContentSha256 fingerprints the later result, profit or loss, and settlement time. contentSha256 covers the complete record. integrity.projectionContentSha256 identifies the canonical core containing the as-of date, periods, slices, records, sources, and forward evidence; it is not a byte-level hash of the whole JSON file.

A hash is a fingerprint for detecting changes to included values, not third-party certification and not proof that an upstream source is independently true. The current public JSON is also not an immutable, versioned correction ledger: a corrected settlement changes the settlement, record, and projection hashes. The source-recorded publishedAt value does not independently prove that every historical pick was published before eventTime. Historical ROI, hit rate, and CLV do not guarantee future results.

Open the raw performance projection · Review settled history · Review data-source boundaries

More detailed tables, filters, and navigation become available after the interactive app finishes loading.