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 · Eleven Finance
- Sequence
- #3
- Score
- 59 → 59 (0)
- Cluster
- mainnet-beta
- Slot
- 464448696
- Off-chain at
- 2026-11-02T09:41:36.767Z
- Anchored at
- 2026-11-02T09:41:48.000Z
- Block time
- 2026-11-02T09:41:48.000Z
Independent verification
- 1. Database (off-chain)
- CPytv2iVQD1bm2JYx7ySQUkBGyNNHnHL2JMuPzRVnPku
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1305 chars)
{"actor":"reviewer","artifact_identity":"9bf0d1eba14623b648e12162da08b88b","blocked_count":1,"decided_at":"2026-11-02T09:41:36.711Z","decision":"review","disputed_pct":0.25,"findings_hash":"CcJki6SjtxE773aWH6vT44oQh65Jcc4wJM7P4CjYT7vE","investigation_id":"f0fb353d-7225-4009-b497-c32fcb3f7b2d","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":59,"omissions":{"material":0,"total":1},"page_content_hash":"4cf2c5e89fdcae1f257793f739dd4b8ecfc709ea3801ab16709d305d1e9601b1","page_slug":"eleven-finance","prev_score":59,"reason":"The exploit narrative (emergencyBurn bug, flash loan, roughly $4.5M loss) is broadly supported by Rekt and secondary PeckShield coverage. The attacker address attribution is imprecise. The recovery and compensation figures could not be verified because the Medium sources were blocked. The ZachXBT section is openly hedged. Current status is unclear, with one aggregator suggesting the project was discontinued in 2022.","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}