> For the complete documentation index, see [llms.txt](https://bigly.gitbook.io/bigly-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bigly.gitbook.io/bigly-docs/extra/faq.md).
# FAQ
What happens to the presale funds?
All SOL raised in the presale is used to seed liquidity at launch.
* The full amount raised is paired with 400M tokens
* This forms the initial trading pool (LP)
* No portion is removed or redirected elsewhere
This ensures strong, transparent liquidity from day one.
What are the trading fees?
Tokens launched through Bigly have a **1.25% trading fee**.
* **50% of all trading fees** go to the auction winner (the deployer)
* The remaining 50% supports the protocol
This aligns incentives by rewarding the party responsible for launching and promoting the token.
What happens to the winning bid?
The winning bid from the auction is sent to the **protocol treasury**.
This capital is used to support the long-term growth and sustainability of Bigly.
What happens to outbid auction bids?
If you are outbid during the auction:
* Your funds are **automatically and immediately refunded**
* There is no lockup or delay
You can continue bidding or exit at any time without friction.
Do auction bidders need to contribute to the presale?
No, presale participants are considered completely separate entities from token deployers.
Is Bigly responsible for tokens launched on the launchpad?
No, Bigly is not responsible for tokens launched through the launchpad and cannot guarantee or control market outcomes.
Also, auction winners may be completely anonymous and individuals may not identify themselves to us.
Trade and participate responsibly.
What does Bigly solve?
#### 1. Endless PvP and Vamp Dynamics
Most token launches compete against each other for the same liquidity and attention.
* New tokens constantly drain capital from previous ones
* Attention is fragmented across too many launches
Bigly reduces this by concentrating capital and attention into a single coordinated event each week.
***
#### 2. Fragmented Liquidity and Attention
Instead of thousands of launches competing daily:
* Bigly focuses liquidity into one primary launch at a time
* Attention is concentrated rather than diluted
This increases the probability of meaningful participation and stronger market formation.
***
#### 3. Trader Fatigue
In current markets, traders are forced to constantly rotate between new tokens.
* This creates exhaustion
* Decision quality drops
* Most opportunities are missed or mistimed
Bigly simplifies this:
* Clear schedule
* Known launch time
* One coordinated opportunity
Less noise, more focus.
#### 4. No Random Creators without skin in the game
The auction ensures someone values the launch enough to win it.
####
What is the starting market cap of tokens?
**Starting Market Cap (USD)** = Total SOL Raised × 2.5 × SOL Price
Is there token utility for $BIGLY?
* 10% of all presale raises buyback $BIGLY
* Holders of 1M $BIGLY will share an airdrop of 1% of all launched tokens
Here's what else is on the table in the future:
* Holder lottery airdrops - random SOL airdrops to $BIGLY holders
* Presale lottery airdrops - random rewards for presale contributors
* Boosted presale allocations for contributors who also hold $BIGLY
Build demand first, then layer in mechanisms that reinforce it
How do I claim my bonus eligibility?
Bonus tokens become claimable on the app by participants who shared their bonus screenshot on X during the presale phase after the token launches.
How do I calculate how many tokens I will receive?
Tokens per presaler = (your SOL / total SOL raised) × (0.57 × total supply)\
e.g. (1 SOL / 500 SOL raised) x (0.57 x 1B) = 1,140,000
Contributing 1% of total raise does not equal to 1% of supply.
---
# 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://bigly.gitbook.io/bigly-docs/extra/faq.md?ask=&goal=
```
`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.