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 · Growth DeFi
- Sequence
- #3
- Score
- 50 → 50 (0)
- Cluster
- mainnet-beta
- Slot
- 464380336
- Off-chain at
- 2026-11-02T05:37:46.280Z
- Anchored at
- 2026-11-02T05:37:58.000Z
- Block time
- 2026-11-02T05:37:58.000Z
Independent verification
- 1. Database (off-chain)
- EhRLByfStMmdjKS6fy5TRPY264h6XewsJZtHyrNGE1GY
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1290 chars)
{"actor":"reviewer","artifact_identity":"e5e77b5f6dd464e4c07d00bc5f5a7058","blocked_count":2,"decided_at":"2026-11-02T05:37:46.230Z","decision":"review","disputed_pct":0.75,"findings_hash":"5eGzduX19JBWVB1a3rRg47raAgKj38iURoNGMEr3JjxZ","investigation_id":"34c018b1-ccde-499e-9f0d-f53bb4537f22","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":50,"page_content_hash":"8c6a182b5d1d36e16a33323d32b3db7f7a93fa4094de8b740333230954b067e1","page_slug":"growth-defi","prev_score":50,"reason":"The exploit narrative is broadly consistent with the REKT account, but the summary and timeline mislabel it as a 'flashloan price oracle' exploit. The page's own section describes a fake-token validation flaw. The attacker address, the 801 ETH total and the current TVL figure could not be verified because the primary sources blocked access. The ZachXBT section has no support. Few claims were independently checked, so this review is limited.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":4,"sequence_num":3,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}