Github: https://github.com/ohMySol/eigen-auction Slides: Project Link: Demo Video: https://youtube.com/shorts/TvgSsjCK1Uw?feature=share
Problem / Background:
As a liquidity provider I am familiar with IL/LVR and toxic flow. Every time an arb bot pushes my pool back to fair value after a CEX price move, that profit comes out of my pocket - it's not a bug, it's how AMMs work.
The profit exists, someone is capturing it, and that someone could be the LPs themselves. Angstrom proved a great solution, but there was no production-ready implementation of this as a Uniswap V4 hook secured by EigenLayer restaking. So I built one.
EigenAuction is the first Uniswap V4 hook that turns LVR from a loss into a revenue with the help of EigenLayer AVS. Instead of arb bots extracting value from the pool, an EigenLayer-secured auction captures that value and routes it back to liquidity providers proportionally.
The hook also bundles user swap intents into the same atomic settlement, meaning regular users get executed at the post-arb price rather than a stale one. Any V4 pool can add this hook - it's a big improvement for any LP who is tired of subsidising arbitrageurs. Another unique feature is that I didn't build a separate network of nodes which will run this auction without any punishment for wrong auction result. Instead auction fairness is powered by restakers of EigenLayer and operators who have a financial motivation to provide correct auction results.
The hardest part was getting the reward distribution to work correctly inside Uniswap V4's flash accounting model. My first approach used V4's sync/settle flow to move the arb reward into the hook, but that caused CurrencyNotSettled reverts because V4 tracks every token movement and any imbalance at unlock exit is fatal. The fix - transferring the reward directly from the operator to the hook outside V4 accounting, before the swap - was non-obvious and took a lot of debugging.
The second major challenge was porting V3-style tick-outside accumulators into a V4 hook context, since V4 doesn't expose the same tick data structures V3 had internally. I had to maintain the accumulator state entirely in the hook's own storage and reason carefully about the order of tick crossing vs reward folding to keep the math consistent.
There was also a fun Solidity pragma clash: EigenLayer's IStrategy requires ^0.8.27 while Uniswap V4 locks at =0.8.26, which meant I had to carefully isolate the EigenLayer-facing interface to avoid pulling the incompatible pragma into the hook's compile unit.