The keeper layer for v4 hooks. Your hook reacts, Conductor acts. Enforced on chain. CA: 0xdd215018a9c558fcdfb2db56ab4d8c60ddf25491
Joined October 2026
- Tweets232
- Following11
- Followers355
- Likes79
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 fun detail about Uniswap v4 hooks: what a hook is allowed to do is written into its address.
The last bits of the address say which moments it can run at: before a swap, after a swap, and so on. So you can't just deploy a hook anywhere.
Hook Studio searches for the salt that gives your hook exactly the permissions it needs, nothing extra.
useconductor.xyz/studio
When you loosen a limit on a Conductor automation, it doesn't happen right away.
By default the change waits a day, in public, before it can take effect. Anyone watching the automation can see it coming.
Tightening a limit, pausing or removing an operator doesn't wait. Making things safer is instant. Making them riskier takes a day.
We ship every day and we build in public, so tell us what to build next.
What would you automate on Robinhood Chain if it took one click? Reply here or tell us in the Telegram. The best ideas go on the list for this week.
t.me/ConductorXYZ
There's a terminal built into useconductor.xyz. Press ctrl+` on any page.
Type tail runs to watch automation runs come in live. Type overview to see everything at a glance. Type pause and the name of your automation, and it builds the transaction for your wallet to sign.
It never holds a key. Type help to see every command.
That fee has a ceiling you choose. Set a fee budget per period, and no operator can charge more than it allows.
If a run would go over your spending limit, it doesn't fail. It waits for the next period.
A detail most webhook services get wrong: they send you events that later disappear.
On a blockchain, a brand new block can briefly be replaced. Conductor waits until an event is confirmed before it sends it to your server. If its block gets replaced before then, we send nothing.
Your server only ever hears about things that actually happened.
Three things to check before you buy a new token:
Does it have an owner who can change the rules?
Can anyone mint more?
Is there a tax that can be switched on later?
Every token launched on the Builder Pad answers no, no and no. It's a plain fixed-supply token, and the contract proves it.
useconductor.xyz/pad
Why does a new stake earn nothing for the first 6 hours?
So nobody can stake right before rewards come in, take a cut, and leave. Your share grows the longer you stay: 1x after 6 hours, 1.25x after a day, 1.5x after a week, 2x after 30 days.
The rewards go to people who stay staked, not people who time it.
useconductor.xyz/stake
Last week we shipped something on Robinhood Chain every day. Here's the full list 🧵
Oct 21: The data layer. It indexes any contract on the chain, with holders, events, webhooks and snapshots.
Oct 22: Automations went live on mainnet. Rules live on chain, and operators run the work.
Six days, six releases, all live on mainnet and all checkable on chain.
This week we're making all of it easier to use and getting more builders on it.
useconductor.xyz
What we, the team behind Conductor, can't do to your automation:
Move your funds.
Change its code once it's deployed.
Swap in a different operator list without you.
What you can always do: pause it, withdraw everything, remove an operator, or change the rules. Only your wallet has those powers.
If we disappeared tomorrow, your money would still be yours.
Your automation can tell you when something needs you.
There are 12 alert types: a run succeeded or failed, the fee budget is low, the deposit only covers a few more runs, an operator stalled, a rule change is queued, the automation was paused.
No API key. You set alerts up by signing with the wallet that owns the automation, and every alert is signed so your server can check it's really from us.
Doing an airdrop on Robinhood Chain? You need a holder list you can trust.
On Conductor you can pull every holder of a token as a CSV, at the current block or any past block. It's one curl command or one CLI command.
Pick a block that's already final, and the file never changes. Send it to anyone and they'll get the same list.
useconductor.xyz/data
That's what Conductor does. Our operators send those transactions, but only inside rules you set on chain: which contracts, how much per day, how much in fees. Anything outside those rules reverts.
Your hook reacts. Conductor acts.
useconductor.xyz