> For the complete documentation index, see [llms.txt](https://basedinc.gitbook.io/basedbid/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://basedinc.gitbook.io/basedbid/explainers/litepaper.md).

# LitePaper

**We're building the infrastructure that&#x20;**<mark style="color:$primary;">**sets a new standard**</mark>**&#x20;for how tokens are launched, across&#x20;**<mark style="color:$primary;">**every major chain**</mark>

<details>

<summary><strong>The Problem</strong></summary>

The current launch ecosystem is broken. Platforms <mark style="color:$primary;">extract the majority of fees</mark> from creators. KOLs receive tokens and are <mark style="color:$primary;">forced to dump</mark> them. Tax models accumulate tokens and sell them in batches, <mark style="color:$primary;">tanking charts</mark>. Contracts <mark style="color:$primary;">can't evolve without relaunching</mark> from scratch

**Projects take all the risk. Middlemen take all the value**

</details>

<details>

<summary><strong>Our Solution</strong></summary>

**We rebuilt the entire stack from the ground up**

<mark style="color:$primary;">**Launch in seconds:**</mark> Deploy a token, LBP or Board <mark style="color:$primary;">instantly</mark> with optimized defaults. No setup friction. No waiting

<mark style="color:$primary;">**Programmable fee routing:**</mark> Define exactly who earns from every swap: creators, KOLs, incubators, communities, buybacks. Fees are captured in the native asset at the swap event, so there's no token accumulation and <mark style="color:$primary;">no contract-driven sell pressure on your chart</mark>

<mark style="color:$primary;">**Boards:**</mark> Programmable launch environments that let KOLs, incubators, and communities turn distribution into <mark style="color:$primary;">recurring on-chain revenue</mark>, with their own rules, market caps and DEX selection

<mark style="color:$primary;">**Multi-chain and capital-efficient:**</mark> Deploy across major EVM chains and Solana. Built-in anti-snipe and anti-MEV protection included

<mark style="color:$primary;">**Built to last:**</mark> Fee control starts with the creator and can transition to the community through DAO-style governance. <mark style="color:$primary;">Projects survive founder exits and CTO events without ever relaunching</mark>

<div data-with-frame="true"><figure><img src="/files/SUeXQG6MI3koDBcVyQ0K" alt=""><figcaption></figcaption></figure></div>

</details>

<details open>

<summary><strong>TL;DR</strong></summary>

Deploy on any chain, at any market cap, on your chosen DEX in seconds. Define who earns, how fees flow, and how rewards are paid. <mark style="color:$primary;">**No middlemen extracting value**</mark>. <mark style="color:$primary;">**No contract dumps destroying your chart**</mark>

**This is the new standard**

<div data-with-frame="true"><figure><img src="/files/rTmV2OJDgShw8FQNWzez" alt=""><figcaption></figcaption></figure></div>

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://basedinc.gitbook.io/basedbid/explainers/litepaper.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.