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_revise · Rossen G. Iossifov
View on Solana ↗
Sequence
#3
Score
20 (-10)
Cluster
mainnet-beta
Slot
443521447
Off-chain at
2026-08-26T15:09:22.181Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
9EzssjiyPse3MYCNTTPFcJ2FN9vEwfcRXFxREuDmdKnm
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2329 chars)
{"actor":"judge","decided_at":"2026-08-26T15:09:21.798Z","decision":"review_revise","investigation_id":"d4b0f97d-daa2-452a-90ca-bfeba11c25d5","new_score":0,"page_slug":"rossen-g-iossifov","prev_score":2,"reason":"The raw disputed rate is low (2 of 30 claims, 6.67%), and the vast majority of the page holds up: the 2021 conviction, the AOAF fraud scheme details, restitution amount, the 2026 charges, and every quoted official statement (Duva, Parman, Holman) were checked against the primary DOJ release and match verbatim with correct attribution. However, one of the two disputed items is not a minor detail — it is the length of a named individual's prison sentence, and the page contradicts its own cited primary source. claim_findings[9] shows the page states Iossifov was 'sentenced to 111 months' at his January 2021 sentencing (sections[0] and timeline[0]), while the Sixth Circuit opinion the page itself cites, plus two independent contemporaneous 2021 reports, state the sentence imposed was 121 months. A separate, correctly-worded reference to '111 months' in the page summary (claim_findings[3]) describes his sentence status as of the 2026 charges, not the 2021 outcome, and was rightly confirmed — so this is one substantive error occurring in two places, not three. The review does not establish whether the 111-month figure reflects an undocumented sentence reduction sometime after the Sixth Circuit affirmed the original 121-month sentence in August 2022, or whether it is simply an error that has been carried into later reporting; no source in the review affirmatively documents a resentencing. What is established is the self-contradiction against the page's own citation, which is the more serious and certain defect regardless of how that second question resolves, and it justifies pulling this page out of a clean approval despite the low raw disputed percentage. Coverage gaps do not add further weight here: the 'current custody status' gap is a routine update-later note (the reviewer found no unreported developments to omit), and the 'sentence-length discrepancy' gap duplicates claim_findings[9] rather than surfacing an independent structural failure.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}