YOUR HOOK REACTS.CONDUCTOR ACTS.

• Hooks

  Uniswap v4

  Every v4 hook on BSC Mainnet: its permissions, its pools and their swaps. Pick one and see the keeper jobs it can hand to Conductor.

  Hooks →

• Hook Studio

  Build a hook

  Build your own v4 hook from tested blocks: a dynamic fee, a fee split for the creator and builder, swap caps, a launch guard. Simulate it on real swaps, then deploy it from your wallet.

  Open Hook Studio →How it works →

• Automate

  Hook fees -> rewards

  Create your own automation contract, write the rules once, and hand the work your hook can't do to Conductor's operators. You keep the keys, the funds and the off switch.

  Create →Or describe it in a sentence →

• Explore

  Public

  Every automation, task and run on the protocol: what ran, what changed, what failed, with the transactions to prove it.

  Explore →

• Operators

  Open

  Anyone can run the work. See who does, how reliably, and what owners paid them. Or run one yourself.

  Operators →Run an operator →

• Rewards

  Builders

  Rewards for building things people use. Publish a recipe or open an automation; each week builders share a pool for the real users of what they made.

  Rewards →How it is counted →

How it works

1. 01

   Your hook reacts.

   A v4 hook only wakes up inside a swap or a liquidity call. It cannot read the clock, rebalance, refresh an oracle, step a fee or pay anyone on a schedule.

2. 02

   Conductor acts.

   Operators watch the pool's events and state, simulate, and submit the job: fee claims, rebalances, oracle refreshes, dynamic fees, payouts.

3. 03

   The chain enforces.

   Every job runs inside rules the hook's owner sets on chain: which calls, which assets, to whom, how much per week. Every run is recorded.