Skip documentation navigation

Launch a project

Build one exact project revision, submit it for review and launch it from the wallet bound to that release.

Start here

Use Hook Builder to create the project. When Submit a Launch accepts applications, it packages the exact revision for review. The submission repository defines the request format and required files.

Use the repository instructions.

Intake rules can change with the review system. Read the current Submit a Launch README before creating a pull request; do not invent a submission format or open a manual PR while the README keeps the intake in prelaunch review.

Prepare the project

  1. Build with a clean source repository.Keep contracts, tests, deployment logic and public project data together at one reviewable revision.
  2. Run the project gates.Compile, test and reproduce the artifacts on the exact commit you intend to submit.
  3. Choose the launch wallet.The GitHub identity, source revision and wallet must match the application.
  4. Describe every important control.Include fees, recipients, liquidity custody, privileged roles, dependencies and mutable behavior.
Open Hook Builder — opens GitHub in a new tab

Submit one revision

A submission identifies one source repository, commit, tree, launch wallet and requested launch path. Changing any of those values creates a new review target.

Submit a Launch is the public home for this workflow when its README accepts applications. Its README defines the intake rules and the files to provide.

This repository is for one concrete project and token. Reusable hook logic belongs in Submit a Template, not in a project submission.

Open Submit a Launch — opens GitHub in a new tab

Review

Review checks the exact source revision, behavior, evidence and launch compatibility. A reviewer can accept the revision, request specific changes or keep the result pending when required evidence is missing.

Changes requested
The submission names the smallest complete correction. Push a new revision and let the checks run again.
Approved revision
The named revision passed the review gates. This is not a safety guarantee or a launch transaction.
Pending
Evidence or an external dependency is incomplete. Pending does not mean that the project is unsafe.

Launch

When the approved revision has an active execution path, the bound creator wallet can open Launch, review the final transaction and sign it. The connected wallet is the only party that can submit that user transaction.

The launch is not complete when a transaction is merely submitted. It must finalize and its token, pool and Router record must agree.

After launch

  • Confirm the finalized transaction and canonical token address.
  • Check that the launch appears in Explore and public feeds.
  • Share the contract address, not only a name or ticker.
  • Disclose material changes, incidents or unavailable project links.
  • Treat a new contract version or materially changed control path as a new review target.