Publish a hook

Add a Hook Block

A Hook Blocks Market listing: MarketPublish (80) with a bond, admitted by the admin before any pool can install it. It earns the usage fee split.

Bring

• The block's spec: what it charges, its bounds and where each unit goes
• A manifest whose sha256 is the manifest_hash you publish
• A fee cap of at most 10%, a tier, and the bond in Config.bond_mint

Review verifies

• The published manifest hash matches the manifest
• Builder 30–60% and backers 10–40% of the usage fee, plus 30% to protocol and reserve, add to 100%
• Bonded at least Config.bond_floor for its tier; the admin can't slash or move bonds (M-5)

Launch a token from a launchpad

LaunchCreate, PoolInit and PoolSeed per pool, an optional dev buy, then LaunchFinalize: a Token-2022 mint with reel-hook, mint authority revoked.

Bring

• Name, ticker, metadata link, supply and decimals
• One to eight quotes with seeds and an opening price each
• The Hook Blocks board (reel.board.v1) and any launch lock or deadline

Review verifies

• The board passes the catalog's validate and the SDK's validateParams
• No mint or freeze authority after LaunchCreate
• Finalize applies the weights and the opening price check; LaunchAbort works before it

Open a pool for an existing token

A Launch (with its own nonce) and one or more pools on a token that already trades. Its other venues are untouched.

Bring

• The mint, where it trades now and how deep
• The quote, the seeds from your own wallet and the Hook Blocks
• Why the opening price matches the token's live markets

Review verifies

• The mint passes PROGRAM.md §1: no freeze authority, permanent delegate, transfer fee or foreign hook
• The opening price against live markets, and the pool's deposit cap
• Swaps, adds and removes of the new pool in simulation before launch

Integrate a launchpad

A prepare, sign, submit adapter: your server builds the same unsigned transactions as reel_build_launch or the SDK's builders, and the creator's wallet signs.

Bring

• The flow your users see, from preview to receipt
• How you build the transactions and how you read them back
• Your retry and resume handling

Review verifies

• Preview and execution encode the same PoolParams bytes (encodePoolParams)
• The partner never holds the creator's key and can't widen its authority
• Retries are idempotent: the same mint and nonce give the same PDAs (AlreadyExists on replay)

Run a keeper or executor

A bot that sends permissionless instructions: KotpSettle when a round ends, BucketCollect to fixed recipients, LaunchReturn. In reel-vaults: OrderFill for a limit order's bounty, FloorRebalance for Floor bids, HolderPay for Holder Pot payouts.

Bring

• Which instructions you send and when
• How you simulate before sending and back off on failure
• Your fee payer and how you fund it

Review verifies

• Only permissionless instructions; every recipient is fixed by the program
• No CPI into Agent-gated pools unless the pool allows it (agent_flags bit 1)
• Behaviour when a round is not over (RoundNotOver) or there is nothing owed

Route swaps through reel pools

A quoter and swap adapter: quote with the SDK's quoteSwap (the program's own math, checked against LiteSVM vectors) and swap with instruction 50.

Bring

• How you discover pools (getProgramAccounts or /api/v1/pools)
• Your account list for Swap, including the 7 transfer-hook accounts on hooked tokens
• How you set the limit (minimum out or maximum in)

Review verifies

• Exact-in quotes match the on-chain output
• A real limit on every swap; guards, Wallet Cap and the Agent gate surface as program errors
• Optional slots filled with the reel program id when unused