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 · Makina Finance
- Sequence
- #3
- Score
- 38 → 24 (-14)
- Cluster
- mainnet-beta
- Slot
- 443523575
- Off-chain at
- 2026-08-27T04:01:07.730Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- F1ccgvADvbyTWJZ5Bn7nAKBhBgcCTL481Yk9oXWwtQhh
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2455 chars)
{"actor":"judge","decided_at":"2026-08-27T04:01:07.216Z","decision":"review_revise","investigation_id":"ae5806de-d332-4745-a0b1-3e6eae151833","new_score":24,"page_slug":"makina-finance","prev_score":38,"reason":"Independently recomputing from the 24 claim findings (17 confirmed, 2 partially_supported, 4 disputed, 1 unverifiable, 0 stale, 0 link_rot) gives a disputed+unverifiable rate of 5/24 = 20.8%, placing this page in the minor-to-moderate revision band rather than triggering a formal investigation or delisting. The page's central story -- the January 20, 2026 oracle-manipulation exploit, its $4.13M loss, flash-loan mechanics, six prior audits, MEV interception and remediation -- is precisely corroborated across independent security researchers and the protocol's own statements (claim_findings[9],[10],[11],[13],[14],[15],[16],[17],[18],[20],[21]), which anchors confidence that this is a real, accurately-documented incident rather than fabricated content. That said, the page places a real, identifiable person, Sath Ganesarajah, in a chairman role at Makina that regulatory filings show he actually held at an unrelated company, Bluebird Mining Ventures (claim_findings[7]) -- this is weighed as more serious than an ordinary factual slip because it attaches a specific person's name and title to the wrong company, and is compounded by a related coverage gap noting the page never names Makina's real leadership. That combination pushes the penalty to the top of this band even though the overall dispute rate is moderate. Two further errors are noted but carry less weight: the stated launch date does not match Makina's own launch announcements (claim_findings[4]), and the page incorrectly says no post-mortem had been published when one existed since February 2026 (claim_findings[22]) -- notably, this second error understates rather than overstates the protocol's transparency, which is taken as a sign of an incomplete search rather than a one-sided negative slant. A mismatched MEV address and a partially-supported angel-investor list (claim_findings[6],[12]) are minor by comparison. The reviewer's stated confidence of 0.78 supports treating these as genuine, checkable defects rather than reviewer uncertainty, so the page is sent back for correction rather than escalated further.","score_delta":-14,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}