Verify a decision
Every moderation decision on AVOID.NET is anchored to the Solana blockchain. You don't have to trust us — you can verify cryptographically that we committed to a verdict at a specific moment and have not rewritten it.
How verification works
- We commit. When a moderator accepts/rejects a submission, we serialize the decision into deterministic UTF-8 bytes (
payload_canonical_string), hash it with SHA-256, encode the digest as base58, and write it to Solana inside an SPL Memo v2 transaction. - We store the bytes. The exact bytes we hashed are stored alongside the decision in our database. Anyone can read them and recompute the hash in any language.
- You compare three values. Database hash, your independently-recomputed hash, and the hash inside the on-chain memo. If all three match, the decision is authentic and timestamped.
The on-chain memo format is
AVOID.NET|v1|h:<b58-sha256>|d:<id>|t:<iso>Find a signature on any investigation page's decision log, or run python -m src.verify_decision --signature <sig> for a CLI check.
Decision
review_revise · SingularityNET (AGIX/WMTx Bridge Key Compromise)
- Sequence
- #4
- Score
- 4 → 7 (+3)
- Cluster
- mainnet-beta
- Slot
- 464924038
- Off-chain at
- 2026-11-03T13:57:44.468Z
- Anchored at
- 2026-11-03T13:58:12.000Z
- Block time
- 2026-11-03T13:58:12.000Z
Independent verification
- 1. Database (off-chain)
- 9sWxyGoVQJ1DDPbaUEdBtdGyK4iQdRmDEmVDvAuacs6G
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2670 chars)
{"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}