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
#4
Score
10 → 26 (+16)
Cluster
mainnet-beta
Slot
455357478
Off-chain at
2026-10-10T18:39:33.597Z
Anchored at
2026-10-10T18:40:32.091Z
Block time
—

Independent verification

1. Database (off-chain)
5xUpKDBexA9mU4fuib5QiCVS1asxFhpFxJYV5MbGvQo3
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (892 chars)
{"actor":"system","decided_at":"2026-10-10T18:39:33.489Z","decision":"rescore","investigation_id":"0ffbfa7c-6f53-4b54-9379-116f5a65d8f5","new_score":26,"page_slug":"mantra-chain","prev_score":10,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 10 → 26. Problems weighed by who is responsible: incidents the subject suffered −20, concerns that are not fraud −12, problems around the subject, caused by others −2.3; legitimacy credit long-running +4; no established finding that it defrauded anyone, so it stays out of the red band; the penalty for incidents it suffered is capped at 20; a recent unresolved incident −22.4; fact-check adjustments (−12) now shown as page reliability, not in the score.","score_delta":16,"score_model":"v2","sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}