The keeper layer for v4 hooks. Your hook reacts, Conductor acts. Enforced on chain. CA: 0xdd215018a9c558fcdfb2db56ab4d8c60ddf25491
Joined October 2026
- Tweets208
- Following10
- Followers340
- Likes78
Pinned Tweet
The keeper layer for v4 hooks. Your hook reacts, Conductor acts, your fees land where you said. Enforced on chain.
CA: 0xdd215018a9c558fcdfb2db56ab4d8c60ddf25491
useconductor.xyz/
Your hook reacts when someone touches a pool. Who runs the jobs in between?
The fee claims, the rebalances, the payouts.
Meet Conductor: the keeper layer for Uniswap v4 hooks.
You set the job and its limits. Operators run it. Your contract enforces it.
useconductor.xyz
A rule we build Conductor by: if we can't prove a number, we don't show it.
Every stat on the site comes from the chain or from a transaction you can open yourself. When something can't be measured, like a swap that was refused and never landed on chain, we say so instead of guessing.
It makes for fewer flashy numbers. It also means every number you do see is real.
Small staking feature that's easy to miss: you can stake for someone else.
Put $CONDUCTOR in for a friend's wallet, and it's recorded as their stake from that moment. They earn the rewards, and only they can withdraw it, to any wallet they want.
A gift that pays them in ETH while it sits there.
useconductor.xyz/stake
Builder rewards pay people whose builds get used. So the obvious question: how do we stop people faking users?
A user only counts if it's a separate real wallet that actually used what you built: paid real fees, made a real deposit. Your own wallets don't count. Wallets linked to you don't count. Clicks and page views never count.
And to be eligible you have to hold $CONDUCTOR over time, not just for one block.
On the Hook Studio marketplace, copying someone's hook doesn't get you their credit.
The contract records who published each hook design first. If someone publishes the exact same settings later, their listing is labelled as a copy of the original, and the original stays on top.
You can't stop people copying a good idea. You can make sure everyone knows whose idea it was.
When you connect an AI agent to Conductor, it gets hard limits written into the code, not just good intentions.
It can propose a top-up, but only up to 0.05 ETH. It can propose raising a cap, but at most 2x and never past 0.1 ETH a day. Proposals expire after 72 hours.
And some things it can't even propose: withdrawing funds, changing the owner, or adding a new place money can go.
How do you know the numbers on Conductor are actually right? A look at our indexer 🧵
Blockchains can briefly disagree about their newest blocks. A block you saw a second ago can be replaced by a different one. If you count on those blocks too early, your numbers can be wrong.
So our indexer separates the chain into two parts.
The newest blocks are shown as live but treated as provisional. Anything that adds up money, like stats, rewards and holder snapshots, only counts blocks a safe distance behind the head, once the chain has settled.
If a recent block ever gets replaced, the indexer rewinds and reads it again.
Right now it's tracking over 500 contracts and more than 10 million decoded events on Robinhood Chain, and it usually sits within a few blocks of the head.
Every automation, payout and reward on Conductor reads from it. And it's open: anyone can query the same data we use.
useconductor.xyz/data
Every automation on Conductor is public.
Open the Explore page and you can see what any automation does, its limits, its balance, every run it has made and the transaction behind each one. You don't need a wallet or an account to look.
If an automation moves money, people should be able to check it. So everyone can.
Launched a token on pons? Your creator fees can work for your holders without you lifting a finger.
The fees-to-rewards automation claims your creator fees on a schedule, swaps them into the reward you choose, and pays your holders. Every step is capped by limits you set, and every run leaves a transaction anyone can check.
No scripts on a server. No forgetting to claim for a week.
What actually happens when a Conductor automation runs? The full life of one run 🧵
1. The keeper checks the trigger: is it time, did the balance cross the line, did the event happen?
2. If yes, it builds the exact transaction and simulates it against the current chain state. If the simulation fails or would break a limit, it stops there and nothing is sent.
3. An operator sends the transaction. The automation contract checks every call against the owner's policy: allowed targets, spending caps per period, fee budget. Anything outside the rules reverts on chain, no matter who sent it.
4. The keeper waits for the receipt, and if gas spikes it bumps the fee instead of leaving the run stuck.
5. The run is recorded with its transaction, gas used and operator fee.
6. It gets a plain-English explanation written from on-chain facts.
7. If you've set up webhooks, your server hears about it within seconds.
Seven steps, all on chain or checkable, every single time. That's what a keeper layer is supposed to be.
You can connect Claude to Conductor in one command:
claude mcp add --transport http conductor useconductor.xyz/mcp
Without a key it can already read public automations and runs. With a key you grant, it can read yours and suggest changes like a top-up or a lower cap.
It never signs anything. You review every suggestion and decide.
Every token launched on the Builder Pad is deliberately boring.
Fixed supply. No owner. No mint function. No transfer tax. No blacklist. No pause button.
That's on purpose. All the interesting parts, like fees, launch limits and payouts, live in the hook, where the rules are visible and can't be changed after launch. The token itself stays a plain token that every wallet, DEX and tool already understands.
A boring token is a token people can trust.
There are no accounts on Conductor. No email, no password, no sign-up form.
Your wallet is your login. When you want to change something on your automation, you sign a short message with the wallet that owns it, and that signature is the only proof we accept.
Nothing to leak, nothing to reset, nothing for us to hold.
Here's what the Builder Pad looks like in real life.
Say you run an art collective on Robinhood Chain and want a community token that actually funds the collective.
On the Builder Pad you:
Create the token: 1 billion supply, no owner, no mint, no tax.
Turn on a launch guard: no single swap can take more than 1% of the pool for the first 6 hours, so snipers can't grab the supply.
Add a creator fee of 0.3% on every swap, paid to the collective's wallet.
Run a whale scenario in the simulator and watch the oversized buys get refused.
Add liquidity and launch, in one signature if your wallet supports it.
From then on, every trade funds the collective, payouts go out automatically, and anyone can check every swap and payout on the token's live page.
useconductor.xyz/pad
The Builder Pad is live on Conductor.
Launch a token with its own Uniswap v4 hook from day one, and design the economy around it, not just the ticker.
Every swap on a Pad token sends ETH to $CONDUCTOR stakers.
Build the economy, not just the token.
useconductor.xyz/pad
How the Builder Pad works.
1. Create your token. A plain token with a fixed supply: no owner, no mint function, no tax. The whole supply goes to your wallet.
2. Design the economy. Pick your hook blocks: a launch guard so snipers can't grab the supply in the first hours, a creator fee on every swap, dynamic fees that rise when the price moves fast.
3. Simulate it. Run real swap scenarios and see exactly what each swap pays before anything touches the chain.