Summary: Shadow Exchange is best understood less as a generic Sonic DEX and more as a Ramses-descended attempt to replace lock-based ve(3,3) governance with a more liquid, penalty-and-wrapper-driven x(3,3) system. Its primary materials explicitly present Shadow as a concentrated-liquidity layer powered by x(3,3), where governance power sits in non-transferable xSHADOW, exits are possible at a cost, protocol fees flow to active stakers rather than LPs by default, and liquid-staked / auto-voting wrappers such as $x33 become likely default vote routers.
What it does:
Runs a Sonic-native concentrated-liquidity exchange with multiple fee tiers and orderbook-style liquidity ranges
Lets users convert SHADOW into non-transferable xSHADOW, which votes weekly on emission direction and earns fees, vote incentives, and exit-penalty rebases
Offers immediate or vesting-based exits from xSHADOW, replacing hard lockups with explicit penalty schedules
Provides a liquid-staked governance wrapper, $x33, that auto-votes, auto-claims, auto-compounds, and increases its ratio against xSHADOW over time
Routes default gauge fees to governance participants rather than LPs, while also supporting configurable fee-split variants for certain pools
Uses dynamic fees, privileged MEV infrastructure, and Sonic FeeM gas refunds to internalize execution value and feed it back into the protocol economy
Key claims:
The docs homepage and GitHub repo frame Shadow as a concentrated-liquidity layer and exchange on Sonic powered by x(3,3), and the core-contract repo says it is built on Ramses V3 Core with enhancements such as dynamic fees, FeeShare, and x(3,3)
The x(3,3) explainer says the protocol is trying to fix a core ve(3,3) problem — dead, locked governance power without an exit path — by letting users leave at any time while redistributing forfeited value to remaining participants
The xSHADOW docs say holders earn 100% of protocol fees, vote incentives, and exit penalties, but only if they are actively staked and vote during the epoch, which makes participation requirements part of the control surface
Those same docs say instant exit returns only half of the underlying value and that vesting periods up to 180 days are required for a full 1:1 redemption, showing Shadow swaps fixed lockups for flexible but punitive redemption economics
The x(3,3) docs say 100% of forfeited exit value is streamed to xSHADOW stakers as a “PVP Rebase,” making dilution protection and churn monetization the same mechanism rather than separate systems
The concentrated-liquidity docs frame Shadow as an orderbook-style AMM optimized for performant LPs and competitive farming, with tighter ranges earning more rewards and default CL-pool fees going 100% to xSHADOW voters rather than LPs
The xSHADOW and x(3,3) docs say emissions are directed weekly by voters and that voters receive swap fees plus vote incentives at epoch flip, making governance power directly monetizable in the familiar gauge-market style
The docs also claim Shadow’s dynamic fees can update as frequently as every 30 seconds and that MEV / arbitrage capture plus Sonic FeeM refunds help route extra value back into the ecosystem, meaning protocol revenue depends partly on privileged execution infrastructure rather than only on open AMM usage
$x33 is analytically important because the docs present it as an auto-voting, auto-compounding liquid wrapper with no deposit/withdraw fees; if it becomes the default interface, practical vote-routing power may concentrate in wrapper logic rather than in many direct voters
Whitepaper: No canonical standalone whitepaper or litepaper surfaced in this pass. The strongest primary materials were the official docs for x(3,3), xSHADOW, and concentrated liquidity plus the public core-contract repository; see ../whitepapers/shadow-exchange-primary-sources-2026-05-07.md.