# Blue Bull Token

**BBT · Make some noise.**

Whitepaper v1.0 · Draft proposal · 7 October 2026

**Status:** This document specifies a proposed project. The project has supplied its BNB Smart Chain (BEP-20, chain ID 56) contract address: 0x9eda922a150fea6bcbdb924d855da404172c196f. Source code, deployed properties, audit and liquidity have not been independently verified for this document. Official X account: https://x.com/bluebulltoken. Official Telegram: https://t.me/bluebullsunited. Statements about token behavior are design requirements until supported by deployed code and evidence. This document is not a confirmation that a token is live.

## 1. The idea

Wall Street has its bull. The internet deserves its own.

Blue Bull Token is a meme-culture project built around a friendly baby blue bull with tiny silver horns, a rounded face and a playful wave. Its world is a dreamy glacial landscape with soft light, frosted materials and room for shared imagination. The character is fictional. Its purpose is to be drawn, remixed, quoted and shared.

The name of the proposed token is **Blue Bull Token**. Its symbol is **BBT**, written **$BBT** in community communication. The bull is a cultural symbol, not a prediction about market direction. Neither the name nor the visual identity promises rising prices.

The central idea is participation: making something together is more interesting than waiting for a chart to move. Creator sessions, public briefs and small, accountable grants are the initial community formats. A token alone does not create a community; the work and culture must earn attention over time.

## 2. Character and culture

The Blue Bull appears wherever a quiet room needs a little creative disorder. It brings ideas, not financial advice. The recurring line is **All horns. No suits.** The wider community is the Herd; its creative workshop is the Bullpen; seasonal challenges happen in the Arena.

- **Create, do not copy.** Publish original work or clearly credit and obtain permission for reused material. Community submissions remain subject to the terms published for each campaign.
- **Loud culture, clear numbers.** Memes can be absurd. Treasury reporting cannot. Every allocation, release and paid campaign should be understandable without decoding a marketing claim.
- **Room for every horn.** Creative contribution is not measured by wallet size. No minimum token balance is required to read public content or join open discussions.
- **No manufactured performance.** Do not present fake engagement, fabricated partnerships, undisclosed paid promotions or trading-volume targets as community achievement.

Visual identity: electric blue `#204CFF`, midnight `#08111E`, ice blue `#A7C4FF`, silver and off-white. The bull is rounded and expressive, with short silver horns, large friendly eyes and a lively hopping pose. The character combines polished blue resin with frosted details. Generous typography and glacial imagery frame the community story, with clear financial tables. The voice is playful, welcoming and self-aware.

## 3. Proposed token specification

| Parameter | Specification |
|---|---|
| Full name | Blue Bull Token |
| Symbol | BBT |
| Intended network | BNB Smart Chain, mainnet chain ID 56 |
| Standard | BEP-20 / ERC-20 compatible |
| Initial supply | 1,000,000,000 BBT |
| Decimals | 18 |
| Token buy / sell / transfer tax | 0% / 0% / 0% |
| Additional issuance | No post-deployment minting |
| Upgradeability | No proxy or upgrade path planned |
| Privileged token controls | No blacklist, pause, mutable fee or transfer-limit controls planned |
| Team / founder / advisor allocation | 0% |
| Presale / private round / KOL allocation | 0% |
| Dedicated burn allocation | None |
| Contract address | 0x9eda922a150fea6bcbdb924d855da404172c196f |

One BBT equals `10^18` base units. The initial supply is `10^27` base units. Decimals define quantity precision, not price precision or additional supply. Contract amounts must be handled as integers; interfaces may format rounded values for display. An initial constructor issuance is compatible with having no callable mint function after deployment.

Zero token tax does not eliminate network gas, exchange fees, slippage or price impact. The absence of privileged token controls does not remove privileges or risks in separate sale, custody or reward contracts. Before launch, published source must show the exact implementation and all dependencies.

## 4. Allocation

All percentages below are percentages of the **one-billion initial supply**, including the percentages in sub-allocation tables. They are not percentages of their parent bucket.

| Allocation | Share | BBT | Availability |
|---|---|---|---|
| Community & Ecosystem | 50% | 500,000,000 | 25M at launch; remaining 475M over 24 months |
| Liquidity & Public Distribution | 35% | 350,000,000 | Enters circulation through sale and liquidity migration |
| Treasury | 15% | 150,000,000 | 0 at launch; release over 12 months |
| Total | 100% | 1,000,000,000 | |

### 4.1 Community & Ecosystem

| Program | Share | BBT | Intended purpose |
|---|---|---|---|
| Arena challenges & rewards | 10% | 100,000,000 | Budgeted creative and community sessions |
| Bullpen creator fund | 7% | 70,000,000 | Art, video, design, translation and community tooling |
| First Herd airdrop | 5% | 50,000,000 | Distribution under published eligibility and anti-abuse rules |
| Partnerships & collaborations | 3% | 30,000,000 | Disclosed cross-community projects and integrations |
| Community growth reserve | 25% | 250,000,000 | Later campaigns and grants with public budgets |
| Community total | 50% | 500,000,000 | |

The 50M airdrop allocation is a total program budget, not an immediate release. Its initial wave can use the 25M community amount available at launch. Subsequent waves share the community release limit with other programs. Campaign eligibility, snapshot timing, claim periods and treatment of unclaimed tokens must be published before participation; none is finalized by this draft.

### 4.2 Liquidity & Public Distribution

| Component | Share | BBT |
|---|---|---|
| Public launch | 24.5% | 245,000,000 |
| Initial DEX liquidity | 10.5% | 105,000,000 |
| Liquidity & public total | 35% | 350,000,000 |

The target is an open launch without a whitelist, private discount or preferential allocation tier. The sale platform and mechanism remain to be selected. A bonding curve is the reference model, not an integration that has already been implemented. The entire 350M should not be described as circulating before sale completion and liquidity migration.

### 4.3 Treasury

| Budget line | Share | BBT |
|---|---|---|
| Listings & market making | 6% | 60,000,000 |
| Marketing & campaigns | 4% | 40,000,000 |
| Operations, audits, infrastructure & legal | 3.5% | 35,000,000 |
| Community rewards & initiatives | 1% | 10,000,000 |
| Contingency reserve | 0.5% | 5,000,000 |
| Treasury total | 15% | 150,000,000 |

Contributor compensation, if any, comes from the operations line and must be disclosed. Zero team allocation does not mean unpaid work, nor does it guarantee that contributors never receive tokens for services. Market-maker loans and inventory must be separately identified in the ledger, with applicable repayment and ownership terms. A listing budget is not a guarantee of any exchange listing.

There is no fourth allocation, dedicated burn reserve, genesis burn or scheduled monthly token burn. This proposal makes no buyback promise and offers no staking APY. A later initiative must use an existing, disclosed budget; it cannot expand supply.

## 5. Release policy and circulation

Community release: **5% of the community bucket**, or 25M BBT, is available at launch. The remaining 475M is scheduled over 24 months, approximately 19,791,666.67 BBT per month. Unused monthly spending capacity does not roll over; unused tokens remain in custody pending a separately disclosed disposition policy. A later proposal cannot silently bypass release restrictions.

For exact accounting, define `R = 475,000,000 × 10^18`. The scheduled capacity for release period `m`, from 1 to 24, is `floor(m × R / 24) − floor((m − 1) × R / 24)` base units. This distributes rounding remainders and sums exactly to R. Final launch terms must publish the start timestamp and precise period boundaries; this table uses month labels for the planned release periods.

Treasury release: zero at launch, then 12.5M BBT monthly for 12 months, beginning 30 days after launch. Treasury policy caps monthly open-market DEX sales at **0.25% of circulating supply**. Final operational rules must define the measurement timestamp, included wallets and treatment of intermediaries before enforcement can be verified.

| Month | Public & LP | Community | Treasury | Projected circulating |
|---|---|---|---|---|
| 0, post-migration | 350,000,000 | 25,000,000 | 0 | 375,000,000 |
| 3 | 350,000,000 | 84,375,000 | 37,500,000 | 471,875,000 |
| 6 | 350,000,000 | 143,750,000 | 75,000,000 | 568,750,000 |
| 12 | 350,000,000 | 262,500,000 | 150,000,000 | 762,500,000 |
| 24 | 350,000,000 | 500,000,000 | 150,000,000 | 1,000,000,000 |

This is a full-release projection assuming a completed public sale, complete LP migration, full use of each monthly capacity and no token burns. It is not live chain data or a prediction of trading float. Reward escrow is included when funded from released allocations. Actual circulation depends on holdings and restrictions. Current total supply already reflects any actual burns; do not subtract them a second time.

## 6. Custody and transparency

Community and Treasury together account for **65% of initial supply**. The intended custody arrangement is a 3-of-5 multisig with publicly identified signers, at least two independent of the founding group. This is material discretion, not a claim that the token is automatically decentralized.

A multisig enforces an approval threshold. It does not automatically enforce vesting, an announcement period or a monthly sale limit. Until separate controls are deployed, published and reviewed, these limits are project policies. The release architecture, signer powers, modules, guards and recovery arrangements need to be disclosed before launch.

Each treasury outflow should be announced at least 24 hours before execution. A listing agreement that requires confidentiality may instead be disclosed within 24 hours afterward. The public ledger should include the transaction hash, amount, budget line, counterparty class and purpose. Compensation and paid promotion should be clearly labeled.

Planned verification materials include the token address and verified source, audit report and unresolved findings, custody addresses and signers, vesting controls, pool address and LP evidence, allocation reconciliation and transaction ledgers. None of these is established by an illustrative website card.

## 7. Public launch and liquidity

Before participation opens, publish the selected platform, sale contract, pricing function, fees, funding threshold, opening rules, timestamps, unsold-token treatment, incomplete-sale or refund process, and migration conditions. Confirm the platform can support the specified allocation and immutable token design. If it cannot, revise this proposal visibly before launch.

105M BBT is intended for initial DEX liquidity, paired with the disclosed portion of raised funds. Initial pool pricing must be explained relative to the sale's final price. A launch-platform wallet cap, if adopted, cannot prevent one participant from controlling multiple wallets and should not be marketed as a complete anti-bot solution.

The intended initial LP position is made inaccessible, with transaction evidence published. **LP tokens are claims on pool reserves; they are not BBT.** Making an LP position inaccessible does not burn the BBT in the pool. Trading changes reserve balances, and other liquidity positions may have separate owners. This mechanism provides no price floor and does not guarantee sufficient liquidity, safety or an ability to exit.

Published BBT address on BNB Smart Chain: 0x9eda922a150fea6bcbdb924d855da404172c196f. Explorer: https://bscscan.com/address/0x9eda922a150fea6bcbdb924d855da404172c196f. No contract address from another project is an official BBT address. Use this exact address consistently on the website and confirmed social channels. Names, tickers and artwork can be copied.

## 8. The Arena: community formats

**The Bullpen** is a proposed creator workshop for posters, short clips, translations and tools. Each brief needs an explicit budget, selection process, usage rights and payment record. Creators should know whether a submission is commissioned, licensed or simply shared.

**Arena Sessions** are seasonal challenges focused on creative and community work. Participation is not defined by generating trading volume. Reward budgets, eligibility, anti-abuse checks, dispute handling and payout timing must be announced before each session. There is no guaranteed payout or fixed yield.

**The Blue Hour** is a proposed public community session: show new work, review the treasury, discuss allocations and take questions. Publishing a recording and a concise recap makes the format useful across timezones.

**First Herd** is the airdrop program, not a promise that every early follower receives tokens. Its 50M allocation follows the release limits and requires explicit eligibility rules. The growth reserve funds later proposals only after budgets and recipients are disclosed.

NFT sales, staking, a cross-chain bridge, charitable donation commitments and revenue buybacks are not part of this initial scope. Adding them would require separate design, funding, disclosures and security review. The project begins with creative culture rather than a list of unbuilt financial products.

## 9. Milestones and community input

| Phase | Outcome | Current status |
|---|---|---|
| 01 — Find the signal | Character, website, draft token model and community playbook | In progress; website and draft document prepared |
| 02 — Show the receipts | Contract, audit, custody, release controls and launch terms | Planned; evidence not published |
| 03 — Open the arena | Public launch, liquidity evidence, eligibility rules and first session | Planned; no launch date set |
| 04 — Let the herd lead | Collaborations, regional sessions, grants and advisory votes | Planned |

Phases advance through demonstrated completion, not a marketing countdown. A target is not a commitment to a date or an exchange listing.

Early community votes are advisory. Multisig signers retain execution responsibility under the published policies. No voting platform, quorum, proposal threshold or binding execution system is live under this draft. Publish these parameters before the first formal vote. A future governance proposal cannot imply an ability to change immutable token code or mint new supply.

## 10. Risks and limitations

BBT is a proposed meme token with no intrinsic value, asset backing, redemption right or claim on business revenue. Its market price, if trading begins, may fall to zero. Participation does not guarantee profit, rewards, access or influence.

- **Attention and execution:** interest may disappear; programs may never ship; community activity may not translate into lasting participation.
- **Liquidity and concentration:** thin markets, concentrated holdings and discretionary allocations can produce large price movements. A published schedule does not guarantee demand.
- **Custody:** signers can collude or lose keys. Policies may not be enforced by code. Some information may be disclosed only after execution under the stated confidentiality exception.
- **Technical dependencies:** token, sale, vesting and reward contracts can contain defects. Networks, wallets, exchanges and service providers can fail. Audits reduce some uncertainty but do not prove safety.
- **Impersonation:** attackers may copy the character, name or symbol. Verify exact addresses across confirmed channels. Never disclose a seed phrase or send money to validate a wallet.
- **Regulatory and tax:** requirements depend on jurisdiction and circumstances. A meme label or disclaimer does not determine legal classification. Obtain appropriate advice before launch or participation where needed.

There is no guaranteed listing, market price, yield, campaign result or roadmap delivery. Do not treat the bull imagery as an assurance of market performance.

## 11. Publication checklist

| Item | Publication status |
|---|---|
| Website and draft whitepaper | Prepared for review |
| BBT contract address | 0x9eda922a150fea6bcbdb924d855da404172c196f (BNB Smart Chain / BEP-20) |
| Deployment and contract-property review | Not independently verified |
| Source verification and audit | Not published |
| Multisig signers and release controls | Not published |
| Launch platform, sale terms and refund rules | Not published |
| Pool address and LP transaction evidence | Not published |
| Official X account | https://x.com/bluebulltoken |
| Official Telegram account | https://t.me/bluebullsunited |
| Wallet dashboard and public ledgers | Not published |

The website must distinguish published links from plans. Placeholder entries should not invite wallet connections or purchases. Once details are confirmed, update both the site and this document and retain a record of material changes.

## 12. Document control

Version: 1.0. Date: 7 October 2026. Status: draft proposal for review. No prior BBT version is superseded.

Material changes to supply, allocations, release rules, custody or launch mechanics require a new version, a changelog and a clear announcement on confirmed official channels. Preserve prior published versions. The homepage includes this complete document from the same source; discrepancies should be resolved explicitly rather than silently changing figures.

Draft revision, 7 October 2026: added section 13 with legal notices and publication requirements, and included the full document on the homepage. Token specifications, allocations and release assumptions are unchanged. The earlier draft is retained at archive/BBT_Whitepaper_v1.0-before-legal-expansion.md.

This document provides project information, not investment, legal or tax advice. It does not itself establish a live service, enforceable token rights, an audit result or permission to operate in any jurisdiction. Applicable laws and actual deployed behavior take precedence over marketing descriptions.

## 13. Legal notices and participation disclosures

### 13.1 Scope and document status

This website and document describe a proposal for information and discussion. They do not by themselves constitute a token sale agreement, an individualized recommendation or an entitlement to receive tokens. No purchase or wallet connection is offered by this draft. Any future transaction must have separately published terms identifying the responsible operator, applicable eligibility rules, transaction mechanics and available remedies. Describing a document as informational does not override how applicable law treats its substance or distribution.

### 13.2 No promised financial or ownership rights

No equity, dividend, business revenue share, asset backing, redemption entitlement, guaranteed return or binding governance right is promised by BBT. No assurance is made about a trading market, exchange listing, price, liquidity, reward or future utility. A participant could lose the full amount committed, including transaction costs. A meme label, zero token tax or inaccessible LP position does not establish safety or a particular legal classification.

### 13.3 Local rules and eligibility

The operator's legal identity, place of establishment, intended markets and governing law have not been supplied for this draft. No jurisdiction-specific authorization or regulatory approval is claimed. Before a sale or rewards program opens, the operator must assess the applicable rules and publish any age, legal-capacity, location, sanctions, identity-verification or other eligibility requirements. Reading this public website does not establish eligibility. Do not circumvent applicable restrictions. No list of restricted countries is invented by this document.

### 13.4 Independent decisions and tax

The material is not personalized investment, legal or tax advice. Participants must evaluate their circumstances and obtain qualified advice where appropriate. Receiving, holding, transferring, selling or being rewarded with tokens may have tax or reporting consequences depending on the applicable rules. The draft does not calculate liabilities or promise any tax treatment. Nothing here transfers or excludes legal obligations that apply to an operator or service provider.

### 13.5 Wallets, transactions and third parties

Blockchain transactions may be irreversible. Wrong addresses, incompatible networks, compromised keys, malicious approvals and contract defects can cause permanent loss. Keep recovery phrases private and verify the chain, address and transaction before signing. Never pay a fee to an unsolicited account to validate a wallet or unlock a promised reward. Third-party wallets, networks, exchanges and platforms have their own terms, fees and operational risks; naming one does not establish a partnership, endorsement or guarantee. Gas, trading fees, slippage and price impact may apply even where token transfer tax is zero.

### 13.6 Public-launch and campaign terms

Before accepting funds, publish the seller or responsible operator, pricing, fees, allocation process, delivery conditions, cancellation or refund treatment, incomplete-sale handling and a support or complaints contact. No blanket non-refundable condition is created by this draft. Before a campaign, publish eligibility, budget, selection criteria, payout timing, disputes and treatment of unclaimed tokens. Do not imply that following an account or submitting work guarantees payment. Statutory rights, where applicable, are not displaced by campaign wording.

### 13.7 Creative work and paid promotion

The invitation to remix is not a blanket license to all artwork, trademarks or third-party material. Publish the scope of any BBT asset license before relying on it for commercial use. Creators retain whatever rights they hold unless they separately agree to a valid license or assignment. Obtain needed permissions and credits for submissions. Campaign terms must identify permitted uses, attribution and compensation. Paid or otherwise materially connected promotions should clearly disclose their relationship; fabricated endorsements, partnerships and engagement must not be presented as authentic community support.

### 13.8 Privacy and data handling

This document is not a completed privacy policy. The responsible data controller, contact details, hosting logs, analytics, cookies, vendors, collection purposes, retention periods, international transfers and applicable user rights must be assessed and described accurately for the deployed service. Do not claim that no data is collected merely because the page has no registration form. Publish the appropriate notice and obtain consent where required before introducing analytics, forms, wallet-linked records or campaign submissions. Public blockchain activity can remain visible independently of this website; do not place private personal data on-chain.

### 13.9 Statements about the future and changes

Programs, schedules and technical properties are proposed until supported by published evidence. Plans can change or fail because of funding, technical, operational or legal constraints. Changes must be documented visibly; they must not be used to silently rewrite completed transactions or existing rights. Neither an illustration nor a roadmap is proof of implementation. Prior drafts should remain available with the effective date and scope of any revision.

### 13.10 Responsibility, remedies and unresolved terms

No blanket liability waiver, indemnity, mandatory arbitration clause or court-selection clause is imposed by this informational draft. It does not exclude liability or statutory rights that cannot lawfully be excluded. Operator identity, complaints procedure, governing law and dispute arrangements remain to be completed for any actual service or transaction, with qualified review in the relevant jurisdictions. The absence of those details is not evidence of regulatory compliance. These disclosures require that review before being used as final transaction terms.

**Blue Bull Token · $BBT · All horns. No suits.**



