Template model
A template is reusable hook logic with a defined parameter range. Each version is reviewed and attributed separately so creators can see exactly which code their launches use.
Use Submit a Template for reusable logic. A concrete token and project belong in Submit a Launch, while Hook Builder remains the skill and tooling layer for creating both.
The repository is the source for the schema, examples and intake rules. Its current instructions do not accept public template applications. Read the repository before opening a pull request; the repository controls when that changes.
Open Submit a Template — opens GitHub in a new tabTemplate or project
| Question | Project launch | Public template |
|---|---|---|
| Purpose | Create one token and market. | Let other creators launch with reusable logic. |
| Review target | One source revision and launch configuration. | One template version, factory, parameter range and payout identity. |
| Creator action | Launch from the bound wallet. | Publish a version for future official launches. |
| Earnings | Defined by the project market. | 10 bps from qualifying official template usage. |
Template economics
The public template policy uses one 20 bps (0.20%) fee. 10 bps (0.10%) goes to the template creator and 10 bps (0.10%) goes to Programmable.
The share applies only to official Programmable launches that use the exact active template version. It does not create a royalty on unrelated deployments or forks outside Programmable.
This policy is not a payout receipt. Payment requires the matching template registry, contract and recipient activation record.
Version and attribution
Approval binds one template ID and version to exact source, artifacts, runtime code, parameter limits, fee policy and creator payout identity. A code, dependency or parameter range change creates a new version.
A version can be paused for new launches if a credible issue appears. Launches already created from an immutable version remain onchain. A pause cannot rewrite their history.
What a template needs
- A clear use case and a bounded set of creator inputs.
- Exact source, reproducible artifacts and dependency versions.
- Hook permissions and every mutable or privileged control.
- Fee, liquidity, asset custody and withdrawal behavior.
- A creator payout identity and an approved software license.
- Tests for the complete allowed parameter range.
Repository reference
Submit a Template contains the schema, examples and review process for this path. Use the repository as the source for current intake instructions.
Follow Submit a Template — opens GitHub in a new tab