Skip to main content
AVOID.NET

Audit log

Every state-changing event for Seoul Northern Coin Fraud Ring (91.3 Billion Won Scheme): 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. #1reviewby reviewerreviewer
    2026-10-27 11:06:59Z
    Score: 2 → 2 (no score change)
    Core facts (verdict, sentences, amounts, period, scheme mechanics, ringleader ages and background) are confirmed by Edaily and Seoul Economic Daily. Issues are minor: an unsupported claim that exchanges were controlled or influenced by the group, an editorial 'pyramid-style' inference, two unmatched direct quotes, and an uncited 11 billion won comparison case. Appeal status is unknown.
    anchoranchored
    chain
    ●mainnet-betaslot 462,047,730
    sig
    RtChMd3ed6JT…ndHB34KXexplorer ↗
    hash
    j1MLTpcyCRzQ…s1xbmto2sha256 → base58
    verifying row…full verify ↗
    canonical bytes (1278 B) ▸
    {"actor":"reviewer","artifact_identity":"aad60d619ba3c4aa511a454715d961fa","decided_at":"2026-10-27T11:06:59.195Z","decision":"review","disputed_pct":0.0769,"findings_hash":"353q7nUW87mwW2YGYBoENCatModACSRR5ZxaB4dwj9b1","investigation_id":"03008484-916d-4a38-8ecd-9f05ee2ee4f4","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":2,"omissions":{"material":0,"total":2},"page_content_hash":"830b3f599e9d2415153c394c02115055a2d0def06f41454522342a886658272f","page_slug":"seoul-northern-coin-fraud-ring-91-3-billion-won-scheme","prev_score":2,"reason":"Core facts (verdict, sentences, amounts, period, scheme mechanics, ringleader ages and background) are confirmed by Edaily and Seoul Economic Daily. Issues are minor: an unsupported claim that exchanges were controlled or influenced by the group, an editorial 'pyramid-style' inference, two unmatched direct quotes, and an uncited 11 billion won comparison case. Appeal status is unknown.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":1,"subject_status":"unknown","subject_status_contradicts_page":false,"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 15684439-2f67-44f2-8372-f59b19d794f9
  2. #2review approveby judgejudge
    2026-10-27 11:06:59Z
    Score: 2 → 2 (no score change)
    Of 12 claims checked, none were disputed and one (claim_findings[9], an uncited 11 billion won comparison case in a low-severity context section) could not be verified, giving a disputed rate of about 8%. The core facts are confirmed by two Tier 2 outlets: the 19 August 2026 verdict, the 14-year sentences, the 91.3 billion won figure, the scheme period and the scheme mechanics (claim_findings[0-2,4,7-8]). Three claims are only partly supported: the claim that the group controlled or influenced exchanges (claim_findings[5]), the 'pyramid-style' wording (claim_findings[6]) and two unmatched direct quotes (claim_findings[3]). These are small wording corrections. The one high-priority coverage gap, that no coins or exchanges are named, is a limit the page already states, so the page stays approved and the gap is a suggestion to expand it. The omissions are minor and the appeal status is unknown, so no escalation applies.
    anchoranchored
    chain
    ●mainnet-betaslot 462,047,735
    sig
    5MXqFCJgajwn…4c2r5sBoexplorer ↗
    hash
    9C7W8gu8Zvf6…tKy7EvPUsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1617 B) ▸
    {"actor":"judge","artifact_identity":"aad60d619ba3c4aa511a454715d961fa","band_override":null,"decided_at":"2026-10-27T11:06:59.195Z","decision":"review_approve","delist_requested":false,"disputed_pct":0.0769,"investigation_id":"03008484-916d-4a38-8ecd-9f05ee2ee4f4","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":2,"page_slug":"seoul-northern-coin-fraud-ring-91-3-billion-won-scheme","prev_score":2,"reason":"Of 12 claims checked, none were disputed and one (claim_findings[9], an uncited 11 billion won comparison case in a low-severity context section) could not be verified, giving a disputed rate of about 8%. The core facts are confirmed by two Tier 2 outlets: the 19 August 2026 verdict, the 14-year sentences, the 91.3 billion won figure, the scheme period and the scheme mechanics (claim_findings[0-2,4,7-8]). Three claims are only partly supported: the claim that the group controlled or influenced exchanges (claim_findings[5]), the 'pyramid-style' wording (claim_findings[6]) and two unmatched direct quotes (claim_findings[3]). These are small wording corrections. The one high-priority coverage gap, that no coins or exchanges are named, is a limit the page already states, so the page stays approved and the gap is a suggestion to expand it. The omissions are minor and the appeal status is unknown, so no escalation applies.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","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 4b1040f0-7275-4750-99cf-55fb4322f324
How verification works. The “Row integrity” check above is computed in your browser — your machine recomputes the SHA-256 of the canonical bytes and compares against the stored hash. No avoid.net server can fake that check. The “full verify” link goes one level deeper: your browser fetches the on-chain transaction from a Solana RPC node and confirms the same hash is in the memo. If you don’t want to trust either avoid.net or the public RPC, run the CLI verifier on your own machine — python -m src.verify_decision <event_id>.