A SHARED STAKE. A PUBLIC PLAN.

Launchpad setup

A coin starts with a community. Its next chapter comes from a creator who adopts it, contributors who build, and governance that reviews the work.

Choose your pairing asset

Launch against a governor-approved onchain asset, including eligible tokenized stocks, wrapped assets, or stablecoins. The exact contract must support normal pool transfers and 0–18 decimals.

Initial eligibility: at least $1M in verified external liquidity and no more than 2% price impact on a $10,000 trade in either direction. Your governance wallet attests to the evidence; the contract enforces reported thresholds and expiry, rather than independently measuring external markets.

Reviews expire within 24 hours. No assets, including USDC, are preapproved. Expiry blocks new launches and initial purchases, while refunds and existing pools remain available. Fees and sale proceeds are paid in the chosen asset. External liquidity does not fund the launch pool: it still begins with zero real quote reserves.

Tokenized stock availability depends on the issuer contract, transfer restrictions, and liquidity on the deployment chain. No stock pairing is live yet. Social import currently uses the default asset; the manual form supports all approved choices.

The rules every launch shares

21 millionFixed supply · minted once

70% / 30%Initial liquidity / governed reserve

20% maximumDeveloper share of total supply

10% minimumCommunity and worker allocation

1% per 21 daysCombined reserve release limit

2.1% per tradeBuy and sell · 5% maximum each

Initial liquidity contains tokens only. Buyers add real USDC; sales are limited by available USDC reserves. Governance approval never overrides the supply, allocation, or release caps.

From source to community

Submit a public source, token name, ticker, and launch terms. You can launch around your own work or someone else’s.
The governor reviews the request and any proposed initial purchase.
The creator proves control of the source identity and agrees to the roadmap. Third-party launches stay unendorsed until adoption.
The founder proposes releases and bounties with work to review. Approval is followed by a two-day public challenge period.

$EVANGEL launches first, with its configured developer subject to exactly the same rules.

Prepare a launch →

Governance has defined boundaries

The Evangel deployer wallet holds platform governance, identity verification, and challenge resolution. It is also the $EVANGEL developer. This is founder-controlled governance. The same wallet can approve proposals, but it cannot bypass the contract’s economic limits.

Kairence integration is being prepared. External-token enrollment, fee routing, and a sovereign signing interface still need confirmation. Current contract decisions use an explicit testnet operator signer.

View governor status →

Connect Base Sepolia

Real transactions need a deployed factory, testnet ETH, and testnet USDC. Until connected, you can explore the interface and prepare launch terms.

Deployment instructions for operators

Use the Evangel deployer wallet for developer, governor, identity verifier, and challenge steward. Keep its private key in an encrypted local Foundry keystore. Only its public address is configured in the app.

npm run contracts:build
npm run launchpad:abi
npm run launchpad:deploy -- --broadcast

Set EVANGEL_LAUNCH_FACTORY and EVANGEL_LAUNCH_BLOCK from the deployment manifest. The script is restricted to Base Sepolia. Source verification and an external contract audit remain release requirements.

Support work without a coin

The donation treasury has its own verification, funding, and review process. Donation funds remain separate from launchpad reserves and trading fees.

Fund open source →