@Lodemarkets

Rewards Season 1 is live: 4% of $LODE supply going to hook-pool LPs Starting tomorrow, 100% of protocol revenue permanently buys and burns $LODE, forever

$350,000 TVL, verified on DefiLlama $11,000 in protocol revenue since launch, on top of regular swap fees paid to LPs: the permissionless buyback program will be open soon, 100% revenue to buybacks Eighteen days live, revenue from day one The first 14 days ran a 50/50 split: half to the LODE treasury, half to LPs as a yield boost. The auction premium ramped from 0 → 1 → 10 BPS in shadow-to-live progression What LPs saw, measured against the equivalent vanilla Uniswap v4 pool, with auction on 10 BPS: ETH/USDC: APY boost +21% ETH/USDT: APY boost +28% Same liquidity, same pair, same fee tier, same safety as adding LP to a vanilla pool. The spread is LVR being recycled back to LPs instead of paid out to MEV arbitrage searchers in the form of stolen price impact. Auction BPS will be raised to the default 30 BPS today, and APY boost will increment with it Revenue scales with TVL. More TVL means more swap volume across the hook, which means more auction premium captured per block. LPs earn more, the protocol earns more, token value grows Next milestones: - Auction premium increasing to 30 BPS - Five new pools launching (high-cap pairs) - Rewards Season 1 begins to LP providers on any LODE hook pool - LODE Builder Program LPs in LODE hook pools earn three streams simultaneously: - Standard swap fees (identical to vanilla) - Auction premium (LVR captured at top of block) - $LODE emissions (boosted weight per pool) A three-stack yield on liquidity users were already going to provide At $500,000 TVL, the builder program activates. Any team can launch a hooked pool and earn LODE boost rewards on their pair. Anyone can build their own pool, the hook handles the LVR capture and the rewards routing The thesis is simple: - Uniswap v3 fees pay LPs - v4 hooks pay LPs and the protocol - LODE is the hook that keeps the lights on without taxing swappers: every basis point of revenue comes from arbitrage edge that already exists in the orderflow, not from real users Eighteen days, $350,000 TVL, $11,000 revenue, 830 auctions filled

LODE hooks TVL now tracked on @DefiLlama! 🎶 Search 'lode markets' in https://t.co/M6sLDSq18k https://t.co/wnPoQdApVP

$2.75b of @Uniswap LP TVL leaks LVR to arbitrageurs every year LODE captures it: 80% returns to LPs as APR boost on top of standard trading fees https://t.co/naAzVWuJnF https://t.co/pnhwQ7MInj

$LODE tokenomics & launch story The supply: 100M total, distributed according to docs: - 44% Protocol-owned liquidity: seeded into LODE/ETH pools at TGE - 38% Future emissions: 4-year linear locked - 8% Core Team: 12-month cliff, 36-month linear vest (4 year total) - 10% Treasury: governance-gated: >0.5%/qtr requires 5-day vote The burn loop: part of the captured premium from a LODE-hooked pool routes through the protocol vault. The vault accumulates revenue, then flushes to buy back $LODE on the open market and burns it. Builder pools stake 100K $LODE permanently, create their own pools, and earn part of the LVR generated At launch, team seeded an LP at $0.0008 in the LODE/ETH 1% pool. Single-side, 34M LODE, range $0.0008 → $0.008 We enabled an anti-sniper 500 BPS hook premium from launch. Snipers still hit (they always do), but the 500 BPS captured $20,700 in protocol revenue as they exited: every dump went through the burn loop. That revenue compounds into more $LODE burned The original range was too tight. Selling started right at launch instead of letting price discover. So we migrated. Removed the LP from the 1% pool and created a new LODE/ETH pool at 1.1% fee tier (same hook, different pool ID) New pool launched at $0.002, 2.5x the original launch price. Two-sided LP from treasury: 21M LODE + 11 ETH in range $0.0005 → infinite Currently, $LODE trades at 100 BPS premium, 100% of captured premium routes to the burn vault TWAP buyback contract running: 10 ETH from revenue deployed, slicing 0.1 ETH into $LODE buys. Each slice burns the LODE directly