Listen
Pick a stream: blocks, transactions, gas samples, ERC-20 movement or network health. usehook opens the subscription and keeps it open while your tab is closed.
on: 'onBlock'Onchain trigger studio · Robinhood Chain
Robinhood Chain seals a block about every second. usehook holds that stream open, tests your condition against every event on it and fires whatever you attached.
A decorative slowly rotating sculpture of the usehook mark: a chrome hook with a glowing node, circled by a bead on a drifting orbit.
01 / Anatomy of a hook
A hook names a stream, a test and an effect. Write one and you have written all of them.
Pick a stream: blocks, transactions, gas samples, ERC-20 movement or network health. usehook opens the subscription and keeps it open while your tab is closed.
on: 'onBlock'Write a test over the event. Anything that fails it flows past and costs you nothing, so you can afford a noisy stream and a narrow predicate.
when: e => e.gas < 0.06Attach what should happen: a banner in the studio, a tone, a quiet line in the log, or a POST that hands the event to your own service.
then: e => notify(e)The clip above is a rendered explainer, not a screen recording. The studio runs the same three-part model against the live chain.
02 / Robinhood Chain data
Every figure below comes from Robinhood Chain's public explorer and refreshes every ten seconds. Your hooks read this same feed.
Waiting for the explorer
Waiting for the fee oracle
—
—
Connecting to Blockscout…
Connecting to Blockscout…
Source: Blockscout for Robinhood Chain . usehook proxies and caches those reads so the public explorer sees one caller per visitor rather than one per widget.
03 / Recipes
Each one opens in the studio with the stream, the test and the effect already filled in. Change the number, arm it, watch the log.
Batch your approvals and mints into the cheapest window instead of watching a gas tracker.
Size moves before the chart does. Get the transaction while it is still the only signal.
Holder count is the slowest number to fake. Crossing it is worth a look.
A widening block interval is your earliest warning that a submission will sit pending.
A cluster of reverts usually means a contract is misbehaving before anyone posts about it.
Congestion shows up in block occupancy long before it shows up in your wallet.
Filter the firehose down to the one method you care about, then read it like a tape.
usehook does the listening; your service does whatever it already does well.
04 / How it runs
Four stages sit between a block landing on Robinhood Chain and something arriving in your service. You configure the third and the fourth.
One connection to Robinhood Chain, shared by every hook you run. Adding a tenth hook does not add a tenth listener.
Raw blocks, transactions and token rows turn into flat events with named fields you can write a test against.
Each event runs through the enabled predicates. Duplicate events are dropped on identity, and each hook honours its own cooldown.
Survivors reach the effect. Webhook deliveries leave from the server, signed with the identity of the wallet that armed the hook.
Hooks you create without connecting a wallet live in your browser and evaluate while the tab is open. Connect a wallet and the studio attaches your address to each hook so webhook deliveries can be verified on the server.
05 / $HOOK
One token across the whole studio. $HOOK lives on Robinhood Chain and will gate the hook quota, webhook volume and the streams that cost real infrastructure to keep open.
No contract exists yet. Any address circulating as $HOOK today is not ours. The real one appears here and on @usehook at the same moment, and nowhere before.
These figures describe the planned configuration and are not live. Nothing on this page sells a token, takes a deposit or asks you to sign a transaction. Holding $HOOK grants no claim on usehook and no promise of a return.
06 / Field notes
The answers you would otherwise have to dig out of a docs site.
Jump to $HOOKA trigger studio for Robinhood Chain. You pick a stream, write a condition over the events on it and attach an effect. usehook keeps the subscription open and runs the condition for you, so you stop refreshing an explorer tab to find out whether something happened.
Robinhood Chain, chain id 4663, with ETH as the gas token. Event data comes from the chain's public Blockscout instance and the public RPC at https://rpc.mainnet.chain.robinhood.com. usehook has no affiliation with Robinhood Markets.
No. Build hooks, arm them and watch the log without connecting anything. Connecting gives you two things: your hooks follow your address instead of one browser, and webhook deliveries become available, because the server will only POST on behalf of an identity it can verify.
Connecting proves you hold an address. It moves no funds, grants no allowance and submits nothing to Robinhood Chain. usehook reads the chain; it does not trade, bridge or hold custody of anything.
The studio stays open to everyone. $HOOK is planned to gate the expensive tiers: more concurrent hooks, higher webhook volume and longer retention on the run log. The planned threshold is 0.10% of supply, which is 1,000,000 HOOK. None of it is switched on, and the contract does not exist yet.
Launching soon. There is no address to copy today. When it deploys it appears in the $HOOK section and on @usehook together. Treat any address you see before that as someone else's.
Treat it as a good signal, not a guarantee. Events reach you through a public explorer that rate limits and occasionally lags; a hook can fire late or miss a sample during an outage. Set a cooldown that matches how often you want to hear from it, and do not wire a hook to anything that moves money on its own.
The studio is open