> 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/background-info/how-it-works.md).

# How it Works

Bigly now has two types of launches:

1. **Weeklies (The Main Event)**\
   • One per week\
   • Presale runs Monday → Wednesday\
   • One auction, one token, all attention focused here
2. **Dailies**\
   • Thursday → Sunday\
   • One launch per day\
   • Same core model, faster cycle

### Launch Flow

Every Bigly launch follows the same core loop:

**Presale → Auction → Launch**

{% stepper %}
{% step %}

### Presale Opens

Each launch begins with a presale window 

• Weeklies: Mon 12PM EST → Wed 12PM EST\
• Dailies: Open Monday 12PM EST → close 12PM EST on day of launch

Anyone can contribute SOL\
No minimum or hard cap

* Allocations are pro-rata based on contribution size: based on how much you contribute relative to the total raised.
* Contribute through the app or send SOL directly to the unique wallet address for each presale.

**Soft cap mechanic**\
• Presales remain uncapped\
• Any amount raised above 500 SOL is proportionally rolled into the next nearest presale

**Early contributor bonus**\
• The first 100 SOL contributed earns 1% of token supply\
• Distributed proportionally among those contributors

**Post on X bonus**\
• Bonus eligibility claims are only available during the presale phase, and must include screenshots of bonus supply window.

**Protocol Buybacks**\
• 10% of all presale raises are used to buy and lock $BIGLY\
• Buybacks are unannounced and executed over time

Designed to reduce predictability and prevent front-running

Once the presale ends, the auction phase begins.
{% endstep %}

{% step %}

### Auction Opens

Auctions now run **in parallel with presales** and finalize shortly after:

• Auction ends 1 hour after presale closes\
• Highest bidder wins the right to launch\
• Bidding in the final minute of the auction extends the timer by 2 minutes.

The winner controls:\
• token name + ticker\
• branding / media\
• final launch execution

**Bidding rules**\
• Minimum raise: last bid + 0.1 SOL\
• Last-minute bids extend the timer

**Daily requirement**\
• To bid on a Daily, you must first submit token details

**Deployer requirement**\
• All launches require an X account at minimum
{% endstep %}

{% step %}

### Scheduled Launch

Rules of scheduling the launch

* The winner must schedule the launch within 4 hours of winning.
* The launch can be scheduled no earlier than 4 hours after the auction ends.
* The launch can be scheduled no later than 24 hours after the auction ends.

Once the winner schedules the launch, the exact time goes public and a countdown becomes visible to everyone.

The entire market knows exactly when the token goes live — creating one coordinated moment of attention and participation.
{% endstep %}

{% step %}

### Token Launch

* The token launches via Meteora's Dynamic Bonding Curve (DBC).
* At launch, raised funds are used to buy tokens and airdrop them to presale contributors immediately (58% of supply).
* An additional 1% of supply is reserved as a bonus — claimable on the app by participants who shared their bonus screenshot on X during the presale phase.
* A 1.25% trading tax is applied on the token, with 50% of fees going to the auction winner forever.
  {% endstep %}
  {% endstepper %}

####


---

# 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/background-info/how-it-works.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.