Shadow Exchange Legacy
Shadow Exchange Legacy consists of volatile and stable AMM pairs deployed only on Sonic. Every LP mint, swap, gauge reward and withdrawal therefore depends on an unapproved Sonic settlement perimeter. The version-1 rejected-chain dossier is decisive regardless of the approximately $1.28M observed on 2026-08-15; AMM inventory loss remains an additional constraint if the product ever reaches an approved chain.
- The Sonic chain verdict changes or an economically separate Shadow product deploys on an approved chain
- Any reopened LP product passes exact-pool, authority, audit, incident, AMM-loss and proposed-size removal review
Watched nightly: a warning on its venues or files, or a cited document that changes, reopens the memo. The first confirmation is due 2026-11-15.
The research file
Mechanism and chain applicability
Shadow documents its Legacy Liquidity product as Sonic-native volatile Uniswap-v2-style pairs and correlated stable pairs. LPs hold fungible pair tokens and can stake whitelisted pairs in gauges for emissions. All pair reserves, swaps, rewards and removals are Sonic contracts, directly meeting the shared v1 rejected-chain dossier.
Current observation and lifecycle
The DefiLlama protocol API read on 2026-08-15 reported approximately $1.28M entirely on Sonic and still classified Shadow Exchange Legacy as a DEX. Current Shadow documentation retains a dedicated Legacy Liquidity page alongside concentrated liquidity, and the adapter methodology counts tokens locked in legacy pools. This is a live legacy perimeter, not a historical record silently merged into V3.
Control, loss and exit applicability
Legacy pool contracts hold paired reserves and return the post-trade asset mix at withdrawal. Shadow documents adjustable swap fees, gauge whitelist and kill or revive controls, and immutable permissionless pools. Those controls and the volatile or stable curve matter after chain review; none removes reliance on Sonic execution, gas, validators or current chain access.
Why the class rule decides
No observed legacy position can mint, earn or exit outside Sonic. The shared v1 rejected-chain dossier therefore controls before AMM quality or size. Reopen only if Sonic passes adviser review or an economically separate Shadow product deploys on an approved chain; any reopened LP product must still pass exact-pool authority, audit, incident, impermanent-loss and proposed-size removal tests.
Class rule
The rejected chain class is outside the approved structures, so every protocol in it is not approved until the rule changes. The rule is about the structure, not an adverse finding about this protocol, and it is not a client instruction. The events that would reopen it are listed with the memo.
Sources
The claims above trace to these. Where a number could not be independently verified, the thesis says so.
- Shadow — Legacy Liquidity mechanics · primary · accessed 2026-08-15
Supports: Sonic, legacy pairs, volatile curve, stable curve, LP tokens, gauges - Shadow — Sonic-native protocol overview · primary · accessed 2026-08-15
Supports: Sonic deployment, current lifecycle, liquidity exchange - Shadow — pool authority and audit design · primary · accessed 2026-08-15
Supports: legacy pool immutability, access control, fee setter, gauge controls, audits - Shadow — Sonic onboarding · primary · accessed 2026-08-15
Supports: Sonic-only access, S gas, wallet transactions, current onboarding - DefiLlama — Shadow Exchange Legacy survey record · secondary · accessed 2026-08-15
Supports: current TVL, Sonic-only perimeter, legacy lifecycle, Dexs category
Inherited controls
The research above describes the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The layer with the most administrative power sets the position’s effective control; that describes control, not quality or suitability.
| Chain | Verdict | Control | Control constraint |
|---|