> For the complete documentation index, see [llms.txt](https://docs.bill-z.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bill-z.com/usdbillz-token-overview.md).

# $BILLZ Token Overview

## Token page

## $BILLZ Token Overview

$BILLZ is designed to support the long-term growth of the Billz ecosystem.

The token is not the product itself. The core product remains Billz: a platform helping crypto-native users and businesses manage, simulate and pay real-world expenses from their crypto treasury.

$BILLZ is intended to support community alignment, ecosystem incentives, referrals, visibility and future product-related utility.

***

### Token Launch

The $BILLZ token launch is planned for May 21, 2026.

The launch is part of the broader Billz ecosystem strategy and should be understood in connection with product growth, community building and long-term platform development.

***

### Token Purpose

The purpose of $BILLZ is to support the growth of the Billz ecosystem over time.

Potential areas include:

* community incentives
* referral rewards
* partner activation
* ecosystem campaigns
* product-related benefits
* future platform utility
* long-term user and supporter alignment

***

### Utility Roadmap

The utility of $BILLZ may evolve progressively as the Billz platform grows.

Potential utility areas may include:

* referral and community incentives
* access to selected ecosystem campaigns
* partner rewards
* potential product-related benefits
* future platform utility

Any utility remains subject to technical, legal, regulatory and product constraints.

***

### Token & Referrals

Billz has introduced a referral system to support ecosystem growth.

Referral rewards may be based on eligible activity, actual usage or net fees generated through the platform, depending on the applicable program rules.

Billz may introduce token-based incentives in the future, subject to eligibility, availability and applicable law.

***

### What $BILLZ Is Not

$BILLZ is not:

* equity in Merchain labs
* a debt instrument
* a claim on company revenue
* a promise of profit
* a guaranteed yield product
* a financial product
* a security
* a guarantee of liquidity
* a guarantee of future platform access

Token value may fluctuate significantly and may become zero.

***

### Token Disclaimer

Information about $BILLZ is provided for general informational purposes only.

Nothing in this documentation constitutes financial advice, investment advice, legal advice, tax advice, an offer to sell securities, or a solicitation to purchase financial instruments.

Crypto-assets are volatile and involve risk. Users should conduct their own research and seek independent advice where necessary.

Availability, utility and access to token-related features may vary by jurisdiction and user eligibility.

{% hint style="info" %}
21/05/2025
{% endhint %}

***

## Tokenomics

```
Total Supply: 1,000,000,000 $BILLZ

Liquidity Pool             45%  ██████████████████████
Treasury Allocation        25%  ████████████
Team Allocation            20%  ██████████
$SERV Staking               5%  ██
Programmatic Fundraising    5%  ██
```

### Visual Summary

***

| Allocation                   | Percentage |          Tokens | Purpose                                                                            |
| ---------------------------- | ---------: | --------------: | ---------------------------------------------------------------------------------- |
| **Team Allocation**          |    **20%** | **200,000,000** | Long-term alignment for founders, core team, and key contributors                  |
| **$SERV Staking**            |     **5%** |  **50,000,000** | Ecosystem rewards connected to the $SERV staking pool                              |
| **Programmatic Fundraising** |     **5%** |  **50,000,000** | Reserved for automated on-chain fundraising mechanisms                             |
| **Treasury Allocation**      |    **25%** | **250,000,000** | Product development, operations, partnerships, audits, growth, and ecosystem needs |
| **Liquidity Pool**           |    **45%** | **450,000,000** | Initial DEX liquidity and market access                                            |

### Distribution Overview

***

| Metric                         |                   Amount |
| ------------------------------ | -----------------------: |
| **Total Supply**               | **1,000,000,000 $BILLZ** |
| **Initial Circulating Supply** |   **450,000,000 $BILLZ** |

### Token Supply

***

> The token is not the product itself.\
> The core product remains Billz: an expense and treasury platform helping crypto-native users and businesses manage, simulate, and pay real-world expenses from crypto treasury.

The allocation is structured to balance initial liquidity, long-term treasury needs, ecosystem incentives, team alignment, and future product growth.

$BILLZ is designed to support the long-term growth of the Billz ecosystem.

### <br>

***

## Notes

{% hint style="warning" %}
This page is informational only and does not constitute:

* an offer to sell
* a solicitation
* legal, tax, or investment advice
  {% endhint %}


---

# 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://docs.bill-z.com/usdbillz-token-overview.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.
