# After the Sale

#### Token distribution & vesting

When the sale closes and conditions are met, escrow releases to your treasury and the vesting/claim contracts activate. Publish your TGE timestamp, claim URL, and verified token contract address. At TGE, investors claim any unlocked portion; the remainder vests per your schedule. If you change dates (e.g., due to an audit finding), post an update immediately with new times and reasons.

#### Reporting & updates to investors

Set expectations before the sale: a short update at TGE + 7 days, monthly for six months, then quarterly. Keep updates factual: shipped milestones, upcoming work, treasury runway highlights, and links to on-chain addresses (treasury, vesting) so holders can self-verify. If you miss a milestone, say so, explain why, and give a new date.

#### Communication best practices (transparency, cadence)

* Single source of truth: A /updates page in your docs.
* Official links only: Repost everywhere, but always point back to your domain.
* No price promises: Describe utility and delivery, not speculation.
* Security reminders: Contract addresses, impersonation warnings, and support channels at the top of each update.
* Community Q\&A: Collect questions and answer them on a predictable cadence. Use Mosaic governance modules to surface prioritized topics.

#### Post-sale market posture

Because Mosaic does not provide LP, your liquidity plan drives early trading quality. Publish which DEX/CEX pairs will go live and when. If using a market maker, disclose the role at a high level. Avoid surprise token movements; label treasury transactions with memos where possible and link to the explorer in your updates.

**Common pitfalls**

* Ambiguous tokenomics (missing cliffs/vesting).
* Unverified token contract addresses.
* Marketing that precedes whitepaper publication.
* No dry-run of claim flow.
* Silence after TGE.

<br>


---

# 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://mosaic-9.gitbook.io/mosaic-launchpad/for-projects-launching-on-mosaic/after-the-sale.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.