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 · Palmswap
- Sequence
- #3
- Score
- 22 → 14 (-8)
- Cluster
- mainnet-beta
- Slot
- 465096433
- Off-chain at
- 2026-11-04T00:14:36.961Z
- Anchored at
- 2026-11-04T00:14:44.000Z
- Block time
- 2026-11-04T00:14:44.000Z
Independent verification
- 1. Database (off-chain)
- GAmC7MwaZiA7JxMuyLro8A4cXjSE3bNEedwn2XVayjMn
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1380 chars)
{"actor":"judge","artifact_identity":"66e2ae6a3654b60bed2fbd98caed471a","band_override":null,"decided_at":"2026-11-04T00:14:36.689Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2857,"investigation_id":"b617fa0c-4c7c-4ddc-885e-fbd0c5fffebd","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":14,"page_slug":"palmswap","prev_score":22,"reason":"The core exploit facts (flash loan, roughly $901,455 loss, attacker address, $721,450 returned, Gotbit conviction) were confirmed against CertiK and secondary reporting. Two of seven checked claims could not be verified (claim_findings[1] attack contract address not in the cited source; claim_findings[6] ZachXBT flag cited only to generic profile pages), giving about 29% unverified. claim_findings[2] has a transposed digit in a BSCScan source URL, and claim_findings[3] gives a return date (2023-07-31) the cited source does not support. The tokenomics and audit claims were not checked, and the missing Tornado Cash laundering detail is a minor omission. The page's description of the project as defunct matches current status data.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}