Bitcoin Cash’s token is simple. The sustainability problem is not.
Bitcoin Cash (BCH) is a hard-capped, proof-of-work monetary asset whose tokenomics are intentionally close to Bitcoin’s original issuance design, while its product intent leans harder into cheap on-chain payments and higher throughput. That combination creates a clean long-horizon tension: the chain wants low fees for usage, but proof-of-work security eventually wants meaningful fee revenue as subsidies decay.
At the protocol level, BCH is “issued” the same way as Bitcoin. Miners produce blocks, and each block contains a coinbase transaction which is where new coins enter circulation and where miners collect transaction fees under the coinbase transaction rules.
BCH is protected by SHA-256 proof-of-work, and blocks are identified by the SHA-256 hash of their headers.
There is no “utility token” wrapper here. BCH is the money unit and the fee asset. It is also the base asset for BCH’s native token functionality (CashTokens), which increases the space of possible demand for blockspace but does not change BCH’s own monetary policy.
Supply, emissions, and distribution
The top-line monetary policy constraint is explicit in node implementations: MAX_MONEY is 21,000,000 BCH (expressed as 21,000,000 * COIN, with COIN = 100,000,000 satoshis) under the MAX_MONEY cap.
New issuance happens only via coinbase. The coinbase outputs are funded by (1) the block subsidy and (2) transaction fees from transactions included in the block.
On-chain emission is an epochal step function. The block reward started at 50 BCH and halves every 210,000 blocks. If you want a close parallel for PoW subsidy halvings, see our Litecoin tokenomics review.
Target block cadence is 10 minutes. In practice, realized emission over calendar time depends on how well difficulty adjustment keeps blocks near target, which matters more for BCH than most chains because BCH shares SHA-256 miners with Bitcoin and has historically experienced hashrate elasticity.
One distribution detail matters for token ownership concentration debates. BCH did not launch with a typical “allocation” table. It launched by forking Bitcoin’s ledger and continuing issuance from there; the mainnet parameters mark the UAHF (the split) at block height 478,558 and label it as the August 1, 2017 hard fork.
- Fork distribution to pre-split Bitcoin holders, Holders of Bitcoin at the time of the August 1, 2017 hard fork had the right to obtain an equal number of Bitcoin Cash units on the BCH chain (effectively mirroring the pre-split UTXO set).
- Ongoing distribution to miners (100% of new issuance), Every block’s coinbase transaction is created by the miner and is the mechanism by which the miner receives the block reward (subsidy) plus transaction fees.
From an “emissions sustainability” lens, this fork-based initial distribution is structurally neutral. It avoided a premine and avoided ongoing protocol-level insider flows. The trade-off is that BCH inherits the same “lost key” and early-holder concentration structure that exists in Bitcoin’s early years, then adds its own post-fork mining distribution path.
Utility, fees, and fiscal flows
BCH has three primary economic functions inside the system.
1) Transaction fees. Users pay fees in BCH to get transactions relayed and mined, and those fees flow to miners via the coinbase transaction. There is no protocol burn. Fees are not destroyed. They are a revenue line for security providers.
2) Block subsidy. The subsidy is the monetary inflation line item. It is deterministic, declines by halving, and asymptotically approaches the cap. The important macro point is not “scarcity.” It is that the security budget transitions from subsidy-dominant to fee-dominant over time, whether the market wants that transition or not.
3) Collateral and settlement asset. Like any UTXO PoW coin, BCH is used as collateral in off-chain contracts and as the settlement asset for applications. Protocol-level CashTokens broaden what can settle on BCH. For a custodial contrast, compare this to wrapped Bitcoin designs.
Two consensus rules are worth calling out because they shape miner cashflow timing and reorg safety behavior. First, coinbase outputs are not spendable immediately (coinbase maturity). Second, block reward plus fees are realized inside coinbase, so both components inherit that maturity delay in practice when miners move funds.
If you care about long-run equilibrium, the fee market design choice is where BCH implicitly takes a stance. BCH historically targeted low fees and higher throughput by raising block capacity constraints (e.g., the long-standing 32 MB maximum). Low fees are great for the product. They are a harder sell for long-run security, because they delay the moment when fee revenue can plausibly replace the subsidy. That is not a moral argument. It is arithmetic.
Governance and parameter control
Bitcoin Cash does not have on-chain governance, a treasury, or a standing emissions controller. Parameters change only via coordinated software upgrades and economic consensus across node implementations and miners.
The upgrade mechanism is “hard governance.” It is coordination around consensus-rule changes. The original split itself is captured in the UAHF technical specification, which describes a time-based activation approach (via Median Time Past) and the requirement that the fork block and subsequent blocks satisfy new consensus rules.
For analysts, the key point is modelability. BCH’s monetary policy is highly modelable because issuance is fixed and capped in code. Governance uncertainty shows up elsewhere: which scalability and script features are added, and how that impacts transaction demand, node costs, and therefore the fee market that eventually has to fund security.
History of tokenomics-relevant changes
BCH’s emission curve is “Bitcoin-like,” but realized emissions per calendar time depend on difficulty adjustment quality and hashrate behavior. BCH’s most tokenomics-relevant history is therefore not “marketing eras.” It is difficulty adjustment changes and capacity-rule changes.
August 1, 2017: the chain split (UAHF) at block height 478,558.
November 13, 2017: BCH activated a hard fork which replaced the emergency difficulty adjustment and introduced a new difficulty adjustment algorithm (DAA), with activation tracked at height 504,031 in common node parameters.
November 15, 2020: BCH executed an upgrade which replaced the then-current DAA with ASERT (aserti3-2d), explicitly aiming to improve stability under hashrate volatility.
May 15, 2023: the network upgrade included CashTokens among the implemented consensus changes.
May 15, 2024: the network upgrade implemented the Adaptive Blocksize Limit Algorithm (ABLA), and common node parameters track this upgrade at height 845,890.
Those upgrades do not alter BCH’s cap or the halving cadence. They do change the economics around blockspace supply and around the variance of block production. Both ultimately feed into miner revenue stability and user UX, which then feed into transaction demand and the fee market.
Risk analysis: sustainability under declining subsidy
The long-run equilibrium question for BCH is straightforward: can a low-fee, high-throughput payments chain generate enough aggregate fee revenue to maintain an adequate security budget once the subsidy becomes small?
Top 3 risks
Security budget compression as subsidies decay (dominant), Trigger: the block subsidy continues halving every 210,000 blocks while average fee revenue per block stays low because blockspace is not scarce at the margin. Mechanism: miner revenue declines in BCH terms and, unless offset by price or fee growth, some SHA-256 hashpower reallocates to alternative chains, reducing BCH hashrate and increasing the feasibility window for deep reorgs or sustained short-term censorship. Who bears it: merchants accepting low-confirmation payments, exchanges, bridge/custody operators, and any application relying on finality for settlement. Measurable indicators: (a) transaction fees per block relative to subsidy, (b) total miner revenue per day on BCH, (c) hashrate share and abrupt hashrate drops, (d) reorg depth frequency and orphan/stale block rate.
This is the core “emissions sustainability” critique. BCH’s monetary inflation is finite and defensible. 21,000,000 max with deterministic halvings is a coherent monetary policy. The question is whether the chain’s economic throughput can justify the residual inflation during the subsidy eras and then replace it with fees later.
Because BCH keeps fees low by design intent and by capacity choices (e.g., large default block size), it is implicitly betting on volume. This is a legitimate design, but it is not free. It turns “security budget” into a macro adoption question. The chain needs either (a) very high transaction counts, (b) high-value settlement transactions willing to pay meaningful fees even in a high-capacity environment, or (c) a much higher BCH price that makes modest fee levels valuable in fiat terms. None of that is guaranteed by the protocol.
Difficulty adjustment improvements (2017 DAA, then ASERT in 2020) are best understood as attempts to make this bet less fragile. They target hashrate volatility and oscillations, which otherwise can produce bursty blocks and long confirmation gaps that degrade payment UX and reduce transaction demand. Better stability helps, but it does not manufacture fee revenue. It mainly reduces self-inflicted volatility costs.
From a long-horizon standpoint, the subsidy decline is the unavoidable tightening schedule. The system goes from paying miners via dilution to demanding that users and applications fund miners directly. BCH’s “low-fee payments” positioning is in constant tension with that destination. That tension can resolve positively if BCH actually becomes a high-volume payment rail. It resolves negatively if usage remains intermittent, because there is no perpetual inflation backstop and no protocol treasury to subsidize security.
Hashrate reflexivity and reorg exposure due to shared SHA-256 mining, Trigger: relative profitability swings between BCH and other SHA-256 chains, especially under fee droughts or after halvings. Mechanism: miners can reallocate hashpower, creating sudden security budget shocks for BCH that are not directly tied to BCH transaction demand. Difficulty adjustment reduces but cannot eliminate the economic incentive to switch. Who bears it: the same set as above, with outsized impact on large settlements that assume stable confirmation cadence. Measurable indicators: hashrate volatility, deviation of realized block intervals from target, and post-halving miner participation drops.
Coordination risk around upgrades, implementations, and “social consensus”, Trigger: contentious proposals which require synchronized rule changes across teams and miners. Mechanism: if coordination fails, chains can split, fragmenting liquidity and confusing users. BCH’s own origin is a hard fork, and its upgrade specs formalize time-based activations that require client alignment. Who bears it: wallets, exchanges, custodians, and application developers who must manage replay protection, chain identification, and operational risk. Measurable indicators: multiple competing rule-sets near scheduled upgrade dates, client version fragmentation, and exchange deposit/withdrawal halts during upgrades.
If you are building on BCH and want a second set of eyes on fee-market dependence, miner incentive alignment, or the long-run equilibrium between throughput and security budget, this is where tokenomics consulting is actually useful. Most “tokenomics design” work is irrelevant for BCH. Security budget math is not.
This article is part of our Tokenomics Deep Dive series.
