BCB Token

Token address

To be published

Choose a chain from the BCB Token menu.

Built in public. Supported by useful products.

We build and test BlockchainBridge openly. Our websites, applications and token infrastructure are in public alpha, with each project’s availability shown on its own page.

Publishing token details is not a market launch announcement. Market availability will be announced separately for each chain.

We advise against purchasing BCB until public alpha is complete and we announce the official market launch for that chain. Verify the token address and trading venue against our published records. A matching name, logo or third-party listing is not proof of safety. BCB’s price, liquidity and returns are not guaranteed.

Product fees support BCB

50% of product fee income is allocated to BCB support. The other 50% funds the projects, team and operating costs.

Before a chain’s market opens, we collect its 50% allocation for the liquidity pool on that same chain when its market opens. This is a share of product fees, not profit calculated after operating costs.

Once markets open, four mechanisms share the BCB-support allocation. They are not four additional allocations, and the same funds are not counted twice:

Liquidity: Add allocated fee assets to a BCB pool on the same chain, paired with an equal value of BCB. Deeper liquidity aims to reduce the price impact of trades, not guarantee a token price.

Treasury purchases: Buy BCB on the market and hold the purchased tokens in the treasury.

Incentives: Fund defined rewards for eligible community contributors and liquidity providers.

Market-purchase burns: Buy BCB on the market and permanently remove the purchased tokens from circulation. Minting or burning as part of a bridge transfer does not count as a market-purchase burn.

The split between mechanisms, source of matching BCB, control of liquidity positions and reward eligibility will be disclosed with the detailed policy. Adding liquidity does not by itself mean it is permanently locked. Allocation records should let readers trace the funding source and the resulting liquidity contribution, purchase, reward or burn.

Markets open in phases

Stellar comes first. Additional markets follow product readiness, not a fixed date.

First target: Open the Stellar market after reaching 10 beta or live projects across four chains.

Next target: Add markets on Solana, HyperEVM, BNB Chain and Ethereum after reaching 20 beta or live projects across ten chains.

These are planned milestones, not claims about today’s launched products. Each chain also needs working products, measured fees and a ready liquidity plan. We will announce each market separately.

How token sales fund the project

Early funding and later token-sale proceeds are separate from product fee income.

Initial funding: Sales of 1% of the total BCB supply fund marketing. Sales of another 1% fund builders, development and team compensation. This is 2% of the single total supply, not a fresh 2% on each chain.

The initial 2% is excluded from the later 90/10 rule. These tokens are sold to raise funds, not given as contributor grants. Early-sale timing, eligibility and terms will be disclosed separately. No early sale is offered through this page.

Later project-operated sales: 90% of gross token-sale proceeds goes to liquidity pools on the chain where those sales take place. The remaining 10% covers team and project costs. No costs are deducted before calculating the 90% allocation.

This policy concerns sales conducted by the project, not every trade between token holders. BlockchainBridge is built by a small, self-funded team. Disclosed funding supports marketing, continued development and team compensation, including work completed before launch.

Verify the token, routes and records

Mainnet addresses, tested bridge routes and listing status will be published as they become available.

We are preparing BCB’s logo, project information and token metadata for explorers, registries, market-data platforms and supported applications. Availability through Axelar or SquidRouter, listings on CoinGecko or CoinMarketCap, and visibility in Uniswap or Jupiter are separate matters, not one shared approval.

Technical integration or a listing does not imply endorsement. Bridge routes and market availability must be checked separately for each chain. A tested route does not establish that every possible route works.

Relevant contract addresses, tested routes and component audit references belong alongside the deployment records. An audit of an underlying protocol does not establish that our whole application, configuration or integration has been independently audited.

Check the token details above before interacting. Where an address is marked “To be published”, we have not yet published mainnet token details for that chain. A matching BCB name alone does not identify the correct token.