Hookr.fun_

Hookr integrations

Give every market its own rules.

Build with the live V5 stack, integrate the typed SDK candidate, bring a custom hook, or scope a new-pool path. Start with one market and a clear technical boundary.

Start a partner review Open the live builder
Builder liveSDK candidateTechnical reviewNew-release work
Integration switchboard Clear route status
LIVEBuilder
REVIEWHook team
PILOTLaunchpad
NEW POOLToken / protocol
HOOKRMarket rules
Blueprint + fixed config
POOLKEYNew poolOne fixed hook slot

Different doors. One reviewable market configuration. Once the pool opens, its hook is fixed.

Current truth

What “integration” means today.

A live primitive, a scoped partner pilot, and a future platform capability are three different things. This is the boundary we use.

Available now

Builder, marketplace, and new-token launch

Hookr's five-block composer, onchain blueprint registry, eligible royalties, and promoted new-token launch paths are live on Robinhood Chain.

Release candidate

Typed launchpad SDK and adapter lifecycle

The public package candidate covers hook composition, launch preparation, bounded swaps, callbacks, receipt reconciliation, and live release verification. It is not yet published to npm.

Needs a new release

Existing-token pools and external hooks

These paths need a new PoolKey or generation. The future WTH adapter remains excluded from the current release and has no production deployment or signing service.

Choose your lane

Come in through the door that matches the work.

Each path has a different evidence bar. Pick the closest one; the technical review can narrow it from there.

For hook builders

Live now

Compose and publish

Combine the five shipped rules, inspect the compiled permissions, publish an onchain blueprint, and launch a new market with it.

  • No-code composition with explicit parameters
  • Onchain blueprint provenance
  • Eligible hook-fee royalties up to the contract cap
Open the builder

For hook teams

Technical review

Bring custom logic

Bring the behavior, source, permissions, test evidence, and target market. Hookr reviews the integration boundary before proposing a pool or release path.

  • Permission and router assumptions mapped
  • Failure modes and exit paths reviewed
  • Source-only examples remain labeled unaudited
Choose a technical track

For launchpads

SDK release candidate

Add programmable markets

Prepare V5 launches, hook configs, fee splits, swaps, lifecycle events, and release readbacks through one typed adapter surface.

  • Dual ESM and CommonJS package candidate
  • Simulation, signature, receipt, and readback stay separate
  • Public V5 source synced; npm publication remains gated
Read the SDK guide

For token and protocol teams

New release required

Open a new hooked pool

A hook cannot be added to an existing v4 pool. The viable path is a new pool with a reviewed hook, liquidity plan, routing, and historical-market support.

  • Existing pools remain unchanged
  • New PoolKey and deployment evidence required
  • Admission checks only 18 decimals and the exact initial pull
  • Hookr's signing path is not live for this lane
Scope the new pool
Release candidate@hookr/sdk · 0.1.0-rc.1

A partner adapter with the safety boundaries left in.

The SDK prepares the exact request a user reviews. It does not collapse simulation, wallet approval, receipt, and readback into a generic “success” callback.

Read the SDK guideMachine-readable manifest
Public V5 source and package candidate are ready for review. npm publication remains gated.
01ComposeFive-block tuple + lane checks
02PrepareLaunch, blueprint, and bounded swap requests
03ReconcileIntent, receipt, and launch-state readback
04VerifyRuntime hashes, identities, and wiring
Coming soon · not in current release

Future partner module

WTH Arb Recapture is coming soon.

Its technical identity and reviewed source boundary are preserved, but it cannot be selected, encoded, or deployed with the current release. A separate activation release will be required.

01 · USER SWAP FIRSTFuture WTH-enabled poolOriginal swap remains the primary action
AFTER SWAPProposed correction attemptFixed venue · profit floor · gas stipend
02 · SECOND VENUESupported poolStale or failed route is caught
FIXED 20% + POOL-LOCKED 80%

10% proposed WTH recipient · 10% Hookr. The pool locks creator, authenticated swap recipient, and trigger-pool shares totaling 80%; default 40 creator / 20 trader / 20 trigger pool. Trigger-pool value remains escrow, not distributed.

COMPOSES WITH

Surge Fees · Auto Burn · Nth-buy Pot

CONDITIONAL

Anti-Snipe · During the Anti-Snipe guard, outer-buy Arb corrections can operate. Outer-sell corrections require an exact-output target buy and fail open until the guard ends.

EXCLUDED IN V6.1 SOURCE REVIEW

LP Rewards

New pools only.Existing V5 pools cannot be retrofitted. An existing token gets a new V6.1 PoolKey; its old markets remain unchanged and the authorized attacher is that market's creator beneficiary. Admission verifies only 18 decimals and the exact initial factory balance delta; later taxes, rebases, pauses, blacklists, callbacks, and other mutable transfer behavior are unsupported.

Coming soon, and excluded now. WTH is a source label: its service identity, production recipient, authenticated trader-recipient semantics, and external ABI acceptance are unverified. There is no production V6.1 deployment, route signer, or promoted Arb release manifest. The LP amount is adapter escrow—not distributed or claimable by LPs—until a reviewed distributor proves delivery to eligible positions.

Route and scanner boundary.Authenticated gates, Pot, and WTH require the exact Hookr router. The generic empty-data lane is only a candidate subset, the exact Robinhood Universal Router matrix is unverified, and the quoter's payer must be the connected execution account. Blockaid's V5 warning is not authoritative: one successful sell proves that route was sellable, not that every route is safe or that the scanner must clear it.

Executor adapter track SDK release boundary

External hook handoff

Bring evidence, not just an address.

A custom hook review starts with the behavior and the boundaries around it. A deployed address or passing demo is useful context, but neither proves safety, routing support, or compatibility with Hookr.

Source-only examples are treated as unaudited. Include an audit link only when it resolves to the exact reviewed source and deployment.

What to include

  • Problem, target users, and intended market behavior
  • Repository, license, commit, and deployed address if one exists
  • Chain, PoolManager, hook permission flags, and upgradeability
  • Router or custom hook-data assumptions
  • Unit, invariant, fork, and failure-path evidence
  • Proposed pilot pool, liquidity, and exit behavior

Partner process

One accountable path from context to readback.

The order matters: scope before code, evidence before launch, and readback before an integration is described as live.

  1. 01

    Share the real flow

    Product, chain, current stack, target users, first market, timing, and the boundary you want Hookr to own.

  2. 02

    Review the hard parts

    Pool creation, hook permissions, routing, liquidity, fee recipients, data, failure paths, and what must remain user-confirmed.

  3. 03

    Define one pilot

    Freeze the exact market, release surface, success measure, responsibilities, and evidence required before anything is called live.

  4. 04

    Launch, read back, learn

    Verify receipts and public behavior, measure the market, then decide whether to expand, revise, or stop.

Start with one market

Tell us where Hookr should fit.

Share enough context for a useful review. Partner integration and hook proposals stay separate so each reaches the right technical path.

No wallet action. A submission creates no partnership, endorsement, deployment, or promise of a reply.