> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vibetoken.cn/llms.txt
> Use this file to discover all available pages before exploring further.
# Quickstart: Launch Your First Vibe Token in Minutes
> Launch your first Vibe Token in minutes: choose your revenue share and pricing constant, launch your token, and make your first contributor grant.
This guide walks you through everything you need to launch a Vibe Token for your software project. By the end, you will have chosen your economic parameters, launched your token, received your founder treasury, and made your first contributor grant — all before a single dollar of revenue is required.
Before you launch, choose two values that will define the economics of your token forever.
**Revenue share (α):** The fraction of every revenue event that distributes to token holders. Most projects set α between 10% and 30%. A higher α rewards contributors more generously but leaves less revenue for operations and reinvestment. Once set, α is immutable.
**Pricing constant (k):** Controls the base price level of your bonding curve (`P = k × √S`). Calibrate k to your current or expected monthly recurring revenue (MRR):
| MRR Range | Recommended k |
| ------------- | ------------- |
| \$0 – \$5,000 | `0.005` |
| \$10,000 | `0.010` |
| \$50,000 | `0.050` |
| \$100,000 | `0.100` |
**Formula:** `k = max(MRR ÷ 1,000,000, 0.005)`
If your MRR is \$0 today, use `k = 0.005`. Higher k means each token is worth more at the same supply level, appropriate when the business already generates meaningful revenue.
Submit your chosen α and k to launch your token. The system initializes with a minimum supply floor of `Smin = 1,000`.
At launch, the initial token price is:
```text theme={null}
P_initial = k × √1000
```
For example, with `k = 0.005`:
```text theme={null}
P_initial = 0.005 × 31.62 ≈ $0.158 per token
```
These two parameters define the complete economic behavior of your token. Neither value can be changed after launch. Model a few scenarios before you proceed.
Immediately after launch, you receive a founder treasury of tokens minted at the initial supply. These tokens are **inert**: they do not receive revenue distributions until you grant them to contributors.
Your treasury is your tool for bootstrapping growth before revenue exists. You can grant treasury tokens to:
* Referrers who bring in your first customers
* Beta testers who shaped your product before launch
* Community members who built early awareness
* Collaborators who contributed work before the business had income
Grants are permanent and irreversible. Once you grant a treasury token to a contributor, it becomes an issued token and immediately begins participating in revenue distributions.
Identify your first contributor — someone who has already helped grow your project, or someone you are asking to do so. Grant them tokens from your treasury.
As soon as your software earns its first revenue event `dR`, that contributor automatically receives:
```text theme={null}
payout = (α × dR) ÷ S
```
For example, if α = 0.20, dR = \$500, and S = 1,200 issued tokens, and your contributor holds 100 tokens (about 8.3% of supply):
```text theme={null}
total_distributed = 0.20 × $500 = $100
contributor_payout = 100 ÷ 1200 × $100 ≈ $8.33
```
No action is required from you or the contributor — distribution is automatic on every revenue event.
α cannot be changed after launch. This gives contributors a credible, permanent guarantee that the revenue share they were promised will never be quietly reduced. Choose α carefully before you launch.
## What's Next
Detailed guidance on choosing parameters, managing your treasury, and structuring contributor grants for your specific business model.
Everything contributors need to know about earning tokens through referrals, tracking distributions, and planning an exit.