Build a hook configuration
Pick up to 8 rules from the registry, set their parameters, choose a graduation mode and authority mode — then validate the composed launch spec with the launcher's own deterministic validator, running entirely in your browser.
Configuration validation — checks the spec against the launcher's rules. Not a guarantee of on-chain execution.
The validator is the launcher's validate-config.mjs bundled for the browser (self-hosted, no CDN) — the same code, error codes and messages as the CLI. Rule 14 (Decay Tax) fails on the standard DBC path and rule 18 (Buy Cooldown) is refused as spec-only, because the validator itself refuses them. Rule definitions and parameter bounds come from /hooks.json (registry v2).
1 · Token & launch settings
authorityMode.2 · Rules (0 / 8)
Parameters, bounds and defaults are generated from the registry. Leave a parameter empty to omit it; required parameters are marked *. The 8-rule cap is the launcher's own limit — the validator enforces it again.
Loading the rule registry…
3 · Composed spec
{}
Validator loads on first use (~590 KB, self-hosted).
…or validate a pasted spec
Building only — this page never launches anything. Launching is the launcher's job: see the agent guide or how a launch runs. Full rule reference: hook explorer.