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 · Term Labs
- Sequence
- #2
- Score
- 22 → 22 (0)
- Cluster
- mainnet-beta
- Slot
- 443510640
- Off-chain at
- 2026-08-25T03:08:00.369Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- G4HfYo8xvqiC5aVSpy1XJsquNKfbgmJRSVqjyB9rBSu3
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1481 chars)
{"actor":"reviewer","decided_at":"2026-08-25T03:08:00.200Z","decision":"review","investigation_id":"28e9132f-6453-444b-94da-233ce895ed34","new_score":22,"page_slug":"term-labs","prev_score":22,"reason":"The page's claims are, on the whole, well-supported by both its cited sources and independent corroboration, particularly for the core facts of the August 2026 governance exploit and the April 2025 oracle incident (amounts, dates, mechanisms, recovery figures, and attributions all check out against multiple independent outlets). The main issues found were: a mischaracterization of the '$25.1 million across five 2026 governance incidents' statistic, which the page frames as occurring 'prior to' Term Labs and describes Term Labs' $8.5M as the largest single loss in the cluster — both contradicted by the underlying reporting, which counts Term Labs as one of the five constituent incidents and identifies the July 2026 BonkDAO exploit ($20M) as larger; a minor date discrepancy (April 26 vs. April 28, 2025) for the oracle incident across the page's own cited sources; an arithmetic overstatement understating the vault-operation interval (16 months claimed vs. ~19 months actual); and one claim (LP veto power) that is factually accurate per independent sources but not actually supported by the two sources the page cites for it.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}