Audit log

Every state-changing event for burgel.eth: moderation decisions on community submissions, plus corrections and updates from the news pipeline. URL-based decisions are designed to carry three independent witnesses — the original source, an Internet Archive snapshot, and a Solana memo signed by our publicly-disclosed publisher key. Archive coverage is still being backfilled, so each decision below reports its own snapshot status rather than assuming one exists.

1. #1publishby system:backfill

   2026-05-30 13:03:50Z
   Score: ? → ? (no score change)
   anchoranchored

   chain

   ●mainnet-betaslot 423,161,806

   sig

   5fhhmpENq94b…Xyf7v7DGcopyexplorer ↗

   hash

   AGsGGiR75ZYc…qjhjJDqtcopysha256 → base58

   verifying row…full verify ↗

   canonical bytes (2819 B) ▸

   {"actor":"system:backfill","investigation_id":"fbbc210c-589b-423d-acbd-c997165eb157","kind":"publish","page_slug":"burgeleth","published_at":"2026-05-30T13:03:50.324Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"burgel.eth","sections":[{"content":"It appears burgel.eth was drained for ~$3M across multiple wallet addresses earlier this week likely as the result of a private key compromise. \n\nThe funds were consolidated into one theft address before they were deposited into Tornado Cash after. \n\nMain theft address\n[0x3a77c47cd683cf0b4e6bbd43683816e106ef3bec](https://etherscan.io/address/0x3a77c47cd683cf0b4e6bbd43683816e106ef3bec)","heading":"burgel.eth","severity":"critical","sources":[{"credibility":2,"name":"burgel.eth","type":"social_media","url":"https://t.me/zachxbt/45"}]},{"body":"The name 'Burgeleth' returned no results in any crypto-specific context across more than a dozen targeted search queries. Searches included: 'Burgeleth crypto scam', 'Burgeleth fraud', 'Burgeleth hack exploit', 'Burgeleth wallet address ETH Solana', 'Burgeleth NFT drainer phishing', 'Burgeleth token rugpull defi', 'Burgeleth Telegram scam alert', 'Burgeleth ZachXBT', 'Burgeleth etherscan OR bscscan', 'Burgeleth coinmarketcap OR coingecko', and domain probes for burgeleth.com, burgeleth.io, and burgeleth.net. No matching social media profiles, websites, blockchain addresses, or news articles were found. The Wayback Machine (web.archive.org) contains no archived pages referencing this name. The closest phonetic matches found were unrelated: 'Burleith' (a Washington D.C. neighborhood), 'Burgeth' (a German surname), and 'Burggit' (a Reddit alternative platform). It is not possible to assign a meaningful trust score without verifiable entity data; the neutral default of 50 is used here to indicate unknown status rather than confirmed risk or safety.","severity":"low","sources":[],"title":"Entity Identification"}],"sources_used":[{"archive_timestamp":null,"archive_url":null,"credibility":2,"name":"burgel.eth","type":"social_media","url":"https://t.me/zachxbt/45"}],"summary":"No verifiable information about an entity named 'Burgeleth' was found across any indexed web source as of May 2026. Exhaustive searches across news outlets, blockchain explorers, social media platforms, regulatory databases, domain registries, and crypto-specific intelligence sources (ZachXBT, Chainalysis, Scam Sniffer) returned zero results matching this name in a crypto or financial context. The slug may refer to an extremely obscure or newly created entity, an alternate spelling of a different entity, or a name that has not yet generated any publicly indexed presence.","timeline":[{"date":"2023-10-06","event":"burgel.eth","source":"t.me","source_url":"https://t.me/zachxbt/45"}]},"v":1}

   Verify offline (run on your own machine)

   python -m src.verify_decision fc1e5862-14b6-4e19-a584-aad92bd08a79copy
2. #2reviewby reviewerreviewer

   2026-06-10 15:37:39Z
   Score: 50 → 50 (no score change)
   The page suffers from a critical internal inconsistency: its summary and 'Entity Identification' section assert no verifiable information exists, while sections[0] documents a specific $3M private-key-compromise drain of burgel.eth with a named theft address and a ZachXBT Telegram citation that is independently confirmed to exist. The core incident claim (drain, consolidation, Tornado Cash) is sourced to a single verifiable Telegram post but lacks independent corroboration and on-chain documentation of the full $3M aggregate. The ZachXBT source URL resolves and contains the attributed text, but no archive URL is provided and no secondary press coverage of this specific incident was found.
   anchoranchored

   chain

   ●mainnet-betaslot 425,574,252

   sig

   2ebYv2JiEFch…7Ksdvw67copyexplorer ↗

   hash

   B1gFNKwUAT6N…ZWard216copysha256 → base58

   verifying row…full verify ↗

   canonical bytes (1042 B) ▸

   {"actor":"reviewer","decided_at":"2026-06-10T15:37:39.508Z","decision":"review","investigation_id":"fbbc210c-589b-423d-acbd-c997165eb157","new_score":50,"page_slug":"burgeleth","prev_score":50,"reason":"The page suffers from a critical internal inconsistency: its summary and 'Entity Identification' section assert no verifiable information exists, while sections[0] documents a specific $3M private-key-compromise drain of burgel.eth with a named theft address and a ZachXBT Telegram citation that is independently confirmed to exist. The core incident claim (drain, consolidation, Tornado Cash) is sourced to a single verifiable Telegram post but lacks independent corroboration and on-chain documentation of the full $3M aggregate. The ZachXBT source URL resolves and contains the attributed text, but no archive URL is provided and no secondary press coverage of this specific incident was found.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}

   Verify offline (run on your own machine)

   python -m src.verify_decision af6c41cd-4776-4c67-a26a-58a39241d81ecopy
3. #3review reviseby judgejudge

   2026-06-10 15:37:39Z
   Score: 50 → 30 (-20)
   The reviewer found 2 of 7 claims disputed (43% disputed_pct), placing this page in the 30–60% band requiring significant revision. Most critically, claim_findings[4] identifies a direct internal contradiction: the page summary and Entity Identification section assert 'no verifiable information exists,' while sections[0] on the same page documents a confirmed $3M private-key-compromise drain with a named theft address and a ZachXBT citation the reviewer verified resolves correctly. Claim_findings[6] further disputes the trust score justification of 50 (neutral) as inconsistent with the critical-severity incident already documented on the page. Two high-priority coverage gaps — the unverified $3M aggregate and the misleading summary — indicate the page requires editorial correction before it accurately represents the evidence it already holds.
   anchoranchored

   chain

   ●mainnet-betaslot 425,574,255

   sig

   3ycZKxna2tev…D9kDfMozcopyexplorer ↗

   hash

   DXMyArreKacv…QsvW8wzmcopysha256 → base58

   verifying row…full verify ↗

   canonical bytes (1204 B) ▸

   {"actor":"judge","decided_at":"2026-06-10T15:37:39.508Z","decision":"review_revise","investigation_id":"fbbc210c-589b-423d-acbd-c997165eb157","new_score":30,"page_slug":"burgeleth","prev_score":50,"reason":"The reviewer found 2 of 7 claims disputed (43% disputed_pct), placing this page in the 30–60% band requiring significant revision. Most critically, claim_findings[4] identifies a direct internal contradiction: the page summary and Entity Identification section assert 'no verifiable information exists,' while sections[0] on the same page documents a confirmed $3M private-key-compromise drain with a named theft address and a ZachXBT citation the reviewer verified resolves correctly. Claim_findings[6] further disputes the trust score justification of 50 (neutral) as inconsistent with the critical-severity incident already documented on the page. Two high-priority coverage gaps — the unverified $3M aggregate and the misleading summary — indicate the page requires editorial correction before it accurately represents the evidence it already holds.","score_delta":-20,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}

   Verify offline (run on your own machine)

   python -m src.verify_decision f56df8de-df55-4549-9767-c850db439090copy