How did you integrate our partners, if any?

We integrated Unichain Sepolia as the live testnet environment for BondMeBro. The Uniswap v4 hook, demo pool, frontend, live swaps, bond settlement, and refund/slash flows were all deployed and tested on Unichain Sepolia, including a live full-refund case and persistent-displacement slash cases.

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

Github: https://github.com/Maheshsiddu29/BondMeBro.git Slides: https://docs.google.com/presentation/d/18HNsiX-BY63LW_QIlSOpWv8NY-m9InhPLPJ9jzJ-Bpc/edit?usp=sharing Project Link: https://bondmebro.vercel.app/ Demo Video: https://drive.google.com/file/d/115B94nw7YoaprY5GRypYfk-2sMdHdDbL/view?usp=sharing

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

BondMeBro was inspired by the problem of LP adverse selection and LVR in AMMs. A high-impact trade can move the pool price significantly, but at execution time it is difficult to know whether that move is temporary or whether it reflects persistent information that leaves LPs exposed.

We wanted to avoid simply charging every large trade a permanently higher fee. BondMeBro instead holds temporary refundable collateral, observes the post-trade price path for a fixed window, and decides whether to refund or retain that collateral based on whether the price displacement reverts or persists.

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

BondMeBro introduces a different tradeoff from traditional dynamic fees: high impact alone does not determine the penalty ,persistence does. The hook uses only on-chain Uniswap v4 state, with no external oracle, wallet reputation system, or off-chain toxicity classifier.

The goal is to give LPs an additional risk-sharing mechanism while treating benign high-impact trades more fairly. In our live Unichain Sepolia testing, persistent displacement resulted in retained collateral, while a price-reversion case produced a 100% collateral refund with zero slash.

Challenges: What was challenging about building this project?

The hardest part was designing the mechanism so it remained correct across real Uniswap v4 swap behavior. We had to solve several issues, including variable-leg custody for exact-input and exact-output swaps, identifying the real refund recipient through router-based execution, block-aware impact calculation, quiet-pool observation, permissionless settlement, and fixed maturity checkpoints.

We also had to defend against edge cases such as same-block trade splitting, mixed token decimals, stale observations, post-maturity state changes, and frontend/router ABI differences. The final implementation was validated with 492 tests, 26 invariant tests, live Unichain Sepolia swaps, settlement, slash cases, and a live full-refund case.