A rule the catalog doesn't have yet. A surface that should be able to trade these tokens and can't. Something in the docs, the composer, or a token page that's wrong or unclear. This page is where those go — from the people actually creating with the launcher, not from a roadmap written in private.
Ideas · last verified 2026-10-21 · the rule panels say what exists today; the public repo is where ideas are tracked.
Ideas are tracked as GitHub issues on the public repo, github.com/anondevv69/hook-launcher — the same repo that carries the program sources and the deploy records. This site is a static deploy with no database behind it, so this page takes no submissions itself: each button below opens an issue with the title and the questions prefilled. You need a GitHub account to file one.
There is no voting machinery and there are no counts on this page. An idea's status is what's written on it — here, and on its issue. Requests are read against the implementation: if an idea contradicts how the engine actually works, the answer on the issue is the explanation, not silence.
Request a rule Request an integration Give feedback
A good rule request names the transfers it judges and comes with one worked example with real numbers. A good integration request links the provider's docs and says what "working" looks like — a route that builds, a listing that appears, a receipt you can link.
These are on the record already — they come out of the platform's own build and deploy records, not from community submissions, and each carries its honest status. When community ideas land, they live on the issues page under their title prefixes.
Decay Tax is implemented and its schedule program, FeeSchedule, is live on mainnet — but no token can be launched with it. The rule works by modulating a mint's Token-2022 Transfer Fee extension, and Meteora DBC creates every launch mint with a fixed extension set that never includes it; the launcher rejects a rule-14 spec at validation time, and initializing a schedule against a DBC-shaped mint fails closed. The missing piece is a direct mint path: tooling that creates a fee-extension mint outside the DBC launch flow. Until it is built, rule 14 stays exactly what its panel says it is — proven mechanism, no launch path.
Status: tracked in the deploy records (the 2026-10-20 proof launches established the boundary). Detail: the rule 14 panel.
Trading Hours (rule 12) gives a token one daily window — a market-hours token that opens in the morning and again after lunch can't be expressed. The limit is in the launcher, not the engine: spec validation rejects a duplicate rule id in the stack, so a second rule-12 entry never reaches the chain, even though the engine itself would store two entries (its own Trading Hours comment imagines exactly that split day). Making split windows real means letting the launcher carry two rule-12 entries and validating the pair — the windows must not overlap and the day masks must make sense together.
Status: tracked; one window per day through the launcher today. Detail: the composition section of the docs.
The Ecosystem Gate (rule 17) keys on an ecosystem tag in a wallet's Registry record, and the Registry carries sixteen ecosystem presets. Exactly one has its attester configured today — preset 1, Muse. Presets 2–16 are unset: a token gated to one of them passes nobody, because no wallet can hold an attestation that no attester exists to sign (the launcher warns about this at spec time). Each further preset needs that ecosystem's own enrollment flow running and its attester configured in the Registry — the stamp is only worth what the flow behind it is worth.
Status: tracked; preset 1 (Muse) is the only one set. Detail: the rule 17 panel.
Every token's preflight report keeps three statuses separate: route supported, route tested, provider indexed. The route-tested evidence on record today is ours — named executions we ran through the standard generic resolver, linked by signature on each token's page. What is missing is a receipt we didn't produce: a swap against a launcher token executed by an independent aggregator's own routing, landing on mainnet. One public aggregator-executed swap would move the route-tested column from "we executed it" to "a third party's machinery executed it" — a different and stronger kind of evidence, and the honest next rung for the tradability story.
Status: tracked; provider indexing requests are prepared, and no aggregator-executed receipt exists yet. Detail: the preflight index defines the three statuses.