
BITCOIN CASH
BCH
Bitcoin Cash is a hard fork of Bitcoin with a protocol upgrade to fix on-chain capacity. Bitcoin Cash intends to be a Bitcoin without Segregated Witness (SegWit) as soft fork, where upgrades of the protocol are done mainly through hard forks and without changing the original economic rules of the Bitcoin. Bitcoin Cash (BCH) is released on 1st August 2017 as an upgraded version of the original Bitcoin Core software. The main upgrade is the increase in the block size limit from 1MB to 8MB. This effectively allows miners on the BCH chain to process up to 8 times more payments per second in comparison to Bitcoin. This makes for faster, cheaper transactions and a much smoother user experience. Why was Bitcoin Cash Created? The main objective of Bitcoin Cash is to to bring back the essential qualities of money inherent in the original Bitcoin software. Over the years, these qualities were filtered out of Bitcoin Core and progress was stifled by various people, organizations, and companies involved in Bitcoin protocol development. The result is that Bitcoin Core is currently unusable as money due to increasingly high fees per transactions and transfer times taking hours to complete. This is all because of the 1MB limitation of Bitcoin Core’s block size, causing it unable to accommodate to large number of transactions. Essentially Bitcoin Cash is a community-activated upgrade (otherwise known as a hard fork) of Bitcoin that increased the block size to 8MB, solving the scaling issues that plague Bitcoin Core today. Nov 16th 2018: A hashwar resulted in a split between Bitcoin SV and Bitcoin ABC
EVERY CLAIM IS SOURCE-LINKED · “—” MEANS NOT VERIFIED, NOT ZERO · METHODOLOGY · REVISIONS
[OVERVIEW]
Mission
Bitcoin Cash is a hard fork of Bitcoin with a protocol upgrade to fix on-chain capacity. Bitcoin Cash intends to be a Bitcoin without Segregated Witness (SegWit) as soft fork, where upgrades of the protocol are done mainly through hard forks and without changing the original economic rules of the Bitcoin. Bitcoin Cash (BCH) is released on 1st August 2017 as an upgraded version of the original Bitcoin Core software. The main upgrade is the increase in the block size limit from 1MB to 8MB. This effectively allows miners on the BCH chain to process up to 8 times more payments per second in comparison to Bitcoin. This makes for faster, cheaper transactions and a much smoother user experience. Why was Bitcoin Cash Created? The main objective of Bitcoin Cash is to to bring back the essential qualities of money inherent in the original Bitcoin software. Over the years, these qualities were f...
Team
Profile source: CoinGecko (coingecko.com · Bitcoin Cash)
[TECHNOLOGY]
[TOKENOMICS]
[CHART]
TradingView • BINANCE:BCHUSDT[MARKET_DATA]
Last updated: Nov 21, 2026, 11:00 PM UTC
[ECONOMICS]
Trading pairs
| Pair | Exchange |
|---|---|
| BCH/USD | Coinbase Exchange spot market BCH-USD reported status online and trading_disabled=false. This is market-availability evidence, not order-book depth or daily volume.Sourceapi.exchange.coinbase.com · BCH USDObserved 2026-10-14 22:04 UTC |
[ECOSYSTEM]
Developer metrics
Community metrics
[UNIQUE_VALUE_PROPOSITION]
Core value proposition
Peer-to-peer electronic cash that prioritizes on-chain payments and native CashTokens support rather than relying only on a settlement-layer role.Sourcebitcoincash.org
Key differentiators
BCH emerged from the August 1, 2017 Bitcoin chain split over scaling strategy and maintains a 21 million coin maximum.Sourcebitcoincash.org
CashTokens provide native fungible and non-fungible tokens secured by the same proof-of-work chain.Sourcebitcoincash.org
BCHN v29 implements Pay to Script, bounded loops, functions and re-enabled bitwise operations for the May 2026 consensus upgrade.Sourcedocs.bitcoincashnode.org · Release Notes 29.0.0
Competitive edge
The design combines payments and UTXO-based token applications on one chain. This simplifies the base-layer asset model but still requires wallet, merchant and application adoption.Sourcesbitcoincash.orgdocs.bitcoincashnode.org · Release Notes 29.0.0
Target audience
Merchants, peer-to-peer payment users and developers building CashTokens or BCH script applications.Sourcesbitcoincash.orgdocs.bitcoincashnode.org · Release Notes 29.0.0
[COMPARATIVE]
Competitive positioning
Relative to the Bitcoin settlement-layer approach described in the project’s history, BCH emphasizes larger-scale on-chain electronic cash and native token functionality.Sourcebitcoincash.org
Strengths
- Native payments and CashTokens share one proof-of-work security model.Sourcebitcoincash.org
- Independent client implementations and explicit cross-client disclosure relationships provide multiple software-maintenance paths.Sourcesupgradespecs.bitcoincashnode.orgdocs.bitcoincashnode.org · DISCLOSURE POLICY
Weaknesses
- Consensus upgrades require client coordination; BCHN warns that older versions must be upgraded to remain compatible with the May 2026 rules.Sourcedocs.bitcoincashnode.org · Release Notes 29.0.0
- More expressive script operations increase implementation and review responsibilities, reflected in BCHN’s critical-code review requirements.Sourcesdocs.bitcoincashnode.org · Release Notes 29.0.0docs.bitcoincashnode.org · Bchn Gitlab Usage Rules And G…
- Fast payment acceptance is not the same as confirmed proof-of-work settlement; the project distinguishes transactions in seconds from confirmation in minutes.Sourcebitcoincash.org
Peer comparisons
- Bitcoin: shared history and scarcity model, with a different scaling direction after the 2017 split.Sourcebitcoincash.org
[ROADMAP]
Roadmap
2023COMPLETED
- CashTokens brought native fungible and non-fungible token support to BCH.Sourcebitcoincash.org
2026COMPLETED
- BCHN v29.0.0 was released with implementation of the May 15, 2026 upgrade: Pay to Script, bounded loops, function definition/invocation and bitwise operations. Completed refers to client delivery; a live node activation check was not performed.Sourcedocs.bitcoincashnode.org · Release Notes 29.0.0
Risk factors
- Operators that miss consensus-upgrade compatibility requirements can diverge from the intended network rules.Sourcedocs.bitcoincashnode.org · Release Notes 29.0.0
- Consensus bugs can create chain-split risk; the historical 2018 Bitcoin ABC disclosure demonstrates this class of failure.Sourcebitcoinabc.org · 2018 05 07 Incident Report
- Payment utility depends on wallets, merchant acceptance and application integration, not only additional protocol features.Sourcebitcoincash.org
Outlook
The constructive case is broader payment and CashTokens use supported by richer scripting. The adverse case is limited real use or upgrade/implementation friction despite added capabilities. The reviewed sources establish delivered software work, not a verified adoption forecast or future release guarantee.Sourcesbitcoincash.orgdocs.bitcoincashnode.org · Release Notes 29.0.0
[GOVERNANCE]
Governance model
Open-source protocol coordination among independent client teams and network participants. BCHN explicitly treats its upgrade specifications as authoritative only for its own implementation, not as a binding rulebook for every Bitcoin Cash client.Sourceupgradespecs.bitcoincashnode.org
Voting mechanism
Consensus changes are implemented in client software and require adoption by network participants; the reviewed process is not a token-weighted DAO ballot.Sourcesupgradespecs.bitcoincashnode.orgbitcoincashresearch.org · 309
Proposal process
Cash Improvement Proposals describe proposed technical or operational changes and undergo public discussion. BCHN implements accepted changes in releases; its own contribution rules require review and testing before merge.Sourcesbitcoincashresearch.org · 309docs.bitcoincashnode.org · Bchn Gitlab Usage Rules And G…docs.bitcoincashnode.org · Release Notes 29.0.0
[SECURITY]
Bug bounty program
BCHN accepts responsible disclosure at security@bitcoincashnode.org and encourages PGP encryption. Its published policy does not promise a fixed bounty in advance, but says valuable disclosures may be rewarded.Sourcedocs.bitcoincashnode.org · DISCLOSURE POLICY
Security incidents
- Apr 26, 2018Bitcoin ABC was notified of a signature-hash flag vulnerability in version 0.17.0 that could have produced blocks rejected by other BCH implementations.Sourcebitcoinabc.org · 2018 05 07 Incident ReportImpact: The disclosed risk was an unintended chain split. The report describes a potential exploit and mitigation, not a confirmed theft or a quantified loss.Sourcebitcoinabc.org · 2018 05 07 Incident ReportResponse: Bitcoin ABC 0.17.1 fixed the issue; developers distributed a private fix to verified miners before public disclosure. This is historical BCH software history, not a claim that current BCHN is affected.Sourcebitcoinabc.org · 2018 05 07 Incident Report
Security practices
- Base-layer transaction history is secured by SHA-256 proof of work. BCH is a native coin, not an issuer-backed reserve claim.Sourcebitcoincash.org
- BCHN requires code review, contributor test plans, manual consensus-change testing and multiple approvals for critical changes.Sourcedocs.bitcoincashnode.org · Bchn Gitlab Usage Rules And G…
- The responsible-disclosure policy describes coordination with other BCH clients, while reserving the ability to issue urgent fixes without fully synchronized releases.Sourcedocs.bitcoincashnode.org · DISCLOSURE POLICY
[REGULATORY]
Regulatory classification
Native permissionless proof-of-work digital currency. The cited U.S. filing documents a regulated-market BCH derivative context, not a universal legal classification.Sourcesbitcoincash.orgcftc.gov · Ptc1027237768
Compliance status
Protocol participation is permissionless, while intermediaries and derivative products remain subject to their own jurisdictional rules. The cited filing does not certify the network itself as a regulated issuer.Sourcesbitcoincash.orgcftc.gov · Ptc1027237768
Jurisdictions
- United States · BCH-linked derivative self-certification filedSourcecftc.gov · Ptc1027237768On October 27, 2023, North American Derivatives Exchange, doing business as Crypto.com Derivatives North America, self-certified a BCH event-contract swap under CEA section 5c(c)(1) and CFTC rule 40.2. An exchange filing is not an endorsement of BCH or a blanket ruling on every use.Sourcecftc.gov · Ptc1027237768
[COMMUNITY]
[GITHUB_REPOSITORIES]
[SOCIAL_MEDIA]
[TECHNICAL_DETAILS]
Technical specifications
- Source
- CoinGecko
- Source Url
- coingecko.com · Bitcoin Cash
- Categories
- Smart Contract PlatformLayer 1 (L1)Bitcoin ForkProof of Work (PoW)Coinbase 50 Index
- Hashing Algorithm
- SHA-256
- Supported Platforms