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
- Sequence
- #2
- Score
- 30 → 30 (0)
- Cluster
- mainnet-beta
- Slot
- 462279314
- Off-chain at
- 2026-10-28T00:48:38.212Z
- Anchored at
- 2026-10-28T00:49:13.000Z
- Block time
- 2026-10-28T00:49:13.000Z
Independent verification
- 1. Database (off-chain)
- 7pyxhgQhxDb86vPEijGb3xvRmMGXoGQrtBwL4QwXN5gy
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1349 chars)
{"actor":"reviewer","artifact_identity":"62e69d10ea4eaa0cd3f0f5a18cd1130b","decided_at":"2026-10-28T00:48:38.131Z","decision":"review","disputed_pct":0.2727,"findings_hash":"GKhGrhfzBspKhCf93eft2VhiK97u2ozcmEEmbSvoeRCE","investigation_id":"0494be34-a966-4de8-8be4-a06877a27149","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":30,"omissions":{"material":0,"total":1},"page_content_hash":"98107063bf9f07fbb23ecd308223e21347b776a7ca457a142b84380139b3d8da","page_slug":"zentra-finance-ctusd-aave-fork-exploit","prev_score":30,"reason":"The core exploit facts (date, time, amount, block, mechanism, deadline, Citrea restoration) are supported by the fetched sources. One claim is disputed: the page says Zentra published a post-mortem on Sept 11, but the cited article says attack details had not been published, and the mechanism came from DeFiHackLabs. The June 2023 refactor and audit-bypass claim has no support in the cited source. The status claims are about five weeks old, but no reopening was found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":2,"subject_status":"exploited","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}