What the evidence supports today
BCH is secured by inspectable SHA-256 proof-of-work rules
SupportedThe Bitcoin Cash block specification defines proof of work as double-SHA-256 hashing of the serialized block header and documents a 32,000,000-byte consensus block-size limit.
Layer North view: The security mechanism and validation rules are public, but actual security depends on deployed software and economically independent hashpower.
BC02A minority SHA-256 chain can face mobile-hashpower concentration
QualifiedBCH uses the same proof-of-work hash family as other SHA-256 chains and adjusts difficulty using ASERT, but this draft has not reproduced current pools, ultimate operators, template control, or miners' chain-switching behavior.
Layer North view: Nominal hashrate and pool labels can obscure common ownership and rapidly movable security, leaving censorship, reorganization, and liveness exposure unresolved.
BC02BC05Effective consensus control and software deployment are unknown
UnresolvedThis review does not include a dated pool and block-template analysis, reachable-node census, client-version distribution, economic-node policy map, or complete record of reorganizations, chain splits, and upgrade incidents.
Layer North view: Open specifications and releases show what software can do, not who controls production or which rules the economy will follow during disagreement.
BC03BC04BC06Snapshot, not a live ticker
Each value is tied to a named source and observation date. Market rank is context—not a quality score.
CoinGecko API cohort snapshot; rank is not a measure of chain security or executable liquidity.
As of 2026-08-13 BC01Consensus block-header hashing documented by the BCH specification.
As of 2026-08-13 BC02Maximum serialized block size in the reviewed specification; realized use and propagation are separate questions.
As of 2026-08-13 BC02BCHN specification lists P2S, bounded loops, functions, and re-enabled bitwise operations.
As of 2026-05-15 BC03BC04BCH is a separate SHA-256 chain with its own consensus history
Native BCH is not BTC or a token contract
SupportedBitcoin Cash Node maintains software and consensus-upgrade support for the BCH blockchain, whose blocks commit transactions through proof-of-work headers.
Layer North view: Shared pre-2017 history and a shared hash function do not make BCH balances or consensus interchangeable with Bitcoin or wrapped BCH.
BC02BC06Difficulty responds through ASERT
SupportedThe BCHN upgrade specification describes activation of the aserti3-2d ASERT difficulty-adjustment algorithm in November 2020.
Layer North view: Difficulty responsiveness can smooth block timing after hashpower changes, but it does not prevent concentrated miners from censoring or reorganizing blocks.
BC05Current mining control is not identified
UnresolvedThis draft has not entity-resolved recent blocks to pool operators, payout coordinators, template providers, hosting firms, or miners that can redirect SHA-256 hardware among chains.
Layer North view: Displayed pool shares can understate common control and overstate committed security.
BC02BC05Scheduled upgrades require compatible economic and node adoption
The May 2026 rules were specified publicly
SupportedThe 2026 BCHN upgrade document specifies activation of Pay to Script, bounded looping operations, function operations, and bitwise operations by median-time-past conditions.
Layer North view: Public specifications aid review, but BCHN notes its upgrade repository is authoritative for BCHN rather than every possible client or economic participant.
BC03BCHN shipped upgrade-compatible software
ObservedBitcoin Cash Node release 29.0.0 states that it implements the May 2026 upgrade and urges older-node operators to upgrade for compatibility.
Layer North view: A released implementation does not establish actual version adoption, independent implementations, or absence of common-mode defects.
BC04Client and economic-node diversity remain unmeasured
UnresolvedThe public BCHN repository and documentation expose one implementation, while this draft has not measured alternative client use or the upgrade policies of exchanges, wallets, miners, and major services.
Layer North view: Consensus governance emerges from software, mining, and economic acceptance rather than a single formal token vote.
BC04BC06Provider supply and rank do not resolve ownership or liquidity
Reported supply follows a capped issuance model
QualifiedCoinGecko reports circulating BCH near the protocol's commonly stated 21-million maximum, but this draft has not independently recalculated the UTXO set, lost coins, fork claims, or freely tradable float.
Layer North view: A cap constrains nominal issuance; it does not establish beneficial ownership, usable float, or demand.
BC01Executable liquidity has not been tested
UnresolvedThe market-data source lists venues and a dated rank, but this review has not reproduced spreads, depth, slippage, derivatives leverage, custody, or withdrawal performance.
Layer North view: Market capitalization is not cash available to exit, particularly during a chain incident or broad deleveraging.
BC01Material risks and reassessment triggers
Impact labels are editorial judgments, not forecasts of price direction. Unsupported likelihood estimates remain unrated.
Mining-pool, template, and mobile-hashpower concentration
UnresolvedBCH proof of work is public, but the entities controlling blocks and the amount of economically committed versus redirectable SHA-256 hashpower are not reconciled.
Reassess when: A dated block-by-block study resolves pool operators, templates, payout addresses, shared infrastructure, hash switching, and reorganization cost.
BC02BC05Consensus-upgrade and chain-split coordination
SupportedScheduled rule changes require miners, nodes, wallets, exchanges, and other economic actors to deploy compatible interpretations.
Reassess when: Upgrade adoption, incompatible blocks, client differences, emergency patches, and economic-service readiness are independently tracked.
BC03BC04BC06Client vulnerabilities and deployment monoculture
UnresolvedA public BCHN release process exists, but the production client mix, node versions, security advisories, and patch latency are not measured.
Reassess when: A reachable and economically weighted node census is paired with a complete vulnerability, release, and patch-adoption ledger.
BC04BC06Ownership, custody, and executable market liquidity
UnresolvedReported supply and rank do not reveal lost coins, related addresses, custodian liabilities, derivative leverage, or stress exit capacity.
Reassess when: UTXO ownership ranges, custodian balances, venue quality, spot and derivative depth, slippage, and withdrawal tests are completed.
BC01Is BCH a good investment? Evidence to test, not a recommendation.
The report does not issue a price target. It shows the observations that support the case, the countercase, and the signals that could change either.
- BCH has direct native payment utility and publicly inspectable SHA-256 consensus rules.
- Difficulty adjustment, scheduled upgrades, and a major node implementation are openly documented.
- The May 2026 consensus changes were specified and shipped in advance of activation.
- Effective security depends on entity-level mining and template control that is not reproduced.
- Scheduled consensus upgrades create coordination and split risk across software and economic actors.
- Supply cap narratives and market rank do not establish diversified ownership or executable liquidity.
- Measure block production, templates, operator concentration, hash switching, and reorganization cost.
- Track client versions, security releases, upgrade adoption, invalid blocks, and chain incidents.
- Reconcile UTXO ownership, custodian exposure, derivatives, and cross-venue liquidity.
Claim-to-source record
Primary records establish documented rules and project-reported status. Dated measurements add observable context; neither substitutes for independent market, legal, or counterparty evidence.
Limitations, disclosures and change log
Known limitations
- Vinoth Kanna is the named analyst, but analyst sign-off has not been recorded for this draft. Jack General is the named reviewer; reviewer approval and independence have not been confirmed.
- No current hashrate, pool-operator, template, node, client-version, hosting, or economic-node dataset was reproduced.
- The UTXO set, issuance, lost coins, beneficial ownership, and freely tradable float were not independently reconciled.
- This is not a complete chain-split, reorganization, vulnerability, outage, or wallet and exchange incident history.
- No standardized spot, derivative, custody, slippage, or stress-withdrawal test was performed.
- Market rank is a dated CoinGecko snapshot, not a durable fact or quality score.
Report disclosure
- Sponsorship
- No project sponsorship has been disclosed for this draft as of 13 August 2026. This statement has not received final publication sign-off.
- Affiliate links
- No affiliate links appear in this report.
- Holdings
- As of 13 August 2026, Vinoth Kanna and Jack General disclosed no crypto holdings or other material conflicts. These are personal disclosures, not independently verified statements.
- Automation
- Automation assisted source collection and drafting; named human verification and sign-off are pending.
Created an internal noindexed BCH evidence draft separating public proof-of-work and upgrade rules from unresolved mining control, deployment, ownership, incident, and liquidity evidence.