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
#2
Score
28 → 28 (0)
Cluster
mainnet-beta
Slot
462280458
Off-chain at
2026-10-28T00:52:42.660Z
Anchored at
2026-10-28T00:53:17.000Z
Block time
2026-10-28T00:53:17.000Z

Independent verification

1. Database (off-chain)
2EZXAyKY7Gdyaojctj63maBt2nndXcu4FyUxKohXMdrP
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1412 chars)
{"actor":"reviewer","artifact_identity":"4f03a078d5c5c7b1fccd81be58d7c8f5","decided_at":"2026-10-28T00:52:42.590Z","decision":"review","disputed_pct":0.2857,"findings_hash":"HNKhp7gJCYQZbnGFDTLs2EXBp2CGFVoLPzVrccqfrjPV","investigation_id":"4b284321-bf69-460c-b1be-6eefc3b247c2","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":28,"omissions":{"material":0,"total":1},"page_content_hash":"db6abdb245eccd05aedf1c166b60a0c3adcd9dbb4170e3638243e73e2099d4b9","page_slug":"renzo-protocol","prev_score":28,"reason":"The core depeg and liquidation figures, and the Code4rena counts and dates, are well supported by DL News and Code4rena. Two problems stand out: the audit is described as 'concurrent' with the depeg although it began six days later, and the November 5, 2025 / 114 million REZ burn figures are not supported by the cited governance thread, which points to an ~100M REZ buyback in October 2025. The page also omits the reported September 2026 rebrand to Renzo Finance. No shutdown, exploit or sanction was found. Many other claims were not individually fetched.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":2,"subject_status":"rebranded","subject_status_contradicts_page":true,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}