Shadow Exchange primary sources — 2026-05-07

Project

• Name: Shadow Exchange
• URL: https://www.shadow.so/
• Category: concentrated-liquidity DEX / x(3,3) governance market / liquid-staked vote-routing layer / MEV-capture routing layer
• Whitepaper status: No canonical standalone whitepaper or litepaper surfaced in this pass.

Primary sources reviewed

1. x(3,3) explainer: https://docs.shadow.so/pages/x-33

   • Says Shadow replaces forced ve-style lockups with stronger incentives and an explicit exit mechanism.
   • Describes the core loop: xSHADOW holders vote on weekly emissions, earn fees and incentives, and receive streamed value from early exits.
   • Says protocol fees and MEV revenue flow to xSHADOW holders, not just to LPs.

2. xSHADOW page: https://docs.shadow.so/pages/xshadow

   • Defines xSHADOW as a non-transferable escrow token representing SHADOW held in the xSHADOW contract.
   • Says holders can exit instantly with a 50% penalty or vest out over as long as 180 days for full redemption.
   • Says only active stakers who vote receive all weekly rewards.
   • Describes $x33 as a liquid-staked, auto-voting, auto-compounding wrapper whose ratio against xSHADOW rises as rewards accrue.

3. Concentrated-liquidity page: https://docs.shadow.so/pages/concentrated-liquidity

   • Frames Shadow as an orderbook-style AMM built around concentrated liquidity and competitive farming.
   • Says default CL swap-fee distribution is 100% to xSHADOW voters.
   • Shows that LP productivity, routing depth, and governance-directed incentives are tightly coupled.

4. Voting page: https://docs.shadow.so/pages/voting

   • Confirms weekly epoch timing and reset cadence (Thursday 00:00 UTC).
   • Even though the page is still sparse, it reinforces that epoch timing is part of the operating model and that voting behavior is reward-sensitive.

5. Core contracts repo: https://github.com/Shadow-Exchange/shadow-core

   • Says Shadow is built on Ramses V3 Core, itself based on Uniswap V3, with enhancements including dynamic fees, FeeShare, and x(3,3).
   • Links audit surfaces including Spearbit, Consensys Diligence, and Code4rena, plus additional specialized testing.
   • Notes that some governance-critical contracts such as Voter.sol, GaugeV3.sol, and FeeDistributor.sol are BUSL-protected.

6. GitHub organization: https://github.com/Shadow-Exchange

   • Corroborates that Shadow is maintaining a broader code footprint rather than only a marketing site.

Mechanism takeaways

• Shadow is a useful descendant in the Solidly / Ramses family because it mutates the lock-based governance flywheel in a specific direction: away from fixed-duration veNFTs and toward non-transferable staking plus liquid wrappers and punitive exits.
• The exit mechanism matters analytically. Rather than trapping users in long lockups, Shadow makes churn costly and recycles that cost back to remaining participants. That turns liquidity preference itself into a yield source for incumbents.
• $x33 may be the most important control surface in practice. If users prefer the wrapper over direct weekly voting, governance power and reward routing can concentrate in auto-voting logic and wrapper operators rather than in many separate holders.
• Shadow also pushes the fee sink farther toward governance participants than many CLMMs do: default CL fees go to xSHADOW voters, while LPs are rewarded more through emissions / productivity and optional custom fee splits.
• The MEV and FeeM pieces matter because protocol revenue is not only swap-volume dependent. Shadow is trying to internalize arbitrage and gas-refund economics into the same governance flywheel.

Why this stays in the active corpus

• It strengthens the x(3,3) comparison set beyond Ramses by showing another live implementation with a slightly different governance / revenue stack.
• It is a good case for reasoning about when liquid governance wrappers become the real vote routers.
• It helps compare how concentrated-liquidity markets change when fee routing, MEV capture, exit penalties, and auto-compounding wrappers are bundled into one protocol economy.