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 · EasyFi
- Sequence
- #3
- Score
- 55 → 55 (0)
- Cluster
- mainnet-beta
- Slot
- 464446644
- Off-chain at
- 2026-11-02T09:34:09.418Z
- Anchored at
- 2026-11-02T09:34:27.000Z
- Block time
- 2026-11-02T09:34:27.000Z
Independent verification
- 1. Database (off-chain)
- 85gHgs16LiS3o5nVarxADSNgVV9qc5skFymkb8aiw6Lt
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1325 chars)
{"actor":"reviewer","artifact_identity":"8a6c42d94e703f04cf5cdb2bf1374807","decided_at":"2026-11-02T09:34:09.352Z","decision":"review","disputed_pct":0.3636,"findings_hash":"7AZHX6537NeSt41KdZG3eKj5pZtm71niePwdhbKtkQSc","investigation_id":"791df2de-5786-4056-a92a-9f5c584c9057","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":55,"omissions":{"material":0,"total":1},"page_content_hash":"8cc1c6083de8c1f2e4b818b18121cbc4cfbb7f211497ead30ae4271008c4c4a0","page_slug":"easyfi","prev_score":55,"reason":"The core hack facts (date, amounts, method, attacker addresses, compensation terms, price figures) are corroborated by CoinDesk, Halborn, Cointelegraph and the Monahan repository. Problems are: the unsourced ZachXBT claim, the 123 BTC and Ren Bridge details, an unsourced timeline entry that conflicts with the Polygon description (BSC launch), the Halborn audit claim, and a one-day error in the compensation date. No shutdown or sanction was found, but the project looks dormant.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}