Public ledger of every directory change — grade bumps, KYC re-tests, sponsorship activations, incident updates. We log it so visitors can verify our claim that the editorial firewall holds.
The list is the product; this is the receipt of how it changes.
Day 12 probe: bundle + backend + SSR marketing all identical to 2026-07-16 state. Site not down. Two consecutive checks with the same 1.9 MB bundle + same shutdown-banner strings suggest the 2026-07-14 slim-bundle was the anomaly, not the stable state. Incident stays open. Grade + provider status unchanged. Reschedule +40h.
Day 10 probe reversed the 2026-07-14 de-facto-retraction finding. Bundle asset back to /assets/index-BiGez_7b.js (last-modified 2026-06-29, 1.9 MB) with all four shutdown-banner strings present. Backend health still operational. Incident status reopened; title + summary rewritten to reflect the reversal. Grade + provider status unchanged. Reschedule +40h.
Day 8 probe: JS bundle rebuilt 1.9MB → 622KB with shutdown-banner strings removed; backend health reports server+db+redis operational; SSR marketing continues to read as normal casino promotion. Read: de-facto retraction by code removal without a public statement. Incident status resolved. Grade + provider status unchanged. Reschedule +40h to keep poll alive.
Day 7 past announced 2026-07-06 shutdown. Site frontend + backend both healthy (api.xmr.gg/health confirms server/db/redis operational). Marketing SSR fully back to casino-promotion copy; Anjouan seal loaded. Shutdown banner strings still in JS bundle behind localStorage-dismissable UI. Operator has not published a follow-up. Read: de-facto retraction without a public statement. Not flipping to hidden — site is not down. Incident title + summary updated to reflect 7-days-past state; incident kept on file so readers see the announced-vs-actual mismatch. Reschedule +40h.
Day 5 past announced 2026-07-06 shutdown. Site still 200, SSR marketing drifted back to normal casino copy, shutdown banner still in JS bundle behind dismissable localStorage key, /api/status returns 200. Operator has neither honored nor formally retracted the shutdown. Incident title + summary updated to reflect missed-date ambiguity. Status held at active. Next re-check +40h.
shutdown-watch 2026-07-09 22:50Z: site still HTTP 200 day 3 past announced 2026-07-06 shutdown. Withdrawal-page minimal shell. Do not flip status yet — grace-in-good-faith shape. Next re-check +40h.
shutdown-watch 2026-07-09 07:44Z: site still HTTP 200 ~3 days past announced 2026-07-06 shutdown. Grace-window remains open; no status flip yet.
shutdown-watch monitor 2026-07-08 06:48Z: site still HTTP 200 clearnet, ~2 days past announced 2026-07-06 shutdown. Grace-period (withdraw) still open; do not flip status/hide maintainer yet. +40h re-check scheduled.
Wake-check on shutdown date: still HTTP 200 with withdrawal banner. Not flipping status yet.
Shutdown announced 2026-07-06 per operator; incident + timeline entries added.
xmr.club
{
"also_listed_at": {
"monerica": true
}
}{"provider":{"id":"xmr-gg","category":"wagering","subcategory":"casinos","name":"xmr.gg","tagline":"Monero casino — slots, crash, mines, plinko, tower, coinflip, sports betting. Provably fair, no-KYC.","review":"xmr.gg is a Monero-paid casino covering the broader vertical xmr.bar leaves on the table — slots, crash, mines, plinko, tower, coinflip, plus sports betting. Provably-fair construction across game types (per their meta + structured data), no-KYC for play, instant deposits + withdrawals. Site has been live since 2026-05-14 (TLS cert + last-modified timestamp) — ~2-3 weeks at first listing, more mature than the brand-new xmr.win but still pre-track-record.\n\n**Privacy posture**: no-KYC claimed for normal play (verified via their `/robots.txt` + landing copy; not exhaustively probed at scale). The site sits behind ddos-guard rather than Cloudflare, which is a mild positive for users who care about CF visibility. We haven't run end-to-end withdrawal tests yet.\n\n**Why C, not B**: