Hookr.fun_
Release candidate0.1.0-rc.1

Integrate the exact transaction. Keep control with the user.

@hookr/sdkturns a partner's product flow into a reviewed Hookr V5 request, then keeps simulation, wallet signature, receipt, and onchain readback as separate states.

Open public repository Read integration manifest
Source and package candidate only. Package review and npm publication remain separate release gates.
  1. 01
    Prepare

    Exact calldata, value, recipients, intent, and terms hash.

  2. 02
    Simulate

    Use the intended account against the current V5 release.

  3. 03
    Sign

    The user's wallet confirms the exact simulated request.

  4. 04
    Confirm

    Wait for the canonical success receipt.

  5. 05
    Read back

    Resolve the intent and verify creator, token, and launch state.

Typed public surface

One package. Four explicit boundaries.

Imports stay small, while the shared release manifest prevents partners from mixing addresses or ABIs across generations.

@hookr/sdk/launch

Launch

Instant and bonded packets, fee splits, blueprint resolution, intent replay protection, and lifecycle events.

@hookr/sdk/hooks

Hook composer

The exact V5 tuple plus contract-aligned validation and lane compatibility checks.

@hookr/sdk/router

Bounded router

Exact-input/output requests with recipient, amount, price-limit, deadline, native value, and approval boundaries.

@hookr/sdk/verification

Release verification

One-block runtime hashes, stable contract identities, and immutable wiring readback.

Adapter packet

Preview and execution share one terms hash.

The prepared packet binds calldata and value. Its idempotency key binds chain, launchpad, creator, and intent. A callback can repeat safely without turning a retry into a second launch.

  • Current creation fee and blueprint params are read before encoding.
  • Creator-side splits support up to four unique recipients totaling 10,000 bps.
  • Trade requests require a nonzero execution bound, recipient, and deadline.
  • The SDK returns requests; it never holds keys, signs, broadcasts, or calls partner URLs.
const config = await readLaunchConfiguration(publicClient)
const intent = createLaunchIntent({ creator, lane: "instant" })

const prepared = prepareInstantLaunch({
  quote: "eth",
  creationFeeWei: config.creationFeeWei,
  intent,
  args: { ...launchTerms, expectedCreator: creator }
})

// simulate exact prepared.request → user signs → receipt → readback
const result = await reconcileLaunchIntent(publicClient, intent)
Coming soon · not in current release

WTH Arb Recapture is coming soon.

Its technical identity and source-review notes remain public, but the current SDK cannot select, encode, sign, or submit this configuration.

Composes

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

No verified WTH service identity, production recipients, authenticated trader-recipient semantics, external ABI acceptance, LP distributor, production deployment, or route signer. A future SDK API requires a separate WTH-enabled release and successful route/readback canary. Quotes must bind the connected wallet as simulation actor; a quote for another payer is not executable evidence. Today's package and transaction entrypoints do not encode the source profile.

Review the future adapter track

Stable release gate

What remains before npm.

  1. Merge and freeze the reviewed public V5 source commit before the app release.
  2. Review the package API, generated tarball, license, and npm organization authority.
  3. Run clean CI, install the tarball in a fixture app, and verify live V5 wiring again.
  4. Publish with provenance, then read the registry and install the exact released version.