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 · Euler V1
- Sequence
- #4
- Score
- 59 → 59 (0)
- Cluster
- mainnet-beta
- Slot
- 464365999
- Off-chain at
- 2026-11-02T04:46:17.322Z
- Anchored at
- 2026-11-02T04:46:45.000Z
- Block time
- 2026-11-02T04:46:45.000Z
Independent verification
- 1. Database (off-chain)
- DWK6sNLpaEA5rFmwv8FouL23Pn9WumxJ5bjAEME1R64D
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1409 chars)
{"actor":"judge","artifact_identity":"966888a299716b7944a583c341a139a4","band_override":null,"blocked_count":2,"decided_at":"2026-11-02T04:46:17.099Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1667,"investigation_id":"f33e91a4-0b1f-4ec9-925b-da21e05a4068","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":59,"page_slug":"euler-v1","prev_score":59,"reason":"The core facts hold up: the March 13, 2023 exploit of about $197M, the staged fund returns, and the September 2024 V2 launch were confirmed (claim_findings[0], [1], [2]). The EUL allocation percentages (claim_findings[6]) could not be verified. Two further claims were not checked because their sources blocked the reviewer, so they are a coverage limit rather than a defect. After excluding those two, 1 of 6 checked claims is unverifiable (about 17%), which puts the page in the minor-issues band. Two claims were only partly supported: the founding year is loosely stated, and the Bentley departure has no date. The reviewer's confidence is low (0.5) and most cited URLs were not fetched, so the penalty is kept at the mild end.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":6,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}