Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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.

Sequence
#2
Score
12 → 4 (-8)
Cluster
mainnet-beta
Slot
462045447
Off-chain at
2026-10-27T10:59:20.161Z
Anchored at
2026-10-27T10:59:30.000Z
Block time
2026-10-27T10:59:30.000Z

Independent verification

1. Database (off-chain)
oy8BG5cxR4hRQdNhub93FVKEm7yQAMM35f6b4fqbLsj
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2128 chars)
{"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}