Skip to main content
AVOID.NET

Audit log

Every state-changing event for SingularityNET (AGIX/WMTx Bridge Key Compromise): 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 10:59:20Z
    Score: 12 → 12 (no score change)
    The core narrative (compromised authorizer key, 8.72M FET drained, 408.5M NTX, 260M AGIX and 53.838M WMTx minted, key reportedly unrotated) is supported by the Metaverse Post and ForkLog articles I could read. The claim that SingularityNET issued no statement is too absolute given reported SingularityNET comments on treasury wallets. The WMTx $6.27M figure is inconsistent with the $16.77M total. The page does not mention Bitquery's larger mint tally or the multi-key theory, and its latest-status claims are about five weeks old. The Crypto Times source was blocked, so the minute-level timeline and the 99% price figure were not independently checked.
    anchoranchored
    chain
    ●mainnet-betaslot 462,045,442
    sig
    5kU7iAUg398v…GeCRLiPoexplorer ↗
    hash
    B7rQaTgJ287j…pCE1DksEsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1573 B) ▸
    {"actor":"reviewer","artifact_identity":"4ee3eaf3952896cc769414438e71a766","blocked_count":2,"decided_at":"2026-10-27T10:59:19.817Z","decision":"review","disputed_pct":0,"findings_hash":"2dGKSpUzsQSL33NAqyeoX2HKU2y9XvRv1HVtpbGyLFn8","investigation_id":"c619740c-0607-41e0-b5da-c19ca0f81524","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":12,"omissions":{"material":1,"total":3},"page_content_hash":"b25f52526932b6e339aea89810fa63a5aecbf02fb19d6f8fcfb3bff51e4a2d4d","page_slug":"singularitynet-agix-wmtx-bridge-key-compromise","prev_score":12,"reason":"The core narrative (compromised authorizer key, 8.72M FET drained, 408.5M NTX, 260M AGIX and 53.838M WMTx minted, key reportedly unrotated) is supported by the Metaverse Post and ForkLog articles I could read. The claim that SingularityNET issued no statement is too absolute given reported SingularityNET comments on treasury wallets. The WMTx $6.27M figure is inconsistent with the $16.77M total. The page does not mention Bitquery's larger mint tally or the multi-key theory, and its latest-status claims are about five weeks old. The Crypto Times source was blocked, so the minute-level timeline and the 99% price figure were not independently checked.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":7,"sequence_num":1,"subject_status":"exploited","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 c4cd7013-ba3d-4d8c-99f6-d22daa9b3451
  2. #2review reviseby judgejudge
    2026-10-27 10:59:20Z
    Score: 12 → 4 (-8)
    The core account of the incident holds up: the 8.72M FET drain, the 408.5M NTX mint, the 260M AGIX and 53.838M WMTx mints, and the reportedly unrotated key are confirmed by independent reporting (claim_findings[0], [1], [2], [6]). No claim was disputed. The page needs revision for three reasons. It omits later analysis showing much larger issuance and several compromised keys (omission_findings[0]). It states that SingularityNET issued no statement more absolutely than the sources allow (claim_findings[3]). It also presents a $6.27M WMTx figure that does not fit the $16.77M total (claim_findings[4]). Its latest-status claims are about five weeks old, and two checks (the 99% AGIX price drop and the minute-level timeline) could not be completed because the source blocked the reviewer, which limits coverage but is not a defect of the page.
    anchoranchored
    chain
    ●mainnet-betaslot 462,045,447
    sig
    5vdUdBbPqNiq…Qzd7euQNexplorer ↗
    hash
    oy8BG5cxR4hR…b4fqbLsjsha256 → base58
    verifying row…full verify ↗
    canonical bytes (2128 B) ▸
    {"actor":"judge","artifact_identity":"4ee3eaf3952896cc769414438e71a766","band_override":null,"blocked_count":2,"decided_at":"2026-10-27T10:59:19.817Z","decision":"review_revise","delist_requested":false,"disputed_pct":0,"investigation_id":"c619740c-0607-41e0-b5da-c19ca0f81524","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":4,"page_slug":"singularitynet-agix-wmtx-bridge-key-compromise","prev_score":12,"reason":"The core account of the incident holds up: the 8.72M FET drain, the 408.5M NTX mint, the 260M AGIX and 53.838M WMTx mints, and the reportedly unrotated key are confirmed by independent reporting (claim_findings[0], [1], [2], [6]). No claim was disputed. The page needs revision for three reasons. It omits later analysis showing much larger issuance and several compromised keys (omission_findings[0]). It states that SingularityNET issued no statement more absolutely than the sources allow (claim_findings[3]). It also presents a $6.27M WMTx figure that does not fit the $16.77M total (claim_findings[4]). Its latest-status claims are about five weeks old, and two checks (the 99% AGIX price drop and the minute-level timeline) could not be completed because the source blocked the reviewer, which limits coverage but is not a defect of the page.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-8,"scored_claims":7,"sequence_num":2,"severity_override":{"applied":true,"band":"minor","from_band":"approve","reason":"Computed disputed_pct is 0% (no disputed findings; the 2 unverifiable findings are source_blocked and excluded, leaving 7 countable). However, omission_findings[0] is material: later Bitquery analysis reported far larger issuance (including CGV) and a multi-key compromise theory that the page does not mention. Two high-priority coverage gaps (no post-incident updates in about five weeks, reliance on secondary sources) point the same way. Escalated from approve to the minor band."},"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 db3f5961-a406-4bfa-9030-f1e089f821a6
  3. #3reviewby reviewerreviewer
    2026-11-03 13:57:44Z
    Score: 4 → 4 (no score change)
    Core figures (FET drain, NTX mint, Bitquery totals, holdings, Bitvavo suspension, key non-rotation) match the ForkLog and CryptoSlate articles I fetched. Issues are minor: CryptoSlate is credited with repeating the AGIX/WMTx tallies but does not report them, and sources conflict on whether SingularityNET issued its own statement. The page hedges unverified items well. No newer status was found.
    anchoranchored
    chain
    ●mainnet-betaslot 464,924,032
    sig
    5B8GfucJRayY…DEU9q6hVexplorer ↗
    hash
    Cs3wZo4jLYf9…ktUdFkBMsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1237 B) ▸
    {"actor":"reviewer","artifact_identity":"7ff6470fb400b8a0b7434916c0ff83a6","decided_at":"2026-11-03T13:57:44.147Z","decision":"review","disputed_pct":0,"findings_hash":"1268xyZFg5J1BTSkXSCTyvL8y9VjznCLuPBLtehhKj4a","investigation_id":"c619740c-0607-41e0-b5da-c19ca0f81524","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":4,"page_content_hash":"61e53624812ef0a43f5492c04c1afbe80a24c8ec85c91b477fcae378e785b6dd","page_slug":"singularitynet-agix-wmtx-bridge-key-compromise","prev_score":4,"reason":"Core figures (FET drain, NTX mint, Bitquery totals, holdings, Bitvavo suspension, key non-rotation) match the ForkLog and CryptoSlate articles I fetched. Issues are minor: CryptoSlate is credited with repeating the AGIX/WMTx tallies but does not report them, and sources conflict on whether SingularityNET issued its own statement. The page hedges unverified items well. No newer status was found.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":3,"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 02bbe7a5-d834-47c2-853d-5cdca7633b78
  4. #4review reviseby judgejudge
    2026-11-03 13:57:44Z
    Score: 4 → 7 (+3)
    None of the 10 claim findings was disputed or unverifiable, so the computed disputed rate is 0%. The core figures (FET drain, NTX mint, Bitquery totals, attacker holdings, Bitvavo suspension, unrotated keys) match the ForkLog and CryptoSlate articles. Three findings were only partially supported: claim_findings[1] credits CryptoSlate with repeating AGIX and WMTx tallies it does not report, claim_findings[4] presents a SingularityNET statement as settled while sources conflict, and claim_findings[8] dates the latest reporting as 'late September' when it is Sept 19-21. The verdict is revise rather than approve because two high-priority coverage gaps remain: no on-chain addresses or transaction hashes, and no links to primary statements from SingularityNET, Fetch.ai or World Mobile. The penalty is kept small because the factual findings hold and the reviewer's confidence is moderate.
    anchoranchored
    chain
    ●mainnet-betaslot 464,924,038
    sig
    cmnvD2wTvDZX…Y9P8yvKGexplorer ↗
    hash
    9sWxyGoVQJ1D…vAuacs6Gsha256 → base58
    verifying row…full verify ↗
    canonical bytes (2670 B) ▸
    {"actor":"judge","artifact_identity":"7ff6470fb400b8a0b7434916c0ff83a6","band_override":{"actual_delta":-5,"actual_verdict":"review_revise","disputed_pct":0,"expected_delta_range":[0,0],"expected_verdict":"review_approve","rationale":"None of the 10 claim findings was disputed or unverifiable, so the computed disputed rate is 0%. The core figures (FET drain, NTX mint, Bitquery totals, attacker holdings, Bitvavo suspension, unrotated keys) match the ForkLog and CryptoSlate articles. Three findings were only partially supported: claim_findings[1] credits CryptoSlate with repeating AGIX and WMTx tallies it does not report, claim_findings[4] presents a SingularityNET statement as settled while sources conflict, and claim_findings[8] dates the latest reporting as 'late September' when it is Sept 19-21. The verdict is revise rather than approve because two high-priority coverage gaps remain: no on-chain addresses or transaction hashes, and no links to primary statements from SingularityNET, Fetch.ai or World Mobile. The penalty is kept small because the factual findings hold and the reviewer's confidence is moderate."},"decided_at":"2026-11-03T13:57:44.147Z","decision":"review_revise","delist_requested":false,"disputed_pct":0,"investigation_id":"c619740c-0607-41e0-b5da-c19ca0f81524","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":7,"page_slug":"singularitynet-agix-wmtx-bridge-key-compromise","prev_score":4,"reason":"None of the 10 claim findings was disputed or unverifiable, so the computed disputed rate is 0%. The core figures (FET drain, NTX mint, Bitquery totals, attacker holdings, Bitvavo suspension, unrotated keys) match the ForkLog and CryptoSlate articles. Three findings were only partially supported: claim_findings[1] credits CryptoSlate with repeating AGIX and WMTx tallies it does not report, claim_findings[4] presents a SingularityNET statement as settled while sources conflict, and claim_findings[8] dates the latest reporting as 'late September' when it is Sept 19-21. The verdict is revise rather than approve because two high-priority coverage gaps remain: no on-chain addresses or transaction hashes, and no links to primary statements from SingularityNET, Fetch.ai or World Mobile. The penalty is kept small because the factual findings hold and the reviewer's confidence is moderate.","replaces_fact_checks":{"score_before_fact_checks":12,"undone":1},"reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":3,"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 403e4931-fc82-4373-80ab-4fcbe7bef36e
  5. #5reviewby reviewerreviewer
    2026-11-04 09:56:04Z
    Score: 7 → 7 (no score change)
    The core figures, dates and attributed statements match CryptoSlate and ForkLog. Issues are minor: the page says key rotation is unconfirmed although CryptoSlate addresses it, one timeline entry attributes the Bitvavo fact to ForkLog, and the ForkLog publication date is unchecked. Protos and KuCoin were not fetched.
    anchoranchored
    chain
    ●mainnet-betaslot 465,259,408
    sig
    5obN7fqGU4RQ…p4HBnYHgexplorer ↗
    hash
    7TPDB4pjAfPx…PsbmCGVLsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1196 B) ▸
    {"actor":"reviewer","artifact_identity":"3487e110cd95edf8fda4d66077406044","decided_at":"2026-11-04T09:56:04.108Z","decision":"review","disputed_pct":0,"findings_hash":"D9xJKsXXydUYP1EJbxsj7NmHPoH9U4USzLbzfBMvnyGZ","investigation_id":"c619740c-0607-41e0-b5da-c19ca0f81524","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":7,"omissions":{"material":1,"total":1},"page_content_hash":"152be2a34c6d070456c12ce4befd4c6074f566b4e8335bdb3bb6f0ce2c1b3cef","page_slug":"singularitynet-agix-wmtx-bridge-key-compromise","prev_score":7,"reason":"The core figures, dates and attributed statements match CryptoSlate and ForkLog. Issues are minor: the page says key rotation is unconfirmed although CryptoSlate addresses it, one timeline entry attributes the Bitvavo fact to ForkLog, and the ForkLog publication date is unchecked. Protos and KuCoin were not fetched.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":5,"subject_status":"exploited","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 db19e548-5cc8-41ed-a9b9-1b4cbc4bbbf1
  6. #6review reviseby judgejudge
    2026-11-04 09:56:04Z
    Score: 7 → 4 (-3)
    All 10 claim findings were confirmed or partially supported, with none disputed or unverifiable, so the claim error rate is 0%. The page understates what its own source says about key rotation (claim_findings[2], omission_findings[0]): CryptoSlate reports the compromised credentials were still not rotated about five hours after the attack. Two smaller attribution problems also need fixing: the Bitvavo suspension is credited to ForkLog but appears in CryptoSlate (claim_findings[7]), and the ForkLog publication date is unchecked (claim_findings[8]). A high-priority gap remains for primary statements from the affected projects. The page covers the exploit and does not contradict the subject's status, so a small penalty and a minor-issues flag apply.
    anchoranchored
    chain
    ●mainnet-betaslot 465,259,413
    sig
    37gm6csjECUq…f1kHkAhXexplorer ↗
    hash
    Ha4EkRaqnMuR…UDDHhmRhsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1942 B) ▸
    {"actor":"judge","artifact_identity":"3487e110cd95edf8fda4d66077406044","band_override":null,"decided_at":"2026-11-04T09:56:04.108Z","decision":"review_revise","delist_requested":false,"disputed_pct":0,"investigation_id":"c619740c-0607-41e0-b5da-c19ca0f81524","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":4,"page_slug":"singularitynet-agix-wmtx-bridge-key-compromise","prev_score":7,"reason":"All 10 claim findings were confirmed or partially supported, with none disputed or unverifiable, so the claim error rate is 0%. The page understates what its own source says about key rotation (claim_findings[2], omission_findings[0]): CryptoSlate reports the compromised credentials were still not rotated about five hours after the attack. Two smaller attribution problems also need fixing: the Bitvavo suspension is credited to ForkLog but appears in CryptoSlate (claim_findings[7]), and the ForkLog publication date is unchecked (claim_findings[8]). A high-priority gap remains for primary statements from the affected projects. The page covers the exploit and does not contradict the subject's status, so a small penalty and a minor-issues flag apply.","replaces_fact_checks":{"score_before_fact_checks":12,"undone":2},"reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":-3,"sequence_num":6,"severity_override":{"applied":true,"band":"minor","from_band":"approve","reason":"omission_findings[0] is rated material: CryptoSlate reports the compromised bridge authorizer and NuNet minter credentials were not rotated or revoked about five hours after the attack, and the page only says rotation is unconfirmed. A high-priority coverage gap (primary statements) points the same way. The claim-level percentage alone (0%) understates this."},"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 1f43e0af-50ca-4c81-a936-2d6b7af688d7
  7. #7reviewby reviewerreviewer
    2026-11-17 18:25:09Z
    Score: 4 → 4 (no score change)
    The page's claims match the two main sources (CryptoSlate and ForkLog) closely and hedge appropriately on unverified figures and the lack of a SingularityNET statement. The only issues are two timeline dates given at month precision that the sources support at day level. A web search found no later developments that contradict the page.
    anchoranchored
    chain
    ●mainnet-betaslot 470,633,424
    sig
    2oye3JGKYpH4…z2hGjeRcexplorer ↗
    hash
    EiSUK2SVXwfF…TyhbjT1ssha256 → base58
    verifying row…full verify ↗
    canonical bytes (1180 B) ▸
    {"actor":"reviewer","artifact_identity":"35d64d79f4a76bd009c92df72b299b38","decided_at":"2026-11-17T18:25:09.598Z","decision":"review","disputed_pct":0,"findings_hash":"6t6zhDndLLDcuxG9pXP71RmHQPiF6c5x48fcsZQ31y9H","investigation_id":"c619740c-0607-41e0-b5da-c19ca0f81524","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":4,"page_content_hash":"db913d62aa4b37e325a32ba1542b3cbfd550b4c1d77fed33d753c4de744ef7cc","page_slug":"singularitynet-agix-wmtx-bridge-key-compromise","prev_score":4,"reason":"The page's claims match the two main sources (CryptoSlate and ForkLog) closely and hedge appropriately on unverified figures and the lack of a SingularityNET statement. The only issues are two timeline dates given at month precision that the sources support at day level. A web search found no later developments that contradict the page.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":7,"subject_status":"exploited","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 c7b2f8dc-7531-4551-b6ef-565727800191
  8. #8review approveby judgejudge
    2026-11-17 18:25:10Z
    Score: 4 → 12 (+8)
    Of 8 claim findings, 6 were confirmed against the CryptoSlate and ForkLog articles and 2 (claim_findings[5] and [6]) were partially supported only because the timeline dates give the month where the sources support the exact day. None were disputed or unverifiable, so disputed_pct is 0%. The reviewer found no omissions, and the page already reports the exploit, so subject status does not contradict it. The high-priority gap, the lack of a primary SingularityNET statement, is already stated openly on the page, so it suggests expansion rather than a penalty.
    anchoranchored
    chain
    ●mainnet-betaslot 470,633,431
    sig
    4ThzJ9BcaFqs…8fF1Liefexplorer ↗
    hash
    36WGYesZXhvG…98PoUSbGsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1303 B) ▸
    {"actor":"judge","artifact_identity":"35d64d79f4a76bd009c92df72b299b38","band_override":null,"decided_at":"2026-11-17T18:25:09.598Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"c619740c-0607-41e0-b5da-c19ca0f81524","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":12,"page_slug":"singularitynet-agix-wmtx-bridge-key-compromise","prev_score":4,"reason":"Of 8 claim findings, 6 were confirmed against the CryptoSlate and ForkLog articles and 2 (claim_findings[5] and [6]) were partially supported only because the timeline dates give the month where the sources support the exact day. None were disputed or unverifiable, so disputed_pct is 0%. The reviewer found no omissions, and the page already reports the exploit, so subject status does not contradict it. The high-priority gap, the lack of a primary SingularityNET statement, is already stated openly on the page, so it suggests expansion rather than a penalty.","replaces_fact_checks":{"score_before_fact_checks":12,"undone":3},"reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":8,"sequence_num":8,"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 e08ed0ed-8f6f-494b-9ee2-f4dbe4669a3c
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>.