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.

Decision
review · Harbor Protocol
View on Solana ↗
Sequence
#3
Score
50 → 50 (0)
Cluster
mainnet-beta
Slot
464289408
Off-chain at
2026-11-02T00:12:36.444Z
Anchored at
2026-11-02T00:13:05.000Z
Block time
2026-11-02T00:13:05.000Z

Independent verification

1. Database (off-chain)
5r4AaR8ZYCW29hxKkoS7dWkiYhqpSozstww1FswQPSLC
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1399 chars)
{"actor":"reviewer","artifact_identity":"b2f63ebe82bec9cc7fa96e9787a76dc3","blocked_count":1,"decided_at":"2026-11-02T00:12:36.372Z","decision":"review","disputed_pct":0.5,"findings_hash":"8v9Z7SJpCwdogL3HvRQoU6TPNPjtCC4hh2AgqQMA98Yh","investigation_id":"a95c7e99-75b1-4edf-bcf5-96d923ec7662","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":50,"omissions":{"material":0,"total":1},"page_content_hash":"45098991af49dcfa5b731fd159f2a02b5727f7d605adb0bcf4c4073044b8bacd","page_slug":"harbor-protocol","prev_score":50,"reason":"The core narrative holds: a June 2023 incident, an August 18-19, 2023 vault exploit with TVL falling from about $370k to $81k, and a later deprecated, zero-TVL protocol. Two attributions are unsupported by the cited sources. The DeDotFi and PeckShield 'confirmed unrelated' claim appears in the section text and the timeline, and the ZachXBT 'flagged' claim has no support either. The named attacker address and the June oracle mechanics could not be verified because the primary Comdex posts were unreachable.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":10,"sequence_num":3,"subject_status":"shut_down","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}