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 · Fusion by IPOR
- Sequence
- #2
- Score
- 52 → 52 (0)
- Cluster
- mainnet-beta
- Slot
- 425437316
- Off-chain at
- 2026-06-10T00:33:10.970Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 9EdtsYzoz74ERCDfZirGqnN8SZarXgCb8Xts8DFT24Ek
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (989 chars)
{"actor":"reviewer","decided_at":"2026-06-10T00:33:10.788Z","decision":"review","investigation_id":"610e5c95-082e-484a-843b-84925eef4194","new_score":52,"page_slug":"fusion-by-ipor","prev_score":52,"reason":"The page's core factual claims — exploit date, amount, technical mechanism, Tornado Cash routing, SEAL engagement, and DAO compensation commitment — are well-supported by multiple independent sources. The most significant factual error is the vault deployment date (listed as 2024-01-01 but arithmetically inconsistent with the '490 days' figure, which points to approximately August 2024). The ZachXBT attribution is not corroborated by any consulted source and should be considered unverifiable. Several docs.ipor.io citation URLs are dead (link rot), and the Ackee audit timeline entry overstates the finality of the July 28, 2023 date.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}