The keeper layer for v4 hooks. Your hook reacts, Conductor acts, your fees land where you said. Enforced on chain.
CA: 0xdd215018a9c558fcdfb2db56ab4d8c60ddf25491
https://t.co/zCmP5T0MPb
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.
https://t.co/FQXnjM9zqm
We’re having trouble getting our team badge on @fomo and are working with support to resolve it.
We’ll also be sharing all project updates through our official FOMO account:
https://t.co/VdV52uf3fB
Before shipping a feature, we ran our own example through our contracts: "never spend more than 0.1 ETH a day."
It could have frozen the automation. We fixed it before anyone used it: the swap now spends only what's left under the cap.
Every run is public: https://t.co/bEkfFPvWtD
One bot shouldn't run everything.
Conductor is opening its operator network. Anyone can run jobs for automation owners, get paid gas plus a small margin, and build a public track record. Owners choose who runs their automations.
https://t.co/ilBrpU6WUF
Want your holders to trust your automation?
A Conductor automation can make any rule change wait a set time before it takes effect. A limit can't be quietly raised overnight. Every pending change is visible on chain first.
How it works: https://t.co/HoEB7omAg7
Building your own tools on Robinhood Chain?
Conductor has a public API, a TypeScript SDK and a CLI. Read every automation, run, hook and pool as JSON, or script your own automations end to end.
Docs: https://t.co/HoEB7on85F
Prefer typing to clicking?
The Conductor site has a built-in terminal. Press Ctrl + backtick on any page to list automations, read runs, inspect hooks or stream live events.
Open it full screen: https://t.co/JDvV8pJviL
Don't start from a blank page.
Conductor recipes are ready-made automations: fee buybacks, payouts, funding a rewards pool. Copy one in a single signature, adjust the limits and go.
Publish your own and you can earn builder rewards when people use it.
https://t.co/Q2gahuUgGX
Launched a token with a v4 hook?
Your creator fees sit unclaimed until someone acts. Conductor claims them, buys back your token and sends it to your rewards pool or a burn address, on a schedule you choose, within a daily cap your contract enforces.
Set it up in one flow: https://t.co/vX9m470sqJ
What does a job on Conductor actually cost?
Our latest hourly payout used 198,411 gas and paid the operator 0.000005 ETH. That's the whole fee, and it's capped by the owner's rules.
On chain: https://t.co/BuUVh0QidQ
On Conductor: https://t.co/URI6sT4yfX
Your automation, your keys.
Pause it, change its rules or withdraw everything whenever you want. Conductor never holds your funds, and operators can only do what your contract allows.
Here's ours, with every rule visible on chain: https://t.co/l08EMqThoh
Know the moment something happens.
Conductor alerts send a signed webhook to your server whenever your automation runs, fails, gets topped up or runs low on its fee budget. Each one is signed, so you can verify it really came from Conductor.
Set up from your automation page. Docs: https://t.co/iJofPB5dBq
Every Conductor automation runs as a simulation against the live chain before you sign anything.
You see the exact calls it will make, how balances change, the gas and the operator fee. Activation needs a passing simulation, so a broken setup never reaches your wallet.
Try it, no wallet needed: https://t.co/vX9m470sqJ
Conductor recap: what we’ve shipped
1,000+ Uniswap v4 hooks indexed on Robinhood Chain
5.7M+ onchain events indexed with zero lag
3 successful mainnet runs out of 3
2 live jobs running automatically
Live now
Hooks explorer
Balance and schedule triggers
A dashboard showing every run
Builder rewards
https://t.co/AuKfzz4pts
Those screenshots were taken before the update was fully connected. You could have shared them in the replies so we could address them publicly. Instead, you sent them in DMs alongside a pitch to manage a Telegram community for us.
We welcome bug reports and criticism. What we don’t appreciate is presenting an unfinished rollout as a product failure while pitching your services. We’re not looking for a community manager.
Operators LIVE to Conductor.
Set up with one command:
npx conductor-operator init
Register with a refundable ETH deposit, run jobs for automation owners, and earn gas reimbursement plus a small margin.
Builder rewards is live on Conductor.
Build something people use, and get rewarded for it.
How it works:
• Publish a recipe or open an automation for others to build from
• Builders share a pool funded by $CONDUCTOR creator fees
• Your share depends on unique, real users running what you made. Fake wallets don't count.
• Hold $CONDUCTOR to qualify
Every number is published, so anyone can check the math. First round starts Monday.
https://t.co/2kFEpNkDYv
Real use case: recurring payments that run themselves.
We gave a Conductor automation one job: pay a wallet 0.0001 ETH every hour. No one presses a button.
Job created: https://t.co/0ghJgDqVot
First payment, sent on its own: https://t.co/qT842h4eSJ
Swap the wallet for a contributor, a treasury or a rewards pool. The contract caps every payment.
Watch it live: https://t.co/bEkfFPvWtD
Builder rewards update:
The payout contract is done, with 30+ tests passing. Scoring is done too, and it catches fake users. In testing, a builder who funded 20 wallets to fake usage got all 20 thrown out.
Every weekly payout is published so anyone can check the math.
Last piece: the rewards page. Then mainnet.
Builder rewards update:
The payout contract is done, with 30+ tests passing. Scoring is done too, and it catches fake users. In testing, a builder who funded 20 wallets to fake usage got all 20 thrown out.
Every weekly payout is published so anyone can check the math.
Last piece: the rewards page. Then mainnet.