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.
- Sequence
- #2
- Score
- 22 → 22 (0)
- Cluster
- mainnet-beta
- Slot
- 443521276
- Off-chain at
- 2026-08-26T14:09:29.978Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- GNiNKdoKoEuR8AQfsPM2xu7UvqmNEbeqm85bNfeBHP2u
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1484 chars)
{"actor":"reviewer","decided_at":"2026-08-26T14:09:29.800Z","decision":"review","investigation_id":"b67351d6-4938-413c-aa54-0ba5284676b1","new_score":22,"page_slug":"ostium-protocol-oracle-signer-key-compromise-july-2026","prev_score":22,"reason":"The bulk of the page's factual content -- the loss amount, transaction/contract addresses, attack timeline, audit-gap history, and post-exploit remediation steps -- is well corroborated by multiple independent sources and, in several places, directly by Ostium's own statements. However, the page's central, slug-defining technical claim -- that a signer PRIVATE KEY specifically was compromised -- goes beyond what Ostium's own post-mortem states; Ostium's own language describes only a compromise of unspecified 'off-chain infrastructure,' and two credible technical outlets (rekt.news, DeFi Prime) explicitly say the precise mechanism remains unconfirmed even after the post-mortem. The page also contains a recurring internal arithmetic error (stating 10,540/12,084 ETH as ~83% when it computes to ~87%, and a $4 million residual that does not reconcile with its own printed figures), an unverified attribution to 'Galaxy Research,' and an unsupported 'second-largest exploit of July 2026' ranking that is contradicted by other July 2026 incidents (AFX Bridge, Coldcard) reported as larger.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}