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_approve · SingularityNET (AGIX/WMTx Bridge Key Compromise)
- Sequence
- #8
- Score
- 4 → 12 (+8)
- Cluster
- mainnet-beta
- Slot
- 470633431
- Off-chain at
- 2026-11-17T18:25:10.018Z
- Anchored at
- 2026-11-17T18:25:27.000Z
- Block time
- 2026-11-17T18:25:27.000Z
Independent verification
- 1. Database (off-chain)
- 36WGYesZXhvGsrx5hbr5VMiDMTVmJ1NDjbTG98PoUSbG
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1303 chars)
{"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}