Launch a coin

The launch flow

Provide a project name, ticker and public source URL, choose e/acc or SOL, and set the initial liquidity price range. The pairing asset is fixed at launch. Linking a repository or creator does not imply endorsement; adoption requires verified ownership.

The factory candidate creates 21 million tokens, deposits 70% into a one-sided Meteora DAMM v2 position, and retains 30% for governed rewards. The venue requires one smallest unit of the pairing asset as an ownership deposit; a SOL launch wraps one lamport. Account rent and transaction fees require additional SOL.

The inspected SOL/e/acc factory replacement is deployed on Devnet under the immediate upgrade guard. Public launches remain disabled pending the remaining live acceptance checks and a separately reviewed production release.

Isolated curve tests

Local tests exercise token-only inventory, virtual e/acc pricing and real-reserve checks. That curve is excluded from the deployable custody build. It is not an automatic production fallback. Trading on other pools is outside Evangel fee enforcement.

Coin descriptions and repository updates

The local launch candidate writes a description and GitHub repository into Token-2022 metadata. Mint and freeze controls stay locked. Name, symbol and the metadata pointer cannot be changed through the metadata update flow.

After adoption, verified repository owners or organization administrators can propose an exact description or repository correction. Governance reviews it before anything changes. Repository moves require verified control of both old and new repositories. Proposals, decisions and review hashes remain public. This uses the existing custody quorum; it does not give the owner direct metadata editing power.

This feature awaits the inspected program upgrade and deployment. Existing mints whose metadata authority was revoked cannot be unlocked. Trading terminals choose which metadata they index and display.