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
publish · Aperture LM
- Sequence
- #1
- Score
- →
- Cluster
- mainnet-beta
- Slot
- 422349734
- Off-chain at
- 2026-05-26T19:42:47.860Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- FTzjepKoBAvTJxazxhMXuUYCm4BUQehfBdcc5mfRNqsf
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (6416 chars)
{"actor":"system:backfill","investigation_id":"012e009b-3cec-4ec2-9443-5a1873c079ce","kind":"publish","page_slug":"aperture-lm","published_at":"2026-05-26T19:42:47.797Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"Aperture LM","sections":[{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://blocksec.com/blog/17m-closed-source-smart-contract-exploit-arbitrary-call-swapnet-aperture","type":"other","url":""},{"credibility":3,"name":"https://coinpedia.org/news/defi-hack-alert-aperture-finance-smart-contract-exploit-suffers-3-67m-loss/","type":"other","url":""},{"credibility":3,"name":"https://blog.solidityscan.com/aperture-finance-hack-analysis-22dca439ff33","type":"other","url":""},{"credibility":3,"name":"https://coinfomania.com/aperture-finance-reports-exploit-and-urges-users-to-revoke-access/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://blog.amlbot.com/13-5m-lost-in-aperture-finance-swapnet-exploit-full-on-chain-breakdown/","type":"other","url":""},{"credibility":3,"name":"https://www.mexc.com/news/643634","type":"other","url":""},{"credibility":3,"name":"https://coinpedia.org/news/defi-hack-alert-aperture-finance-smart-contract-exploit-suffers-3-67m-loss/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://docs.aperture.finance/docs/transparency/security-audit","type":"other","url":""},{"credibility":3,"name":"https://blog.solidityscan.com/aperture-finance-hack-analysis-22dca439ff33","type":"other","url":""},{"credibility":3,"name":"https://blocksec.com/blog/17m-closed-source-smart-contract-exploit-arbitrary-call-swapnet-aperture","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://x.com/ApertureFinance/status/2015938720453820752","type":"other","url":""},{"credibility":3,"name":"https://coinfomania.com/aperture-finance-reports-exploit-and-urges-users-to-revoke-access/","type":"other","url":""},{"credibility":3,"name":"https://cryptoadventure.com/aperture-finance-reports-v3-v4-contract-exploit-halts-front-end-functions/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://coinmarketcap.com/currencies/aperture-finance/","type":"other","url":""},{"credibility":3,"name":"https://alphagrowth.io/aperture-lm","type":"other","url":""},{"credibility":3,"name":"https://medium.com/@aperturefinance/aperture-finance-aptr-fca15735d698","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://defillama.com/protocol/aperture-finance","type":"other","url":""},{"credibility":3,"name":"https://coinmarketcap.com/academy/article/what-is-aperture-finance","type":"other","url":""},{"credibility":3,"name":"https://alphagrowth.io/aperture-lm","type":"other","url":""},{"credibility":3,"name":"https://chainbroker.io/projects/aperture-finance/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://zachxbt.mirror.xyz/","type":"other","url":""},{"credibility":3,"name":"https://blocksec.com/blog/17m-closed-source-smart-contract-exploit-arbitrary-call-swapnet-aperture","type":"other","url":""},{"credibility":3,"name":"https://coinpedia.org/news/defi-hack-alert-aperture-finance-smart-contract-exploit-suffers-3-67m-loss/","type":"other","url":""}]}],"sources_used":[],"summary":"Aperture LM (also marketed as Aperture Finance) is a multi-chain DeFi liquidity management protocol that launched in 2022 and raised $12 million at a reported $250 million valuation. On January 25, 2026, the protocol suffered a critical smart contract exploit due to insufficient input validation in its V3 and V4 helper modules, resulting in $3.67 million stolen from Aperture directly and contributing to a combined ~$17 million loss across a coordinated attack that also hit SwapNet. Stolen funds were laundered through Tornado Cash, no public compensation plan for affected users has been confirmed, and the protocol's closed-source contract architecture was identified as a compounding risk factor that hindered independent security review.","timeline":[{"date":"2022-01-01","event":"Aperture Finance founded; initial audit of Terra DNS module by Oak Security completed March 2022.","source":""},{"date":"2022-08-01","event":"Oak Security/Solidified audit of Avalanche PDN Strategies completed September 2022.","source":""},{"date":"2023-05-08","event":"First Narya.ai audit of UniV3 automation contracts completed.","source":""},{"date":"2023-07-03","event":"Second Narya.ai audit of UniV3 automation contracts completed.","source":""},{"date":"2023-09-29","event":"Veridise audit of UniV3 fork deployment completed — last documented audit on record.","source":""},{"date":"2024-05-31","event":"APTR token officially launched on Ethereum, Arbitrum, and Mantle Network.","source":""},{"date":"2024-06-10","event":"APTR token reaches all-time high of approximately $0.12497.","source":""},{"date":"2025-12-31","event":"APTR token ends 2025 down approximately 99.25% year-over-year, trading near $0.00005.","source":""},{"date":"2026-01-25","event":"Arbitrary-call vulnerability in Aperture Finance V3/V4 helper module exploited across Ethereum, Arbitrum, Base, and BNB Chain; $3.67 million stolen. Same attacker simultaneously exploits SwapNet for ~$13.4 million; combined losses reach ~$17 million. Exploit first flagged by PeckShield.","source":""},{"date":"2026-01-25","event":"Aperture Finance halts frontend functions, issues emergency advisory urging users to revoke approvals for contract 0xD83d960deBEC397fB149b51F8F37DD3B5CFA8913.","source":""},{"date":"2026-01-27","event":"Attacker deposits approximately 1,242.7 ETH (~$2.4 million) into Tornado Cash in structured batches. AMLBot publishes initial on-chain findings.","source":""},{"date":"2026-01-28","event":"BlockSec publishes detailed technical analysis of both the Aperture Finance and SwapNet exploits, attributing root cause to insufficient input validation in closed-source contracts.","source":""},{"date":"2026-02-03","event":"AMLBot publishes full on-chain forensic breakdown; secondary attacker linked to Li.Fi/Jumper Exchange exploiter network.","source":""}]},"v":1}