v4keeper @v4keeper

End-to-end test on mainnet: a price-triggered job. 0.20 USDG in escrow. A swap crossed the target price, the hook emitted JobTriggered, and a bonded keeper executed the job for 0.198 USDG. Swap: robin.etherscan.io/tx/0xdf276d77f… Execute: robin.etherscan.io/tx/0x140d038b5…

First end-to-end runs on Robinhood Chain mainnet. A swap on a v4 pool fired the hook's afterSwap and flagged a limit order. A bonded keeper executed it and was paid from escrow. Trigger: robin.etherscan.io/tx/0xdf276d77f… Payout: robin.etherscan.io/tx/0x140d038b5… v4keeper.xyz

How a keeper runs a v4 Keeper job: 1. Read open jobs from the registry 2. checkJob: is the trigger met? 3. Simulate execute, so a failed call costs nothing 4. Send only if the USDG reward covers gas It also wakes when the hook emits JobTriggered in a swap. v4keeper.xyz/keepers

The official $V4KEEP contract is now on the v4keeper.xyz homepage, with a one-click copy button and links to Pons and the explorer. If a CA doesn't match this one, it isn't ours: 0xae90db71b4aaf2c18e5430615074c2d2d93a630b v4keeper.xyz

How v4 Keeper handles a bad run: After every run there's a 1-day dispute window. The job poster can open a dispute with evidence, an arbiter rules on it, and if it's upheld, up to the keeper's full bond goes to the poster. Every slash is an onchain event. Rules and contract addresses are in the docs: v4keeper.xyz/docs

Uniswap v4 detail most people miss: a hook's permissions live in its address. V4KeeperHook sits at 0x1a41…9040. The last 14 bits (0x1040) switch on exactly two callbacks: afterInitialize and afterSwap. It can't run before swaps or change swap amounts. Contract: robin.etherscan.io/address/0x1a41…

Why job calls run through a separate contract: Job calldata can be anything, so the v4 Keeper registry never executes it directly. It hands the call to JobRunner, which holds no funds and only accepts calls from the registry. Escrowed USDG rewards and keeper bonds stay out of reach of whatever a job asks for. Verified source: robin.etherscan.io/address/0x52Ef…

Running a keeper on v4 Keeper: 1. Bond 0.002 ETH in the registry 2. Watch for JobTriggered from hooked v4 pools 3. Execute the job and collect the USDG reward from escrow Posters can dispute a bad run for 1 day. Unbonding takes 3 days, so the bond stays on the hook until disputes clear. v4keeper.xyz/keepers

Posting a job on v4 Keeper: 1. Pick a type: limit order, stop-loss, TWAP slice, rebalance, or custom call 2. Set a trigger: a time, or a price on a v4 pool 3. Add the call and a USDG reward per run The reward is escrowed up front. Cancel and the rest comes back. v4keeper.xyz

A quick tour of v4 Keeper. Post a job, bond as a keeper, and let the Uniswap v4 hook flag your trigger on every swap. Keepers get paid from escrow. $V4KEEP v4keeper.xyz

How the v4 Keeper hook works: After every swap in a hooked pool, V4KeeperHook reads the new price and checks each watched job: limit order, stop-loss, or range rebalance. When a trigger is met, it emits JobTriggered and a bonded keeper can execute it in the same block, paid from registry escrow. The hook takes no fee, holds no funds, and never changes swap amounts. Each check is gas-capped inside try/catch, so a watched job can't make a swap revert. Verified: robin.etherscan.io/address/0x1a41…

Burned 2,016,757 $V4KEEP from the dev wallet, sent to the dead address. Tx: robin.etherscan.io/tx/0x12e339162… CA: 0xae90db71b4aaf2c18e5430615074c2d2d93a630b

What $V4KEEP is for: • Keeper bonds: stake $V4KEEP alongside ETH to bond as a keeper and rank higher for jobs • Fee share: a cut of the 1% protocol fee goes to $V4KEEP stakers • Fee discounts for job posters who pay in $V4KEEP • Governance over protocol fee, min bond, and dispute window Rolling out in stages. Contracts stay open and verified. v4keeper.xyz

x.com/i/article/2113…