RobinHook

Building Counterfactual Execution.
Change one event in committed history.
Re-execute what follows. Verify what survives.

[RobinHook @robinhooktech]

🔒 $RHOOK now has 3 pools!

NEW: RHOOK/ETH + RHOOK/HOOKR, alongside our original legacy pool

Both new LP positions are LOCKED FOR GOOD. Nearly 400M RHOOK seeded at launch

No withdrawals or re-ranging. Trade on @Hookrfun & @Uniswap
CA: 0x3c022D43a9f826cd206C2Ba60Bc753d8b36185c4

[RobinHook @robinhooktech]

Finally got the RHOOK Developer Alpha source on GitHub

Python API, CLI, Hookr adapter and tests are there. We also replayed a real Hookr block with LP Rewards changed from 100 to 50. One buyer got ~0.5% more RHOOK

Native replay kit isn't public yet, but we're getting there

https://t.co/bvJjdh1QTJ

[RobinHook @robinhooktech]

@ChainlinkP @Hookrfun

[RobinHook @robinhooktech]

Hookr made it to #1 on @TradePools . Now we want RHOOK to become #1 on @Hookrfun

And we want to earn that spot by building something genuinely useful. Counterfactual Execution, a solid SDK, and tools other devs can actually build with

149 pools already. We're just getting started

[CRP Agentic Engineer LARP ARC @ChainlinkP]

Fun fact.

There's 149 listed @Hookrfun pools on Robinhood Chain.

Quite impressive for a young ecosystem.

Many more will $HOOKR.

[RobinHook @robinhooktech]

Anyone can figure out that lowering a fee component will probably give a buyer more tokens. You don't need a new protocol for that

But that wasn't the interesting part of our experiment with a @Hookrfun pool

We wanted to find out if we could take a block that already happened, change one rule, and actually execute the entire block again instead of just calculating what the difference should be

We took block 93251803 on Robinhood Chain and first replayed all 7 ordered arrivals through native Nitro, including the system transaction. The state root, receipts root and block hash matched the original chain
Then we went back to the same historical checkpoint, changed one parameter in Hookr's RulesConfig (LP Rewards: 100 → 50 bps), and executed those same arrivals again. The transactions, their order and the contract code were left untouched

The buyer's net $RHOOK output was 0.504% higher in the counterfactual branch

That's roughly what you'd expect from lowering the fee. But we didn't calculate the result from a formula. We got it from the new execution's Transfer events, along with its own receipts, gas usage and state commitments

Both native executions took about 1.27 seconds in total. Our unified Go/Nitro worker also reproduced the exact results of an earlier specialized experiment without needing a rebuild for the new parameter

Now imagine asking a less obvious question

What if a hook had been disabled during a real block? What if a liquidation threshold had been different? Would the same transactions still succeed? What would the resulting state look like?

Those are the kinds of questions we want developers to explore with RHOOK

We documented the experiment, results and execution commitments on GitHub if you want to dig into the details:

https://t.co/7M7Ls3nTZg

[RobinHook @robinhooktech]

yeah yeah, we know 😅

we've been talking a lot about what RHOOK could do. fair enough. we're working on the part where we actually show it

but the rabbit hole goes pretty deep

what if LP rewards were turned off during a real swap? what if a buy limit never existed?

or here's one we really want to explore: take a real DeFi exploit, add a safety rule, replay the same transactions. does it actually stop the attack, or does something else happen?

that's the kind of stuff we want to find out

starting with @Hookrfun pools. we'll show the receipts when they're ready 👀

[RobinHook @robinhooktech]

haha tell Boss Peng he doesn't have to wait anymore! 😂🤝

We've already addressed the old 0.004 ETH swap limitation by adding two new liquidity pools without the POT restriction

There are two ways to trade larger amounts now: through Uniswap, which can route swaps into the new pools, or directly through Hookr, which also supports larger swaps through the original legacy pool

Of course, actual liquidity and slippage still matter, but that old restriction is no longer the blocker 🙌

[RobinHook @robinhooktech]

Blockchains tell you what happened

RHOOK asks a harder question:

Would a transaction still succeed if part of its history were different?

Replay the alternative. Verify the outcome.

The bigger idea? Make that answer a condition for execution

Counterfactual Execution 🪝

[RobinHook @robinhooktech]

Good news, this is already fixed! 🙌

The old ~0.004 ETH swap restriction was caused by the POT hook on our original liquidity pool

We've since added two new pools without POT, so larger swaps can now go through them. You can use Uniswap to aggregate the routes, or swap directly through Hookr, where even the original legacy pool supports larger trades

Just keep an eye on price impact for bigger orders, as usual

No need to wait anymore 🤝

[RobinHook @robinhooktech]

@Hookrfun @MCDAOio @whatthehookv4 @Uniswap

[RobinHook @robinhooktech]

@saylor

[RobinHook @robinhooktech]

Bears throwing hands?

We're throwing HOOKS 🥊🪝

$RHOOK

[RobinHook @robinhooktech]

Small $RHOOK update 🪝

Enhanced Token Info on DEX Screener is paid for! ✅

Meanwhile, we're building the Counterfactual Execution SDK and analyzing real Hookr market transactions as we work toward our first integration.

Still early. Still building.

🌐 https://t.co/UQEGVCwVVC

[RobinHook @robinhooktech]

This is a recorded demo of one bounded historical experiment - not a live replay service or a public native SDK yet

Next we're building a better developer workflow: ask several questions about the same alternative world without replaying it every time

[RobinHook @robinhooktech]

What if one action in a blockchain's past changed which later transactions still work? 👀

Genesis showed the ripple effect.

Now RHOOK's second public demo asks: which exact transaction breaks - and can we verify it?

https://t.co/6dDuAmHQ8i

[RobinHook @robinhooktech]

Why care?

Imagine asking: “Would my swap still work if something earlier had gone differently?”

That's what RHOOK is exploring

This is one recorded, bounded case - not a live tool for any transaction yet

[RobinHook @robinhooktech]

RHOOK is still being built 🪝

We've now replayed real blockchain history with one action changed and verified what happened next

Our first developer alpha is working locally

Next step: turning this into something you can actually try

More soon 👀