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 · Lodestar Finance
- Sequence
- #2
- Score
- 32 → 32 (0)
- Cluster
- mainnet-beta
- Slot
- 424312459
- Off-chain at
- 2026-06-04T20:05:47.583Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 7PzbhNuDkfMkJqowoZKDkQb5aiHuvZMjTohQhfatsQG6
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (884 chars)
{"actor":"reviewer","decided_at":"2026-06-04T20:05:47.391Z","decision":"review","investigation_id":"9f16c147-d747-4bcb-ad79-43f72fbaf199","new_score":32,"page_slug":"lodestar-finance","prev_score":32,"reason":"The page is broadly accurate in its account of the December 2022 exploit, its mechanism, and the aftermath. However, it contains a material factual error in the Pre-Exploit Audit section: the SourceHat pre-exploit audit DID flag the GLPOracle vulnerability as a High severity finding, and the '18 medium + 2 gas' finding counts belong to the post-exploit Hats Finance competition rather than the SourceHat audit. One CoinTelegraph citation is dead (404). These errors are significant enough to require correction before publication.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}