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.

Decision
review_revise · NEAR Intents
View on Solana ↗
Sequence
#4
Score
41 → 41 (0)
Cluster
mainnet-beta
Slot
462051373
Off-chain at
2026-10-27T11:20:19.205Z
Anchored at
2026-10-27T11:20:29.000Z
Block time
2026-10-27T11:20:29.000Z

Independent verification

1. Database (off-chain)
FEh6oGywmQUuCjwvpVyUezV9qbkbfaYMBrwddHR4Z1w4
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1852 chars)
{"actor":"judge","artifact_identity":"0433878f9dd9d2bc87f187cb7a922e7c","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T11:20:18.713Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3571,"investigation_id":"f6117990-9f86-4fca-9f9f-44c646c1b886","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":41,"page_slug":"near-intents","prev_score":41,"reason":"The core incident facts hold up: the $3.8M amount, the BNB Chain hot wallet and the SHIELD figures were confirmed (claim_findings[0], [9]). Of 14 scored findings (one blocked Hacken finding excluded), 5 were disputed or unverifiable, about 36%. Four are the exploit and announcement dates, which are one day late (claim_findings[1]-[4]). One is the unverified claim that the price drop was caused by the disclosure (claim_findings[13]). Separately, the page says no funds had been returned and the post-mortem was unpublished, which two outlets contradict (claim_findings[5]-[7]; omission_findings[0], critical). The page needs correction on recovery status and dates, and the unconfirmed KuCoin and Bitcoin routing should be attributed to ZachXBT.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":14,"sequence_num":4,"severity_override":{"applied":true,"band":"significant","from_band":"significant","reason":"The review reports a critical omission (the attacker returned the roughly $3.8M in full, per Decrypt and CoinDesk) and subject_status.contradicts_page is true. The page still presents an unrecovered theft. The band is held at significant, not deny, because the core exploit facts are confirmed and reviewer confidence is 0.7."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}