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
#3
Score
10 → 5 (-5)
Cluster
mainnet-beta
Slot
462057948
Off-chain at
2026-10-27T11:43:36.955Z
Anchored at
2026-10-27T11:43:51.000Z
Block time
2026-10-27T11:43:51.000Z

Independent verification

1. Database (off-chain)
56eC2zaFnYhWAMLox4mFPRFARSSxGKwiG7ahETBfAw7d
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1594 chars)
{"actor":"judge","artifact_identity":"36a194fa2d8e1fa583e0e00dec397e47","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T11:43:36.335Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1111,"investigation_id":"b80f49cf-4365-4930-8755-0111bc52f99a","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":5,"page_slug":"aztec-connect-deprecated-bridge-exploits-june-2026","prev_score":10,"reason":"The core account (date, time, amount, the numRealTxs mechanism, the April 2024 renouncement and the separation from the current Aztec network) is confirmed by the Aztec Labs post-mortem (claim_findings[0-2], [6]). One of nine scorable claims could not be found in a source (claim_findings[9], the broader-context loss figures), about 11%, and one more was unreadable because the source blocked access and is left out of the count (claim_findings[7]). Several claims are only partly supported: the $2.27M total is a derived figure close to the post-mortem's sum of about $2.28M (claim_findings[4]), the fund-routing chain belongs to the second-wave wallet (claim_findings[3]), and the 1.6% token move is not in the cited article (claim_findings[5]). The page's status as exploited is accurate and the only omission is minor, so the penalty is kept at the low end of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-5,"scored_claims":9,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}