Custom hooks and builder royalties
To choose an existing launch hook, use the four-hook comparison. To submit a fee-policy hook, start with abyss-hooks and its contribution guide.
Submit a supported hook
Use the supplied pool-bound base and preserve its constructor, accounting and callback rules. Submit one hook folder with the required files:
| File | Include |
|---|---|
*.sol | Complete hook sources, based on the supplied static or dynamic reference. |
hook.json | Hook identity, source, license and fee-policy declaration. |
integration.json | Proposed registry inputs and author terms. |
review.md | Formula, rounding, boundaries, dependencies, authority, risks and check results. |
test/Smoke.t.sol | Concrete smoke suite inheriting the provided harness. Add policy-specific tests as needed. |
Run the contribution guide's local qualification checks and include their results with the pull request. A source merge does not register the design: maintainers separately review the deployed artifact, economics and author consent before registry admission. Strategies requiring different liquidity management, lending or upgradeable behavior need additional integration; they are not fee-policy submissions.
How royalties work
A registered author's royalty comes from owner income attributable to the market using that hook. It does not add a trader fee or take funds from the launch's rewards or burns. The four ordinary app hooks have zero author royalty.
If a market has 100 units of owner income after protocol charges, any strategy reservation and collection bounty, a 10% author royalty credits 10 to the author and 90 to the owner. Other markets' owner income is excluded. See limits and exact rounding.
Author income is credited when fees are collected and remains in the earned asset. Use the SDK author-claim workflow to read credits and build transactions; there is no royalty-claim web UI. Claims pay the current registered payout wallet, whose controls are in the author reference.