Skip to main content
Launch·Updated Jul 2026Standard V1.0

The Raise

Deployment leaves you with a raise in progress, not a live market: your supporter vault is open, your token cannot trade, and contributions accumulate toward the minimum that makes going live possible. This page covers shaping that raise, running it honestly, and the special case of funding it yourself.

The three dials​

The raise is configured by three numbers, all fixed at deployment:

  • The minimum to go live — your committed pool-seeding plus committed launch-accumulation (plus the protocol's 0.5 ETH surplus floor). This is the vault's finalizeMinimum: below it, launch is structurally impossible and every contribution remains refundable. Your public commitment and the contract's enforcement are the same number — you cannot launch with less than you committed to.
  • The maximum raise — the vault's overall cap. Everything raised above the committed minimum flows to your Treasury as market-making capital: it makes your launch's engine stronger. It is not team money, and presenting it as anything but engine capital misrepresents the system.
  • The per-wallet cap — the fairness dial, bounding any single contributor's share of the supporter pool.

Representing the raise honestly​

How you present the raise is constrained by what the contracts actually give supporters — and precision here is not compliance theatre; the standard's credibility is your launch's credibility. The facts:

  • Supporters receive no tokens, no ownership, no governance — at launch they buy on the open market on the same terms as everyone else, or not at all.
  • A contribution creates a locked pro-rata share of the supporter bucket — 10% (as configured) of whatever liquidation proceeds your market eventually generates.
  • That share may be worth nothing. If the market never produces conditions the engine sells into, the supporter pool stays empty. No copy you write should promise otherwise, because nothing in the contracts backs it.
  • Until you launch, every contribution is refundable at will — unilaterally, unblockably. Your vault admin can also batch-refund to wind down a raise that will not fill (funds only ever return to their original contributors).

After launch, supporter shares accrue automatically as the engine liquidates, and supporters claim whenever they like — no action from you is ever required. The full mechanics live in The Supporter Vault and Supporter Distributions.

Funding your own launch​

A team seeding its launch entirely with its own capital is a supported configuration, not a workaround: set the supporter share to zero (it folds into market-making), size the vault caps so one wallet can fund the whole raise, enable the vault whitelist with your address as its sole member, and fill the vault yourself. The on-chain trail is the standard one, with all the same guarantees.

One operational note: the whitelist is enabled by your vault admin in a call after deployment — so enable it before funding the vault if you intend a closed raise. See team-funded launches.