Partner integration standard

Choose the integration you actually need.

Six reusable tracks cover hook source, token launches, existing-token pools, launchpads, generators, and external executors. Each ends in a concrete artifact and evidence packet.

Choose one outcome. Bring the inputs. Prove each boundary.

Choose a track Send private brief

Tracks: 6 versioned
Hook candidates: 3 source-only
Deployments: 0 verified

Integration factsEvidence gated

Six reusable tracks cover hook source, token launches, existing-token pools, launchpads, generators, and external executors. Each ends in a concrete artifact and evidence packet.

Tracks: 6 versioned
Hook candidates: 3 source-only
Deployments: 0 verified

Source
Test
Deploy
Verify
List

Source → test → deploy → verify → submit

Uniswap automation starts only for a newly production-verified, unique chain + hook address. Existing shared addresses remain deduplicated.

Partner integration switchboard

Start with the outcome, not a generic partnership form.

Each lane returns a versioned technical artifact and has its own evidence gates. If your ask is still commercial discovery, keep it in the private partner queue until the technical outcome is known.

01hook_publication

Publish a hook

Hook authors with source that should appear in Hookr.

A pinned, reviewable hook manifest in the public catalog.

Hookr returnsSource issue + external-hook manifest

Inputs and review gates

You bring

Public repository and exact commit
Hook contract paths and permission flags
Dependencies, ordinary-swap behavior, and security status

We verify

Pinned source passes its declared test suite
Runtime and PoolKey evidence stay separate from source review
Uniswap submission starts only after production verification

02hook_token_launch

Launch a hook + token

Builders whose hook and token are one launch product.

One launch plan covering contracts, token, pool, liquidity, and listing evidence.

Hookr returnsLaunch brief + external-hook manifest

Inputs and review gates

You bring

Pinned hook and token source
Target chain, quote asset, PoolKey, and initial liquidity plan
Factory, router, ownership, fee, and recovery model

We verify

Atomic launch and rollback behavior are tested
Deployed wiring matches the reviewed source and constructor inputs
Hook listing is deduplicated by unique chain + hook address

03existing_token_pool

Add an existing token

Tokens that need a new hook-powered v4 market.

A new PoolKey and migration plan without pretending the old pool changed.

Hookr returnsExisting-token market brief

Inputs and review gates

You bring

Token address, chain, current pools, and current liquidity depth
Chosen hook or desired behavior
New-pool seed liquidity and migration/discovery plan

We verify

The existing pool remains untouched
The new immutable PoolKey is reviewed before initialization
Liquidity, routing, tax, and arbitrage effects are tested independently

04launchpad_sdk

Integrate a launchpad

Launchpads and protocols adding Hookr as a launch mechanic.

A versioned adapter contract for preview, launch, receipt, and status callbacks.

Hookr returnsSDK adapter + lifecycle contract

Inputs and review gates

You bring

Current launch lifecycle and SDK/API surface
Supported chains, assets, custody, and signer boundaries
Preview, launch, receipt, retry, and failure callback requirements

We verify

Preview and execution payloads encode the same reviewed terms
Partner authorization cannot expand Hookr deployer authority
Receipts and postconditions are idempotent and replay-safe

05hook_generator

Connect a hook generator

Agents and tools that generate custom v4 hook source.

Machine-readable export into Hookr without auto-trusting generated code.

Hookr returnsGenerator export + provenance packet

Inputs and review gates

You bring

Generator repository or API and version identity
Generated source, dependency lock, compiler settings, and test outputs
Human review, audit, and deployment handoff boundaries

We verify

Every artifact is pinned and reproducible
Generated claims are revalidated by Hookr's schema and tests
No generator can authorize deployment or external submission by itself

06executor_adapter

Attach an executor

Hooks coordinating two or more pools through an external executor.

A fork-tested interface with explicit auth, profit accounting, and PoolKeys.

Hookr returnsExecutor interface + fork-test packet

Inputs and review gates

You bring

Executor interface and deployed/source identity
Auth owner, rotation path, target chain, and every PoolKey
Profit recipients, split math, failure behavior, and recovery path

We verify

Authorization, swap success, profit accounting, and readback are separate assertions
Fork tests model the production auth path instead of bypassing it
Liquidity movement and multi-pool failure remain atomic or explicitly recoverable

Open a public technical brief ↗Read machine-readable tracksNo names, emails, or private chat excerpts in a public issue.

Coming soon · not in current release

WTH Arb Recapture is a future adapter module.

Its technical identity and reviewed source boundary are preserved. It cannot be selected, encoded, or deployed with the current release.

V6.1 source composition

Surge Fees · Auto Burn · Nth-buy Pot

Explicit exception

LP Rewards

LP donation and first-release Arb Recapture are not combined.

Future pool scope

A separately deployed WTH-enabled hook generation and new PoolKey.

Current native V6.1 pools, existing V5 pools, and old markets remain unchanged.

Coming soon, not production protection.No WTH-enabled production contracts, promoted release manifest, or route signer exist. The current release includes no WTH configuration or activation path.

Open executor-adapter track Open existing-token track Read SDK boundary

One contribution contract

Two lanes. The same evidence bar.

A blueprint configures Hookr’s shared chassis. A standalone product brings its own hook, factory, router, dependencies, pool, and lifecycle.

Composable blueprint

Rules on Hookr’s chassis

Parameters compose into the currently deployed Hookr implementation.

Open builder

Standalone hook product

Its own contracts and pool

Use this for Looong, Luck, Wager, and any system that cannot be expressed as parameters.

VolaDelta lane

01Pin sourceRepository + exact commit
02Break itTests + independent review
03DeployNew hook + new PoolKey
04VerifyReceipt + runtime + liquidity
05ListRegistry + conditional routing

Pinned candidates

VolaDelta, without invented deployment claims.

The pinned repositories pass their local Foundry suites. They remain source-only and unaudited until public-network evidence is added.

Source onlyunaudited

Looong Hook

A canonical LOOONG/WETH pool where verified buys create non-transferable custodied positions, mature holders can earn WETH rewards after 30 days, and part of the sell fee can move from early profitable exits to eligible holders.

Hook publication Hook + token

Pool: canonical pool only
Ordinary routing: No custom data required
Routing form: Required after deploy

before initializebefore swapafter swapbefore-swap deltaafter-swap delta

Compatibility and risk

Source tests cover ordinary exact-input and exact-output swaps in both directions with empty hookData through LooongRouter. Verified position buys and sells use one-shot authenticated intents through that router; an optional exact-output witness uses a separate versioned domain. Compatibility with Hookr's production router path is not yet proven.

Dependencies

Uniswap v4 PoolManager
Wrapped Ether
LOOONG ERC-20
LooongRouter
LooongHookFactory
LooongLaunchV1

Known boundaries

The repository labels itself a reference implementation that is unaudited and not ready for public deployment.
Before another owner has mature shares, a verified seller can receive the full 2.90% sell component back and effectively pay only the 0.10% base hook fee; the advertised anti-flip pressure is therefore weak during bootstrap.
Verified buys place LOOONG in hook custody and rely on internal non-transferable position, basis, rebate, and reward accounting.
Free withdrawal and alternate pools can bypass the position-and-reward behavior, while separate wallets can sybil mature-holder eligibility.
Before- and after-swap return deltas, exact-output gross-up, partial-fill handling, and PoolManager claim conservation require independent review and target-chain fork testing.
The holder-incentive outcome depends on early-profit, maturity, wallet-sybil, ordinary-swap, and MEV behavior; source tests are not a production economic review.
No public deployment, initialized pool, locked-liquidity receipt, source verification, or live monitoring evidence has been supplied.

Inspect pinned source

Source onlyunaudited

Lucky Hook

An ownerless canonical ETH/LUCK pool that takes hook-level swap fees, funds Chainlink VRF, and distributes periodic rewards to eligible mature buyers.

Hook publication Hook + token

Pool: canonical pool only
Ordinary routing: No custom data required
Routing form: Required after deploy

before initializebefore swapafter swapbefore-swap deltaafter-swap delta

Compatibility and risk

Empty hookData is accepted and non-empty hookData reverts. Delta-return fee accounting changes swap settlement, so the pool is not vanilla even though ordinary swaps do not require custom hook data.

Dependencies

Uniswap v4 PoolManager
Chainlink VRF v2.5 wrapper
RewardToken
LuckyLaunchFactory
LuckySwapRouter — optional

Known boundaries

The repository states that it has not been audited.
Reward liveness depends on Chainlink VRF funding, fulfillment, and timeout recovery.
Fee, liability, buyer-index, and random-selection invariants require independent production review.

Inspect pinned source

Source onlyunaudited

Wager Hook

An immutable canonical ETH/WAGER pool where ordinary swaps use empty hook data, exact-input swaps may optionally create fixed-odds WETH wager tickets, and randomness is requested only after the season closes for later settlement.

Hook publication Hook + token

Pool: canonical pool only
Ordinary routing: No custom data required
Routing form: Address-dependent

after initializebefore swapafter swap

Compatibility and risk

Empty hookData remains an ordinary swap. The optional wager path uses exact 36-byte versioned hookData and the dedicated router; routed Uniswap trades can use the ordinary path without enabling the wager feature.

Dependencies

Uniswap v4 PoolManager
Wrapped Ether
Production randomness provider
WagerRandomnessAdapter
WagerLaunchFactory
PermanentPositionLocker
WagerRouter — optional

Known boundaries

The repository states that it is unaudited and not ready for real-value deployment.
The Robinhood Chain path has no evidenced production randomness provider; changing away from Chainlink VRF requires a new dependency and trust-model review.
Wager solvency and settlement depend on reserve accounting and the selected randomness provider's lifecycle behavior.
A real-money wager product requires jurisdiction-specific product and legal review before public launch.

Inspect pinned source

Post-deployment automation

One trigger. Two honest outcomes.

A unique verified mainnet hook enters the public registry flow. A routing form is sent only when Uniswap’s published trigger rules require review and the builder has supplied current private consent.

01 / Registry

Uniswap Hooklist issue

Every new supported-chain hook address gets a source-aligned issue packet and submission attempt.

Public creation is currently restricted. Opened ≠ processed; Hookr records the exact outcome.

02 / Routing

Conditional Labs review

Only 0x91 addresses, return-delta hooks, and major-token-pair pools need the form.

Automatic routing ≠ audit, endorsement, or guaranteed inclusion.

Contact and consent live outside Git. The executor checks the live form definition, writes an at-most-once ledger first, and stores only a non-private receipt.

For hook builders

Submit the source directly to Hookr.

One issue, one pinned commit, one manifest. Deployment evidence can follow later.

Open integration issue Read V2 public catalog

Private handoff

Have a real system or private context to share?

Choose one technical track and send only the context needed to route the work. Hookr stores contact details in the operator-only partner queue, never in the public manifest.

Review request only · no deployment, listing, or reply promise