Methodology
How every number here is computed
Every ACTIVE site the operator claims daily (15), the top sites by best reported $/SC from the 2026-09-12 research, and the top DailyCashList casinos by DCL rank (2026-10-18 snapshot) that have a resolved home URL. DailyCashList-sourced rows carry third-party-reported daily values, labelled as such, an unverified reset rule and a homepage CLAIM link until the daily-bonus path is observed. Unknown values are null and render as 'varies' or 'see site' — a null is never filled with a guess.
The math
The $/SC figure is the reported pack price in USD ÷ nominal redeemable SC yielded — a pack's price per SC coin. It is not an expected value: playthrough, game RTP, and whether you actually reach redemption are not netted in (playthrough is noted separately on each site page). 1 SC ≈ $1 redeemable; GC/CC/FC/PE are non-redeemable play coins (Fortune Coins FC converts ~100 FC = 1 SC-equivalent; Funrize PE converts 100:1). Where a pack has a promo code that changes the yield, the coded yield is the number shown. Where sources give a range, the range is shown — not just the flattering end, and no midpoint is invented. Rankings on this site use the conservative (weaker) end of the range, so an unverified best-case never outranks a solid number.
Sources
- mira/substrate/lanes/side_hustle/strategy/site_inventory.yaml (2026-08-03 provider refresh + 2026-09-13 activations)
- mira/artifacts/sidehustle/research/2026-09-12_pack_ev_live.md (pack EV + signup freebies, all web sources accessed 2026-09-12)
- mira/artifacts/sidehustle/research/dcl_118.json + dcl_new_62.json (DailyCashList snapshot 2026-10-18: listing, third-party-reported daily SC and redeem minimums; resolved home URLs only)
- mira/artifacts/sidehustle/research/dcl_118.json + dcl_new_62.json (DailyCashList dashboard snapshot 2026-10-18, rank order + resolved home URLs)
Evidence classes — how good is each number?
Every pack value carries one of four evidence classes instead of a single overloaded "verified" label:
- VERIFIED — operator_observed. Measured by one of our own on-site passes: a real ClaimChef run observed the pack and its balance delta. This class is reserved — as of 2026-09-14, zero records hold it (0 of 101). The green badge appears only after a real on-site observation, never before.
- PUBLISHED — operator_published (0 of 101 today). The operator's own published pack/price math, captured from an operator-controlled page and cited per record. This class is reserved: a round-2 audit (2026-09-14) found the earlier 22-record PUBLISHED migration overstated provenance — those values trace to affiliate/review reporting and book values — so every one was reclassified to REPORTED. Zero records hold PUBLISHED today.
- REPORTED — third_party_reported (22 today). Affiliate/review-site reporting — including everything from the 2026-09-12 receipt (which is affiliate-source material, not on-site wallet observation), the 22 values briefly labeled PUBLISHED in the round-1 migration, and inventory book values of the same origin.
- UNVERIFIED — unverified (79 today). Single-source, conflicting, or unstated. Shown with a dashed badge, or verify on-site when nothing credible exists. Unverified never becomes marketing copy.
Said plainly: as of 2026-09-14, no operator-origin numbers exist yet — every pack value in the Menu is third_party_reported or weaker, and nothing has been verified by an on-site ClaimChef pass yet. Where a daily bonus shrank or vanished (McLuck 0.8→0.2 SC; Hello Millions' daily SC removed), the page says so — honest staleness beats fake freshness, and every page carries its last-verified date. Where a site's daily SC surface has unproven cash value (Chumba, per the 2026-08-28 owner note), it is rendered as claimed-surface and excluded from redeemable-value totals.
What we don't do
- No fabricated numbers, no invented midpoints, no extrapolated earnings.
- No fake author personas — the lab is the author; receipts are the credential.
- No affiliate links until operator programs are approved and verified (all affiliate_url fields are null today).
Honest ROI — the locked block
Our research estimate, not yet measured by ClaimChef: dailies alone come to roughly $100–250/mo in redeemable SC, and fast drop capture could push that toward $250–500/mo. These are ranges, not promises — sites cut bonuses without notice, and anyone guaranteeing you money in this space is lying to you.
Source: ClaimChef competitor & pack research, 2026-09-12. Replaced with measured ranges only if ClaimChef ever has real, aggregated data. Methodology.
Update log
Initial 30-site build. The Menu table, per-site pages, drop-code placeholders, and this methodology page generated from data/menu.json. No numbers fabricated; unverified rows are labeled.
External audit fixes: the overloaded "verified" label was split into four evidence classes (operator_observed / operator_published / third_party_reported / unverified). Every pack value today is operator_published or weaker — the green VERIFIED badge is reserved for on-site passes and appears nowhere yet. Moonspin best corrected to $0.40 (0.33 belongs to its alt pack); Zoot's invented 11-SC midpoint yield removed ($2.99 → 10–12 SC source range kept). Homepage ranking switched to the conservative end of each range.
Round-2 audit correction: the earlier migration of 22 pack values to operator_published (PUBLISHED) overstated provenance. Auditing each record against the 2026-09-12 receipt's per-row sources showed every one traces to affiliate/review-site reporting or to inventory book values of the same origin — none to a captured operator-published page. All 22 were reclassified to third_party_reported (REPORTED). PUBLISHED is now a reserved class that requires a captured operator page per record; zero records qualify today, so no operator-origin number exists anywhere on this site.
Truth audit: copy that described unbuilt features (auto-claiming, live code monitoring, paid support, paid plans, creator payouts) was removed or marked not built. Drop-code pages now show only codes from that casino's own channel (previously every page showed the same Stake.us codes). Extension coverage is stated from data/detectors.json.