Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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
#5
Score
28 → 28 (0)
Cluster
mainnet-beta
Slot
464285778
Off-chain at
2026-11-01T23:59:46.151Z
Anchored at
2026-11-02T00:00:11.000Z
Block time
2026-11-02T00:00:11.000Z

Independent verification

1. Database (off-chain)
3W6uHYrp8Hq2Zf2yDsNtvKBSbLy4DeVE8mDvM9Fbj8ph
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1488 chars)
{"actor":"reviewer","artifact_identity":"3e0bed51ae8b8a5dfd03312cd0ed6b67","blocked_count":1,"decided_at":"2026-11-01T23:59:46.048Z","decision":"review","disputed_pct":0.2222,"findings_hash":"DE2A2WvffqnbhWckn6V4is8UpAdAw8gcKGQ8caa2e97","investigation_id":"b1f3fb25-5fcd-4377-b433-917b184e949e","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":28,"page_content_hash":"58ca125b8b5bb7beae0bdedcecc205e0090cfdac8a49a406a1bbd6e6c4d1cad3","page_slug":"pike-finance","prev_score":28,"reason":"The core incident narrative (two exploits on April 26 and 30, 2024, ~$1.98M combined, OtterSec warning, Pike's retraction of the 'USDC vulnerability' framing, thin-liquidity token launch) is supported by Protos and The Block. Weaker points are the February 2024 mainnet date attributed to Protos, the reimbursement mechanics (4% collateral, $2M) not found in the cited Protos piece, the specific Halborn/CertiK testing claims, and the October timing of the TGE, which may have been September 30. Review sampled only about ten claims and did not fetch CertiK, Merkle Science, Quadriga or Pike's own pages. No shutdown or new exploit found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":9,"sequence_num":5,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}