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_revise · ValueDefi
- Sequence
- #5
- Score
- 34 → 34 (0)
- Cluster
- mainnet-beta
- Slot
- 464273572
- Off-chain at
- 2026-11-01T23:16:10.712Z
- Anchored at
- 2026-11-01T23:16:41.000Z
- Block time
- 2026-11-01T23:16:41.000Z
Independent verification
- 1. Database (off-chain)
- AAxpY9MoTwJNAajkS4B9H4P3CdwB9EcxkYwC3CyNk1t5
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1370 chars)
{"actor":"judge","artifact_identity":"0ffe0eb5809de7c7923b116cf96147ab","band_override":null,"decided_at":"2026-11-01T23:16:10.464Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1667,"investigation_id":"d3f4ed3e-58a3-4164-b8c3-f478058afd5c","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":34,"page_slug":"valuedefi","prev_score":34,"reason":"Of 6 claims checked, none were contradicted outright and 1 could not be found in the sources (claim_findings[1], the 'nine of 16 pools' figure), giving 17% unverifiable or disputed, which is the minor-issues band. Two further claims were only partly supported: the '$8.5 million' figure attributed to BASv2 appears to be a mix-up with 8.5M BDO tokens (claim_findings[0]), and the rekt leaderboard statement is attached to the third exploit when it follows from the second (claim_findings[2]). The core dates, amounts and mechanisms of all three exploits were confirmed. The reviewer checked only a small sample, with 0.4 confidence, so the penalty is kept at the low end of the band. No shutdown or other omission was reported.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}