Skip to main content
AVOID.NET
← SafeW Technology Co. Ltd. (SafeW Messaging App)9 decisions on this page

Audit log

Every state-changing event for SafeW Technology Co. Ltd. (SafeW Messaging App): 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:03:45Z
    Score: 2 → 2 (no score change)
    Core claims on the OFAC designation, Xinbi volume, June 2025 migration, and the disputed Singapore incorporation are supported by Treasury, OpenSanctions, SPF and TRM. The Bybit and WazirX attribution is not found in any cited source and should be removed. The DOJ seizure breakdown could not be checked (403).
    anchoranchored
    chain
    ●mainnet-betaslot 462,046,682
    sig
    4a6DRjXjsFZg…DvdFezaUexplorer ↗
    hash
    eLKUt8qvMZJc…YD5tieJZsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1186 B) ▸
    {"actor":"reviewer","artifact_identity":"b580b99d1501a3cb68fceb65ccaef085","blocked_count":1,"decided_at":"2026-10-27T11:03:45.083Z","decision":"review","disputed_pct":0,"findings_hash":"4hRRvgMvJAcsncUYi6XGYUcjKqpZzCJcDpbbFegWJKQZ","investigation_id":"549c8914-6b37-43af-b419-1249946871d6","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":2,"page_content_hash":"8cc44c8f95ff03e5673a4834a6d1ba538d3d02fc0fb858f685fe26db0bba98a6","page_slug":"safew-technology-co-ltd-safew-messaging-app","prev_score":2,"reason":"Core claims on the OFAC designation, Xinbi volume, June 2025 migration, and the disputed Singapore incorporation are supported by Treasury, OpenSanctions, SPF and TRM. The Bybit and WazirX attribution is not found in any cited source and should be removed. The DOJ seizure breakdown could not be checked (403).","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":7,"sequence_num":1,"subject_status":"sanctioned","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 2cd47896-f29d-4e98-98e5-a5be832a1b72
  2. #2review reviseby judgejudge
    2026-10-27 11:03:45Z
    Score: 2 → 0 (-8)
    Six of the seven checkable claims were confirmed against Treasury, OpenSanctions, the Singapore Police Force and TRM Labs, so the computed disputed share is 0% (claim_findings[7] was excluded because its source blocked the reviewer). The page moves out of the approve band because claim_findings[3], in a critical section, attributes the Bybit and WazirX hacks to Xinbi and SafeW and no cited source says so, and because coverage_gaps[0] (SafeW ownership, jurisdiction and operations) is high priority. The sanction is current and the page reports it, so no omission applies. The unsupported specifics should be removed, which makes this a minor revision.
    anchoranchored
    chain
    ●mainnet-betaslot 462,046,685
    sig
    4CHPtvV21jr1…8wKtyoiLexplorer ↗
    hash
    8fjophn8WkrH…vtzpgrFBsha256 → base58
    verifying row…full verify ↗
    canonical bytes (2162 B) ▸
    {"actor":"judge","artifact_identity":"b580b99d1501a3cb68fceb65ccaef085","band_override":{"actual_delta":-8,"actual_verdict":"review_revise","disputed_pct":0,"expected_delta_range":[0,0],"expected_verdict":"review_approve","rationale":"Six of the seven checkable claims were confirmed against Treasury, OpenSanctions, the Singapore Police Force and TRM Labs, so the computed disputed share is 0% (claim_findings[7] was excluded because its source blocked the reviewer). The page moves out of the approve band because claim_findings[3], in a critical section, attributes the Bybit and WazirX hacks to Xinbi and SafeW and no cited source says so, and because coverage_gaps[0] (SafeW ownership, jurisdiction and operations) is high priority. The sanction is current and the page reports it, so no omission applies. The unsupported specifics should be removed, which makes this a minor revision."},"blocked_count":1,"decided_at":"2026-10-27T11:03:45.083Z","decision":"review_revise","delist_requested":false,"disputed_pct":0,"investigation_id":"549c8914-6b37-43af-b419-1249946871d6","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"safew-technology-co-ltd-safew-messaging-app","prev_score":2,"reason":"Six of the seven checkable claims were confirmed against Treasury, OpenSanctions, the Singapore Police Force and TRM Labs, so the computed disputed share is 0% (claim_findings[7] was excluded because its source blocked the reviewer). The page moves out of the approve band because claim_findings[3], in a critical section, attributes the Bybit and WazirX hacks to Xinbi and SafeW and no cited source says so, and because coverage_gaps[0] (SafeW ownership, jurisdiction and operations) is high priority. The sanction is current and the page reports it, so no omission applies. The unsupported specifics should be removed, which makes this a minor revision.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-8,"scored_claims":7,"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 9ff15b09-7cd4-46ca-8a4a-5f25cb3f821e
  3. #3rescoreby systemsystem
    2026-11-01 12:37:11Z
    Score: 0 → 37 (+37)
    Rescored under Scoring v2, the published formula (avoid.net/scoring): 0 → 37. Problems weighed by who is responsible: the subject's own conduct −50, concerns that are not fraud −3.2; legitimacy credit long-running +10, regulated +5; 1 section(s) set aside until a failed fact-check is resolved; fact-check adjustments (−8) now shown as page reliability, not in the score.
    anchoranchored
    chain
    ●mainnet-betaslot 464,094,852
    sig
    4UwAjXQEw54Q…qq87q8SYexplorer ↗
    hash
    jC93FL6Z6rsq…WdWTnd3Zsha256 → base58
    verifying row…full verify ↗
    canonical bytes (768 B) ▸
    {"actor":"system","decided_at":"2026-11-01T12:37:11.422Z","decision":"rescore","investigation_id":"549c8914-6b37-43af-b419-1249946871d6","new_score":37,"page_slug":"safew-technology-co-ltd-safew-messaging-app","prev_score":0,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 0 → 37. Problems weighed by who is responsible: the subject's own conduct −50, concerns that are not fraud −3.2; legitimacy credit long-running +10, regulated +5; 1 section(s) set aside until a failed fact-check is resolved; fact-check adjustments (−8) now shown as page reliability, not in the score.","score_delta":37,"score_model":"v2","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 832e6fac-90d6-4c97-accd-0896b0e9e6bb
  4. #4rescoreby systemsystem
    2026-11-03 13:59:53Z
    Score: 37 → 47 (+10)
    Re-read and rescored after the page was re-researched (2026-11-03). Rescored under Scoring v2, the published formula (avoid.net/scoring): 37 → 47. Problems weighed by who is responsible: the subject's own conduct −25, problems around the subject, caused by others −3.8; legitimacy credit long-running +2.
    anchoranchored
    chain
    ●mainnet-betaslot 464,924,623
    sig
    62WKCqw7DpU7…nPd7Tbryexplorer ↗
    hash
    5ZLrvW7dJ3iy…NiWeeLVisha256 → base58
    verifying row…full verify ↗
    canonical bytes (702 B) ▸
    {"actor":"system","decided_at":"2026-11-03T13:59:52.525Z","decision":"rescore","investigation_id":"549c8914-6b37-43af-b419-1249946871d6","new_score":47,"page_slug":"safew-technology-co-ltd-safew-messaging-app","prev_score":37,"reason":"Re-read and rescored after the page was re-researched (2026-11-03). Rescored under Scoring v2, the published formula (avoid.net/scoring): 37 → 47. Problems weighed by who is responsible: the subject's own conduct −25, problems around the subject, caused by others −3.8; legitimacy credit long-running +2.","score_delta":10,"score_model":"v2","sequence_num":4,"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 0d12c729-3cb3-41ac-b241-beb44d137e5e
  5. #5reviewby reviewerreviewer
    2026-11-03 14:01:14Z
    Score: 47 → 47 (no score change)
    Core claims (OFAC designation of SafeW and Anwen on 2026-09-09, Xinbi details, DOJ seizures and restraints) are confirmed by Treasury and news sources. The one defect is the Elliptic citation: the linked WazirX article does not mention Xinbi or the $220,000 transfer, which comes from a different Elliptic piece. Timeline dates are imprecise but not wrong. The page flags its own uncertainty appropriately.
    anchoranchored
    chain
    ●mainnet-betaslot 464,924,923
    sig
    632sn2xj2yD3…hwjGV2kHexplorer ↗
    hash
    h31rtoavvA2u…dUovKdvbsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1289 B) ▸
    {"actor":"reviewer","artifact_identity":"9830b7abd9655eff6ea6732c766747e7","decided_at":"2026-11-03T14:01:14.226Z","decision":"review","disputed_pct":0.125,"findings_hash":"543PJJtXEwQoLWH87QjxPGzFRv53TBoDJf6nfFUbFkKW","investigation_id":"549c8914-6b37-43af-b419-1249946871d6","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":47,"omissions":{"material":0,"total":2},"page_content_hash":"b7c0279e265f4d55a38f1eb7aa80332d0eedbb9d49282cfb55d2f2de39c211fe","page_slug":"safew-technology-co-ltd-safew-messaging-app","prev_score":47,"reason":"Core claims (OFAC designation of SafeW and Anwen on 2026-09-09, Xinbi details, DOJ seizures and restraints) are confirmed by Treasury and news sources. The one defect is the Elliptic citation: the linked WazirX article does not mention Xinbi or the $220,000 transfer, which comes from a different Elliptic piece. Timeline dates are imprecise but not wrong. The page flags its own uncertainty appropriately.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":5,"subject_status":"sanctioned","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 c162593a-66b5-49f4-91ff-4e6700ca3685
  6. #6review reviseby judgejudge
    2026-11-03 14:01:14Z
    Score: 47 → 47 (no score change)
    The core claims hold up: the OFAC designation of SafeW on 2026-09-09, the Xinbi details and the DOJ seizures are confirmed by Treasury and news sources (claim_findings[0-2], [5]). One of eight findings (claim_findings[7]) counts as unverifiable, which puts the disputed share at about 12.5%, in the minor band. That finding is a negative statement about the Bybit hack for which nothing contradicting was found. The Elliptic citation points to the wrong article (claim_findings[3-4]), so the Xinbi/WazirX claim is real but its link needs replacing. The two omissions are minor and the page's sanctioned status matches the reviewer's findings.
    anchoranchored
    chain
    ●mainnet-betaslot 464,924,929
    sig
    5hu5N9bVDgxC…dWKy58Bnexplorer ↗
    hash
    AcTohstu1XEx…jRudHQ3Gsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1318 B) ▸
    {"actor":"judge","artifact_identity":"9830b7abd9655eff6ea6732c766747e7","band_override":null,"decided_at":"2026-11-03T14:01:14.226Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.125,"investigation_id":"549c8914-6b37-43af-b419-1249946871d6","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":47,"page_slug":"safew-technology-co-ltd-safew-messaging-app","prev_score":47,"reason":"The core claims hold up: the OFAC designation of SafeW on 2026-09-09, the Xinbi details and the DOJ seizures are confirmed by Treasury and news sources (claim_findings[0-2], [5]). One of eight findings (claim_findings[7]) counts as unverifiable, which puts the disputed share at about 12.5%, in the minor band. That finding is a negative statement about the Bybit hack for which nothing contradicting was found. The Elliptic citation points to the wrong article (claim_findings[3-4]), so the Xinbi/WazirX claim is real but its link needs replacing. The two omissions are minor and the page's sanctioned status matches the reviewer's findings.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":6,"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 bda041d5-7d56-4aeb-a3a5-f0145d236b71
  7. #7rescoreby systemsystem
    2026-11-04 09:53:32Z
    Score: 47 → 50 (+3)
    Re-read and rescored after the page was re-researched (2026-11-04). Rescored under Scoring v2, the published formula (avoid.net/scoring): 47 → 50. Problems weighed by who is responsible: the subject's own conduct −25, problems around the subject, caused by others −2.3; legitimacy credit long-running +8; serious regulatory wrongdoing with no established harm to customers is held in WARNING (26–50).
    anchoranchored
    chain
    ●mainnet-betaslot 465,258,689
    sig
    3d1nF4NBDEFo…G2FNTZ8Qexplorer ↗
    hash
    8jtiXPPfy8c3…sCf5DDTzsha256 → base58
    verifying row…full verify ↗
    canonical bytes (797 B) ▸
    {"actor":"system","decided_at":"2026-11-04T09:53:31.397Z","decision":"rescore","investigation_id":"549c8914-6b37-43af-b419-1249946871d6","new_score":50,"page_slug":"safew-technology-co-ltd-safew-messaging-app","prev_score":47,"reason":"Re-read and rescored after the page was re-researched (2026-11-04). Rescored under Scoring v2, the published formula (avoid.net/scoring): 47 → 50. Problems weighed by who is responsible: the subject's own conduct −25, problems around the subject, caused by others −2.3; legitimacy credit long-running +8; serious regulatory wrongdoing with no established harm to customers is held in WARNING (26–50).","score_delta":3,"score_model":"v2","sequence_num":7,"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 b712b473-bdb2-4584-b9b1-e490cabee206
  8. #8reviewby reviewerreviewer
    2026-11-04 09:54:44Z
    Score: 50 → 50 (no score change)
    Core claims about the OFAC designation, date, legal basis, Singapore base, and June 2025 migration match the Treasury release. Secondary figures (freeze, Elliptic numbers, WazirX link) were only partly checked. The page is carefully hedged and shows no contradictions.
    anchoranchored
    chain
    ●mainnet-betaslot 465,259,115
    sig
    4Xg6XfmGKJXs…EfDBbFtDexplorer ↗
    hash
    4v44dSLtnzHT…9b2m2KUrsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1110 B) ▸
    {"actor":"reviewer","artifact_identity":"b96301bf4952ba8137a3b04f97c16fa4","decided_at":"2026-11-04T09:54:43.833Z","decision":"review","disputed_pct":0,"findings_hash":"FUG6igupyscGJ8SSaTRgzLBzYbNqS6qZNdbK3mtbwbKZ","investigation_id":"549c8914-6b37-43af-b419-1249946871d6","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":50,"page_content_hash":"60b30ecd65097cd16845c7136b0c62518c0940ac5f343d71de2c860dd96b5518","page_slug":"safew-technology-co-ltd-safew-messaging-app","prev_score":50,"reason":"Core claims about the OFAC designation, date, legal basis, Singapore base, and June 2025 migration match the Treasury release. Secondary figures (freeze, Elliptic numbers, WazirX link) were only partly checked. The page is carefully hedged and shows no contradictions.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":8,"subject_status":"sanctioned","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 4a3e3133-3983-4997-b148-89beaab6dfb5
  9. #9review approveby judgejudge
    2026-11-04 09:54:44Z
    Score: 50 → 50 (no score change)
    Four of the five checked claims were confirmed, three of them against the US Treasury press release (claim_findings[0-2]). The other, the UK sanctions claim in claim_findings[3], matched secondary reporting. One claim, the Secret Service freeze and Elliptic figures, was only partially supported because part of it was not fetched (claim_findings[4]). None were disputed or unverifiable, so the disputed share is 0%. The OFAC sanction status is already on the page, and the review found no omissions. Open coverage gaps are medium or low priority and suggest expansion only.
    anchoranchored
    chain
    ●mainnet-betaslot 465,259,121
    sig
    4zgV6d1dcWAp…ePjoU3Biexplorer ↗
    hash
    CxJzgF9bGN4a…sjxuwnezsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1247 B) ▸
    {"actor":"judge","artifact_identity":"b96301bf4952ba8137a3b04f97c16fa4","band_override":null,"decided_at":"2026-11-04T09:54:43.833Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"549c8914-6b37-43af-b419-1249946871d6","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":50,"page_slug":"safew-technology-co-ltd-safew-messaging-app","prev_score":50,"reason":"Four of the five checked claims were confirmed, three of them against the US Treasury press release (claim_findings[0-2]). The other, the UK sanctions claim in claim_findings[3], matched secondary reporting. One claim, the Secret Service freeze and Elliptic figures, was only partially supported because part of it was not fetched (claim_findings[4]). None were disputed or unverifiable, so the disputed share is 0%. The OFAC sanction status is already on the page, and the review found no omissions. Open coverage gaps are medium or low priority and suggest expansion only.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":9,"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 37d69751-ff14-4bd0-a9e6-bd10d3e5d03d
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>.