Vibestarter lets you launch a token with time-released funding tied to your project’s Origin Capsule. This page covers what you’ll need ready, what the wizard will ask you to decide, and the commitments you take on once your raise goes live.

If you want to launch, start by completing a founder application. Applications are reviewed against identity, project scope, and AI-build provenance.

Have these ready before you open the launch wizard. Missing any of them will block finalization.

See Origin Capsule for what counts as valid proof, and Raise Types for choosing between Fixed Goal, Open-Ended, and Pro-Rata.

The deposit is a spam filter and commitment signal. It’s returned to you when the raise finalizes successfully. If the raise fails to meet its goal, the deposit is still returned. It’s only forfeited if the platform admin removes the raise for fraud or rule violations.

A single transaction creates your token, registers the Origin Capsule, and deploys your escrow contract. From that moment your raise is live and backers can contribute.

Funding isn’t the finish line. The ongoing commitments are how the platform protects backers and keeps founders accountable.

• --Tranches release 10% at kickstart, then 15% per month for 6 months. You request each one when it unlocks.
• --Every tranche request opens a 72h challenge window. If backers challenge, admin reviews and can freeze the raise.
• --Treasury allocations (if any) are gated by proposal-based withdrawals. You justify spending to your backers before releasing funds.
• --Your founder allocation vests on a 6-month cliff + 12-month linear schedule. No early-exit path.
• --Tokens you don’t claim get distributed to backers. LP is locked on Aerodrome indefinitely.

• --Ship against the roadmap you declared at launch
• --Post regular progress updates on the raise page and your linked X account
• --Respond to challenges transparently — a dismissed challenge should be earned, not ignored
• --Keep treasury proposals specific and justified — backers read them
• --Maintain the X identity you linked at launch; a dormant handle is a red flag

Building in public is the cheapest way to meet all of these at once. Your normal workflow — commits, deploys, audits — can stream on-chain as attestations, so the record speaks for you: