BondedHooks is an experimental research project building a marketplace and management layer for Uniswap v4 hooks. Instead of requiring pool admins to write and audit custom Solidity for every new behavior, BondedHooks aims to make hook-powered pools feel more like configurable infrastructure: admins can compose pool behavior from small, single-purpose commands bundled into curated blocks, then apply them safely to pools with allowlists, immutability options, provenance tracking, and conflict rules.

BondedHooks also introduces a community-aligned funding model for hook development. Through bonding, anyone can back promising hook ideas with ETH to fund both (1) developer bounties to ship the work and (2) a gas/rebate backstop to reduce friction for users. When a funded command or block is published and adopted across pools, bonders earn a share of long-term fees—designed around a simple “bond once, earn forever” rewards-per-share model. On the incentives side, BondedHooks is exploring points and gas rebates via on-chain rails (e.g., GasBank / GasRebateManager / DegenPool) and off-chain operator processing (AVS-style services) to credit users per epoch and support future prize mechanics that can donate value back into pools.

This is not live yet and is still under active development. The current codebase is a hackathon-built prototype and not audited—expect rapid iteration, breaking changes, and ongoing hardening as the design matures. The goal is to ship a drag-and-drop UI, expand the block catalog, add fee-routing and dynamic fee capture, and continue improving operator safety and verification.

Website: BondedHooks.com (in development) Telegram (open now): https://t.me/BondedHooks

How did you integrate our partners, if any?

Where the AVS code lives (including COFHE prototype)

Rebate AVS runtime and helpers: Bonded-hooks/operator/DegenAVS.ts:1 and Bonded-hooks/operator/processor.ts:1 Shaker AVS runtime and helpers: Bonded-hooks/operator/ShakerAVS.ts:1 and Bonded-hooks/operator/shakerProcessor.ts:1 Operator README / run instructions: Bonded-hooks/operator/README.md:1 COFHE / Fhenix integration (prototype, sponsored by Fhenix): Bonded-hooks/operator/DegenAVS_COFHE.ts:1 and Bonded-hooks/src/BidManagerCofhe.sol:1

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

Github:https://github.com/Jammabeans/Bonded-hooks Slides: Project Link: Demo Video:https://www.youtube.com/watch?v=BCYnjL5EcaA

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

Uniswap v4 hooks are powerful but hard to adopt: most pool owners aren’t Solidity engineers and there’s no safe, simple way to compose and evolve hook behavior.

There’s no sustainable funding loop for new hooks: developers ship code, but there’s no built-in model to finance development or share ongoing value.

Hooks add gas overhead, which discourages usage without some rebate or incentive. LPs still face impermanent loss and need additional, uncorrelated revenue sources.