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 · Rhea Lend
- Sequence
- #3
- Score
- 58 → 58 (0)
- Cluster
- mainnet-beta
- Slot
- 464298839
- Off-chain at
- 2026-11-02T00:46:25.414Z
- Anchored at
- 2026-11-02T00:46:51.000Z
- Block time
- 2026-11-02T00:46:51.000Z
Independent verification
- 1. Database (off-chain)
- 2ayHRjJEkt32kgPvnJVCKrnFmRtPSHpsDuvT4kAcXdLT
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1446 chars)
{"actor":"reviewer","artifact_identity":"12d2f00aeac8c16dfcecd8aa931fc4d1","blocked_count":1,"decided_at":"2026-11-02T00:46:25.343Z","decision":"review","disputed_pct":0.4444,"findings_hash":"67CbN4QacZYos4T3d6vmjPGWY7VKzDTHToBQwFx1ucPa","investigation_id":"9b3955d1-a1de-427d-bfb0-14671152301d","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":58,"omissions":{"material":1,"total":2},"page_content_hash":"107a9db580b52db057e67c39e98ef5400d892b3165645ddc0f9b1762e577ab76","page_slug":"rhea-lend","prev_score":58,"reason":"The core exploit narrative is well supported: the April 16, 2026 date, the $18.4M loss revised from $7.6M, the April 13-15 preparation, the 423 wallets and the recovery figures all match The Block and Coin Edition. Problems are the attribution of the flaw's identification to Halborn, the unsupported claim that the exploited code passed a BlockSec April 2025 audit (not listed on the audits page), the inconsistent February and March merger dates, and stale status as of November 2026. Sampled sources were mostly secondary and not all cited URLs were fetched.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":9,"sequence_num":3,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}