How the desk publishes a winner record
A winner record is published only after three checks are complete. First, the partner operator publishes the prize tier. Second, the operator’s confirmation note names the contest, the entry count, and the prize tier. Third, the desk cross-references with the published IPL scorecard for the same fixture window. If any of the three checks fails, the record is held in pending status. We do not publish speculative entries.
This week’s verified entries
| Handle | Prize | Contest | Week | Status |
|---|---|---|---|---|
| @northblock_no.7 | ₹2,40,000 | SL · 247 entries | Wk 12 — Finals window | Verified |
| @spin-doctors | ₹1,80,000 | GL · 612 entries | Wk 11 | Verified |
| @dewy-evening | ₹95,000 | H2H | Wk 11 | Verified |
| @openers-anonymous | ₹52,000 | SL · 99 entries | Wk 10 | Verified |
| @death-over-physics | ₹28,000 | SL · 500 entries | Wk 10 | Verified |
| @top-3-skip-the-cap | ₹18,500 | GL · 1,243 entries | Wk 09 | Verified |
What the desk does NOT publish
Speculative leaderboards, “best-of” compilations without partner operator confirmation, and any record that the operator has not finalised. We also do not publish operator-internal names or contact details. The ledger is read-only — it is for buyers to verify the contest product, not a marketing tool.
A note on contest formats
The ledger mixes three contest formats. SL (small league, up to ~1,000 entries) rewards consistency. GL (grand league, above ~5,000 entries) rewards variance. H2H (head-to-head) is a daily challenge between two line-ups. Each format rewards a different captain frame; cross-format comparisons are not meaningful.
How often the ledger updates
The desk publishes one update per week during the IPL season, on the Friday after the previous week’s fixtures close. Each update lists the previous week’s verified winners. During the off-season, the ledger is paused.
The ledger’s working rhythm
The ledger updates once a week during the IPL season, on the Friday after the previous week’s fixtures close. Each update lists the previous week’s verified winners. During the off-season, the ledger is paused. The desk does not back-fill or estimate; it only publishes a verified record.
Reading contest-format differences
SL, GL and H2H are three different products. SL rewards a steady XI shape with low captaincy variance. GL rewards the differential captain. H2H rewards the role matchup of two lineups facing the same fixture. Cross-format comparisons between records are not meaningful.
Prize tier clarification
Prize tiers are published only after the partner operator confirms the payout. The verification reviewer cross-references with the published IPL scorecard for the same fixture window. Records that cannot be verified are held in pending status and never published speculatively.
Contest discipline — the desk’s view
The desk publishes the ledger to help buyers verify contest products. It is not a leaderboard and not a marketing tool. The reader is expected to make their own contest choices; the ledger is a record of the most recent verified winners, not a forecast.
The ledger’s purpose
The ledger publishes verified winners to help buyers verify the contest product. It is not a marketing tool; it is not a contest-recommendation engine. The ledger’s only job is to record who won, when, and at what tier, with verification dates.
The verification pathway
The verification pathway has three steps. First, the partner operator publishes the prize tier. Second, the partner operator’s confirmation note names the contest, the entry count, and the prize tier. Third, the desk cross-references with the published IPL scorecard for the same fixture window. If any step fails, the record is held in pending status.
The ledger’s limits
The ledger does not include taxes withheld, charges applied, or payout-fee adjustments. The ledger records the published prize tier only. The desk recommends reading the partner operator’s published terms for the full payout picture.
Why the desk publishes the ledger
To provide buyers with a public record. To provide partners with a verification record. To provide the desk with a continuity record across seasons. The ledger is part of the editorial product; it is read by buyers and partners alike.
The ledger update window
The ledger updates once a week during the IPL season, on the Friday after the previous week’s fixtures close. Each update lists the previous week’s verified winners. During the off-season, the ledger is paused.
The no-fabricated-record rule
The desk never publishes a record that the partner operator has not confirmed. Speculative leaderboards are not published. Back-filled records are not published. Pending records are not published. The ledger is a verified record only.
How the ledger supports buyers
The ledger helps buyers verify the contest product. It is not a marketing tool. It is not a contest-recommendation engine. The reader uses the ledger to verify the partner operator’s published contest structure.
The desk’s ledger discipline
The ledger updates once a week during the IPL season, on the Friday after the previous week’s fixtures close. Each update lists the previous week’s verified winners. The desk never publishes speculative records.
The desk’s policy on the ledger
The desk publishes the ledger as editorial reference. The desk never publishes speculative records. The ledger supports buyers by providing a verified record; it does not recommend contests.
The desk’s ledger reading
The desk publishes the ledger as editorial reference. The ledger updates once a week during the IPL season, on the Friday after the previous week’s fixtures close. The desk never publishes speculative records.
The desk’s no-fabrication policy
The desk never publishes a record that the partner operator has not confirmed. Speculative leaderboards are not published. Back-filled records are not published. Pending records are not published.
How the ledger supports buyers
The ledger helps buyers verify the contest product. It is not a marketing tool. It is not a contest-recommendation engine. The reader uses the ledger to verify the partner operator’s published contest structure.
The desk’s policy on the ledger
The desk publishes verified records only. The desk never publishes a record that the partner operator has not confirmed in writing. The ledger is the desk’s editorial reference for the contest product.
The ledger policy in detail
The desk publishes the ledger as editorial reference. The ledger updates once a week during the IPL season, on the Friday after the previous week’s fixtures close. Each update lists the previous week’s verified winners. The desk never publishes speculative records.
The verification pathway in detail
The verification pathway has three steps. First, the partner operator publishes the prize tier. Second, the partner operator’s confirmation note names the contest, the entry count, and the prize tier. Third, the desk cross-references with the published IPL scorecard for the same fixture window. If any step fails, the record is held in pending status.
How to interpret the ledger
The ledger records who won, when, and at what tier, with verification dates. The ledger does not include taxes withheld, charges applied, or payout-fee adjustments. The reader uses the ledger to verify the partner operator’s published contest structure.
What the ledger does not cover
The ledger does not cover responsible play — that lives at /responsible-play/. The ledger does not cover jurisdiction — that lives at /is-it-legal/. The ledger is editorial reference for the contest product.
