How did you integrate our partners, if any?

Reactive Network. A ShieldReactiveController (Lasna RSC) subscribes to Reactive CRON and, on each tick, sends an authenticated cross-chain callback through the chain callback proxy to a ShieldReactiveExecutor on Base, which calls the hook's bounded triggerQuietDrip() to release stranded LP reserve via Uniswap v4 donate() — no keeper, no bot. Two-factor callback auth (callback-proxy msg.sender + locked rvm_id). Verified live on Base Sepolia ← Reactive Lasna: tx 0x7a2b6afb30e436f9da3b1bc3dde55bc5f549654443b96fc681a029313ebed71f (block 42275501).

What are the key links to share? (Ex. demo video, GitHub, deck)

Github: https://github.com/Hebx/EvenFlow Slides: https://canva.link/ohh3e99jzlp1p3i Project Link: Demo Video: https://www.loom.com/share/4186f27292ca42eaa82ff685fb49214c

Problem / Background: What inspired the idea? What problems are you solving?

Passive LPs lose to informed, one-directional flow, and even a good defensive fee leaves realized yield lumpy — fat during toxic bursts, thin when quiet — with surplus value stranded in the pool. We wanted to price toxicity honestly without an oracle AND turn that surplus into a smoother LP payout, then solve the last-mile problem that the surplus stays stranded when nobody swaps.

Impact: What makes this project unique? What impact will this make?

Three composable layers, each optional above the base: (1) an oracle-free directional fee that funds a reserve, (2) opt-in ERC-6909 smoothing that captures the toxicity premium and drips it back to in-range LPs via canonical donate() with wei-exact conservation, and (3) a Reactive Network cron that releases stranded reserve cross-chain with no keeper. On burst-then-quiet flow, per-step yield variance drops ~61% (2.5× tighter) at conserved total yield. Every claim is backed by an explorer-verifiable tx (real Base mainnet-fork PoolManager + live Base Sepolia + a live Lasna→Base reactive drip).

Challenges: What was challenging about building this project?

Making custody honest: capture→escrow→drip had to conserve value exactly (captured == dripped + remaining to the wei) and stay opt-in so the default path holds no funds.

Keeping Reactive off the per-swap hot path while still being the thing that makes smoothing work in an idle pool.

Reactive callback security: moved from a spoofable injected-address check to two-factor auth (callback proxy msg.sender + locked rvm_id), and a set-once controller to break the executor⇄controller mutual-address deploy dependency.

Proving it for real: driving a genuine cron-triggered cross-chain drip on testnet, not a mock.