Revenue is the starting point. Allocation is the connection to BCB.
Useful products give customers a reason to pay. Our allocation model gives a share of that revenue a defined purpose within the BCB ecosystem.
Useful service → customer payment → revenue allocation → BCB-support mechanism
The connection is practical: allocated revenue can contribute liquidity, purchase BCB from the market, or fund defined participation programs. The applicable mechanisms and amounts depend on each product’s allocation policy.
Liquidity Contributions: Put Earned Assets Into BCB Markets
Allocated fee assets are paired with a corresponding value of BCB and contributed to specified liquidity pools. Our model includes contributing liquidity on the blockchain where the product earned those fees.
This connects activity in a product to resources supplied to a BCB market, even when the original customer transaction did not involve BCB.
The important details are concrete: which assets were contributed, where the paired BCB came from, which pool received them, and who owns and controls the resulting liquidity position.
We describe the contribution made, not promise that a pool’s value will always rise.
Market Purchases: Use Revenue to Buy BCB
Allocated funds can purchase BCB from the market. This creates a direct connection between product revenue and a specific action involving the token.
Purchased BCB can be retained in the treasury or assigned to defined liquidity and ecosystem programs. Its destination matters just as much as the purchase itself.
A treasury holding is not a burn. Tokens retained for future use have not been permanently removed from supply, and any subsequent deployment should remain visible in the allocation records.
A buyback is a measurable action, not a promise about the market price.
Liquidity and Ecosystem Incentives: Fund Defined Participation
Allocated revenue can also fund programs that encourage useful participation, including incentives for eligible liquidity providers in specified BCB pools.
Each program needs a defined budget, a clear source of funding, eligibility conditions and distribution rules. Where purchased BCB funds the program, its path should be traceable from the original revenue allocation through the purchase to the distribution.
These incentives support particular activities. They are not automatic interest payments to everyone who holds BCB.
The purpose is to fund participation that serves the ecosystem, not distribute rewards without explaining who pays for them.
One Allocation. A Traceable Path.
These three mechanisms are uses of allocated revenue, not three additional sources of earnings.
Illustrative example:
A product allocates $100 of earned revenue to purchase BCB. Those purchased tokens are then distributed through a liquidity-provider incentive program.
That is one $100 allocation moving through two steps: a market purchase followed by a distribution. It is not $100 of buybacks plus another $100 of newly generated funding.
Likewise, pairing earned fee assets with BCB does not turn the contributed BCB into additional product revenue.
Our reporting standard is to follow the resources from their source to their destination, distinguish planned allocations from completed actions, and avoid counting the same funds twice. The Allocations tab is where readers can examine those product-specific rules and supporting records.
The question is not simply whether revenue exists. It is how that revenue is connected to BCB.