# LaunchOS

LaunchOS is Laika’s issuance rail — a curated and permissionless launch system that ships tokens with structure from day one.

Every launch can auto-bootstrap a DAO, a treasury, and staking (StakeOS), so projects graduate from meme → market without duct-taping infra.

***

### What LaunchOS solves

Most launchpads optimize for speed and virality; they leave teams with no treasury, no DAO, no incentive design. LaunchOS flips the script:

* <mark style="color:yellow;">**Signal > noise:**</mark> curation is earned on-chain (not back-channeled).
* <mark style="color:yellow;">**Built-in structure:**</mark> DAO + staking + treasury at genesis.
* <mark style="color:yellow;">**Aligned incentives:**</mark> emissions and bribes route to communities that organize.
* <mark style="color:yellow;">**Anti-frontrun design:**</mark> commit–reveal voting + randomized go-live.

***

### Two paths, one backbone

#### 1) Cabal Launch (curated)

For projects that want meritocratic selection and insider-level *earned* perks.

* Commit–reveal voting by veLAIKA and veTOKEN holders (no interim leaderboards).
* Weighted by vePower (USD-normalized); no quadratic bias.
* Randomized launch window post-vote (anti-sniping).
* Alpha Window for aligned participants:
  * Top 3 StakeOS pools by vePower get a private alpha ping \~1h before TGE.
  * Supportive voters of the winner get 1-minute early access (per-address buy cap, e.g. $5k).
* Auto-bootstrap: bonding-curve settlement triggers DAO + treasury seeding + StakeOS pool.

#### 2) Open Launch (permissionless)

For creators who need to go fast without sacrificing structure.

* Anyone can launch by committing a DAO allocation (e.g., 5–25% of total supply).
* When bonding-curve conditions are met:
  * Liquidity migrates to BarkSwap (DEX).
  * DAO is deployed and treasury receives its predefined share of curve proceeds.
  * Project becomes eligible for StakeOS listing.

> Both paths share the same infrastructure: bonding curves, auto-DAO, treasury routing, analytics dashboards, and hooks into StakeOS / ShillOS.

***

### Default parameters (governance-tunable)

* Treasury allocation (project-set, enforced at deploy): 5–25% of total supply.
* DAO seeding (curated): a portion of supply (e.g., up to 15%) seeded at/after TGE.
* Whitelist window (curated): 1 minute; $5k per address cap (anti-whale burst).
* Reveal & go-live: commit–reveal end → randomized TGE within 7-day window.
* Bonding curve: shape/params chosen at submission from vetted presets.
* Anti-bot: rate-limiting, proof-of-humanity options, allowlist for alpha window.<br>

> Exact values can be updated via protocol governance; projects see the active defaults at submission time.

***

### End-to-end flow

#### For projects / teams

1. Submit metadata (brand kit, tokenomics, allocation, curve preset, DAO params).
2. Choose path (Cabal or Open).
3. *(Cabal only)* Participate in a stealth epoch; no interim results.
4. Prepare launch: confirm treasury split, StakeOS policy, initial bribe budget (optional).
5. TGE: alpha ping + whitelist minute (if curated) → full public open.
6. Auto-bootstrap: DAO deployed; treasury funded; StakeOS pool created; BarkSwap migration configured.
7. Post-launch: publish first proposals (budgets, staking incentives), optionally trigger ShillOS campaigns.

#### For voters / curators (veLAIKA + veTOKEN)

* Review submissions in-app; vote commit–reveal during the weekly epoch.
* Support winners to earn alpha access and future bribes/yield via StakeOS.

#### For early participants

* Alpha recipients (top pools + supportive voters) get the 1-minute window.
* Everyone else enters at the public open; no hidden backdoor deals.

***

### Anti-frontrun & fairness

* Commit–reveal: hides interim tallies, prevents last-minute dogpiles.
* Randomized TGE window: reduces bot timing advantage.
* Per-wallet caps in alpha minute: curbs single-wallet dominance.
* Transparent rules on-chain: same playbook for every project.

***

### Integrations on day one (bonded tokens)

* StakeOS
  * Single-asset ve(3,3) pool created with the token’s policy (min/max lock, reward split).
  * Projects can bribe veLAIKA voters to route emissions to their pool.
* GovernOS
  * DAO treasury and governance contracts deployed; default quorum/timelocks applied.
  * Proposal templates (budgets, emissions, buyback & burn, creator campaigns).
* ShillOS
  * Campaign brief templates; escrow → proof-of-publication → payout flows.
  * Creator/KOL discovery and on-chain payment rails.
* BarkSwap
  * Post-curve liquidity migration; LP policy presets (fees, incentives).

***

### Benefits at a glance

* Curation without gatekeeping — anyone can launch; *earned* insiders get alpha.
* Structure by default — DAO/treasury/staking live at genesis.
* Merit-based access — governance and engagement convert into real perks.
* Ongoing alignment — emissions and bribes reward communities that organize.

***

### Notes & disclaimers

* LaunchOS is non-custodial. Projects remain responsible for their disclosures and legal compliance.
* Whitelist minute and caps apply only to curated launches; public access follows immediately after.
* Bribes are non-refundable once a voting epoch starts; outcomes and routing are on-chain.
* Parameters shown at submission are the source of truth; changes require governance approval.

***

<mark style="color:yellow;">**TL;DR**</mark>

LaunchOS turns token issuance into a programmable, fair and structured process. Projects arrive as economies, not tickers. Communities earn *insider-level* perks on-chain. And from day one, everything connects to the rest of the Super App flywheel.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://litepaper.laikachain.dog/core-modules/quickstart.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.