The first Solana AMM with Uniswap v4-style hooks
This build reads an invented world. Three programs exist in it: Ftk9…gzya passes every check, Fwbn…YNWu has invalid flags, BGwh…uGbV is approved and upgraded since.
The nine reads approve_hook makes run here, in the order the chain refuses them.
A name is what the record stores and the directory prints.
A reviewer needs somewhere to reach you.
The review reads your source; there is nowhere to read it from.
Two lines on what the hook does.
Which pools this hook is for.
The config authority reviews the application and, if approved, signs approve_hook with the terms above. The directory lists the hook as soon as it reads the record — Approved hooks is a getProgramAccounts over the AMM, not a list anyone maintains. There is no timeline. Approval is once per program; after any upgrade, new pools are refused until the authority signs reapprove_hook.
An application opens as an issue on the hook registry repository. This build has none: set NEXT_PUBLIC_CARPENTER_HOOK_REGISTRY to it, as owner/name.