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
- 10 → 10 (0)
- Cluster
- mainnet-beta
- Slot
- 462279346
- Off-chain at
- 2026-10-28T00:48:43.153Z
- Anchored at
- 2026-10-28T00:49:20.000Z
- Block time
- 2026-10-28T00:49:20.000Z
Independent verification
- 1. Database (off-chain)
- 5YQtaXVahdZooe73gncpGBLyK4ce5FBJ7SjAdty87o3p
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1589 chars)
{"actor":"reviewer","artifact_identity":"d5413c4775c66245c9b7fe674d5050dc","decided_at":"2026-10-28T00:48:43.085Z","decision":"review","disputed_pct":0.2308,"findings_hash":"9rX4EbppwBydpxATas27x2EMBqmU9r7ZMguVuAn2z9jy","investigation_id":"b4f97d31-3bf4-4118-aae4-ecc0c1826a1e","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":10,"omissions":{"material":1,"total":3},"page_content_hash":"297001d6d311c268dff88e3da81de12d3a4337562295dcc2155b7709efc85f50","page_slug":"flashloopadapter-aave-v3-safe-module-exploit","prev_score":10,"reason":"The core incident facts hold up against crypto.news, mpost and Blockfence. These are the date, the amounts, the addresses, the fake-Safe mechanism, the Morpho flash loan, the Aave statement and the bounty terms. Problems found: an unsupported 'reentrancy-adjacent' label, a transaction hash I could not find in any source, a 'both Safes disabled the module' claim that the cited Blockfence article does not make, and an overstated 'first' for SlowMist. The summary's wording that 114.09 ETH was drained from the Safes conflates the attacker's net profit with victim losses. The page omits the reported Tornado Cash laundering, and its bounty status is stale. About half the cited sources were not fetched.","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}