Публичный реестр каждого изменения — чтобы любой мог проверить, что редакционный firewall работает.
Список — это продукт; здесь — чек о том, как он меняется.
Third-party corroboration from Monero Society TG community member @Brownoid (internal-only per witness-protection rule). Pre-existing community suspicion + post-evidence confirmation. Warning-lead evidence chain gains community-level corroboration bullet.
XMR Escrow demoted C → F on 2026-08-05 for active exit-scam. Verified operator identity via documented DM history (@xmrescrow X was real operator). Victim reported $6,000 BTC loss with 3 verified on-chain txids. Operator identifier "TT" matches GitHub org xmrescro display name "tt". Coincident scrub of public contact surfaces (X deleted, GitHub whitewash commit, /about reactive whitewash). Site still taking new escrows. Full shame-list warning-lead prepended. All evidence URLs preserved to Internet Archive.
Verification pass 2026-08-05. Site still operational. /about page explicitly disclaims social media + warns against imposters + publishes PGP + XMPP/Tuta contacts only. Reframed warning-lead — imposter-scam hypothesis now on the table. Severity critical->high. Grade C held pending reporter chain-of-contact clarification. F escalation gated on real-channel verification or independent reports.
Redacted reporter handle (@IanMVA) from public review body per reporter-privacy rule. Added verified X-account-deleted corroborating signal (2026-08-05). Bumped incident severity low -> critical. Grade held at C pending curator escalation decision to F. Reporter handle retained in internal audit trail + submission row only.
Open-incident treatment triggered by submission #59 (user scam report against operator "TT", claimed $6,400 loss). Single-source, receipts referenced but not attached. Warning-lead prepended. Grade C held pending +14d corroboration.
Rotated links.tor to operator-advertised onion (xmrescrobcw33cnm5…) per /onion-audit drift resolution.
xmr.club