Skip to main content
AVOID.NET
Sign in
← 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 · Fluid (Instadapp)
View on Solana ↗
Sequence
#2
Score
52 → 52 (0)
Cluster
mainnet-beta
Slot
443512652
Off-chain at
2026-08-25T08:04:10.950Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
Fe9S4t1hJQE7HNsp5tCsc7LhcXGG93EztcpUomLjeBbL
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1036 chars)
{"actor":"reviewer","decided_at":"2026-08-25T08:04:10.844Z","decision":"review","investigation_id":"e2cde9dd-d0ba-45e1-8daa-fb77b6e8957e","new_score":52,"page_slug":"fluid-instadapp","prev_score":52,"reason":"The page's account of the two 2026 security incidents (May Merkle key compromise, March Resolv bad-debt event) and the Instadapp-to-Fluid rebrand is well supported by convergent independent reporting and a primary governance source. However, the total funding figure ($24.5M) is disputed by consistent independent funding-database records showing $12.4M, the December 2024 Statemind audit attribution does not match Statemind's own public audit record (likely conflated with a MixBytes December 2024 audit), and several quantitative figures (TVL, fees, revenue, circulating supply) are stale relative to current live source data, understating the protocol's current TVL by roughly 20%.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}