# Welcome to Cartpad

<figure><img src="https://3397964060-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBZYSpYi02lBETubxc0DF%2Fuploads%2FkdhDqCYzCS9x5rwM8pTN%2FCARTPAD.jpg?alt=media&#x26;token=401027c3-b6d4-4ac9-87b6-ab5e915c4c8d" alt=""><figcaption></figcaption></figure>

Since inception, the success of DeFi applications has been staggering, although limited at inception, its growth has been accelerating to propel the industry around financial disintermediation to a multi-billion dollar powerhouse. \
\
While limited initially, the DeFi market capitalization has culminated in exponential growth. The institutional landscape of DeFi is rapidly expanding, taking over, mor- phing and synthesizing the institutions of traditional finance by infusing de- centralized governance and permissionless access mechanics, all on-chain, all inclusive and incorruptible. \
\
The main aim of Cartpad  is to solve the illiquidity problem of Solana Ecosystem, and to provide the one harmonized UX/UI using our platform.\
\
The current market situation is just purely chaos. New projects popping out every day, and not everyone will have the chance to buy.&#x20;

Cartpad was originally born as a Solana-only launchpad. We believes that Solana is the blockchain of the future, and the ultimate economic equilibrium will be reached when the majority of projects will be launching on Solana.

CartPad will give everyone equal chance to join IDO on our platform.&#x20;


---

# 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://cartpad.gitbook.io/cartpad/welcome-to-cartpad.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.