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_revise · dTRINITY dLEND
- Sequence
- #10
- Score
- 35 → 42 (+7)
- Cluster
- mainnet-beta
- Slot
- 464653087
- Off-chain at
- 2026-11-02T21:52:04.128Z
- Anchored at
- 2026-11-02T21:52:24.000Z
- Block time
- 2026-11-02T21:52:24.000Z
Independent verification
- 1. Database (off-chain)
- 7qZbWs3qinx2r3GGv6YMphKmuJ7RP44AjebskBSDgDje
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1646 chars)
{"actor":"judge","artifact_identity":"427bc784c1a687a743e36c03cec71b36","band_override":null,"blocked_count":2,"decided_at":"2026-11-02T21:52:03.832Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2857,"investigation_id":"32a844a0-4b60-4c3c-9c8c-06ae37b7387e","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":42,"page_slug":"dtrinity-dlend","prev_score":35,"reason":"Both security incident narratives (September 2025 approval abuse and March 2026 deposit inflation) were confirmed against Revoke.cash, Verichains and ChainCatcher, and no claim was disputed. Two of seven checkable claims could not be verified: the SlowMist citation points to an EOS DApp category page that does not appear to match (claim_findings[1]), and the BeInCrypto sector statistics were not found (claim_findings[8]), giving roughly 29% unverified. Two further claims (Cyberscope listing, December 2024 press release) were excluded because the sources blocked the reviewer, which limits coverage but is not a defect of the page. A high-priority gap remains: the page lacks dTRINITY's own post-mortems and an official status update on the Ethereum market, so a small penalty applies.","replaces_fact_checks":{"score_before_fact_checks":52,"undone":2},"reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":7,"score_limit":{"applied":-10,"limited":false,"proposed":-10,"rule":"second_opinion_agreed","second":-10},"scored_claims":7,"sequence_num":10,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}