A short synthesis. The Bitcoin landscape contains three chains carrying claims about what Bitcoin is. The Stoic philosopher Epictetus identified a framework for separating what is real from what is perceived. Applied to the three chains, the framework produces a finding the dominant discourse does not surface.
The Stoic philosopher Epictetus, writing in the first and second centuries CE, identified four kinds of appearances to the mind. Discernment in judgment, he argued, requires consciously holding these four categories distinct. The alignment between what is, what appears to be, and what is perceived to be is rarely as tight as casual assumption suggests, and the gap between them is where most error in human reasoning lives.
Real and perceived. The alignment is tight. What the mind perceives matches what exists.
Neither real nor perceived. The thing does not exist as it claims, and is not broadly perceived to.
Real but not perceived. The thing exists as it claims, but the perception of it has not caught up. The most dangerous category for the perceiver to remain in.
Not real but widely perceived. The thing does not exist as it claims, but is broadly perceived to. The most dangerous category for the system as a whole.
The third and fourth categories are where the captured information environment does its most consequential work. Category 3 is what gets buried under a discursive layer that prevents the perception from catching up to the reality. Category 4 is what gets constructed when a perception is sustained despite the reality not matching it. Both depend on the information environment producing systematic gaps between what exists and what is widely understood to exist.
Applied to the three Bitcoin chains, the framework produces a structural finding that the dominant discourse around Bitcoin in 2026 does not surface.
The Bitcoin whitepaper is the document each of the three chains claims a relationship to. Reading each chain against the whitepaper is the only way to determine which claim each chain's relationship actually supports. Nine pages of plain text. The load-bearing specifications are short.
"An electronic payment system based on cryptographic proof instead of trust, allowing any two willing parties to transact directly with each other without the need for a trusted third party."
"A new key pair should be used for each transaction to keep them from being linked to a common owner."
"The system is secure as long as honest nodes collectively control more CPU power than any cooperating group of attacker nodes."
"The network is robust in its unstructured simplicity. Nodes work all at once with little coordination."
The whitepaper specifies a peer-to-peer payment system designed to remove trusted third parties, preserve pseudonymity through fresh keys per transaction, defend against mining-based chain reorganization through honest-majority hashpower, and operate as a low-coordination network whose robustness comes from its unstructured simplicity. These are the properties against which each chain is measured.
The full documentary record for each chain's relationship to the whitepaper is in Vol.13 (the protocol-and-institutional analysis) and the BSV companion (the Wright-vs-whitepaper comparison). What follows is the distilled reading of where each chain falls in Epictetus's framework, with the supporting arguments referenced rather than reproduced.
The chain that most observers think of when they hear "Bitcoin" is structurally not the system the whitepaper describes.
The protocol now operating under the Bitcoin name has departed from the whitepaper at multiple load-bearing points. §1's non-reversibility property has been broken by RBF (introduced 2016, defaulted in late 2024). §2's coin-as-chain-of-signatures architecture has been broken by SegWit's witness segregation (2017). §7's pruning architecture and §8's SPV verification model have been degraded by SegWit's separation of authorization data from the original Merkle commitment; the original BIP 37 SPV mechanism the whitepaper describes has been deprecated by the development community itself. §10's fresh-keys-per-transaction discipline is not preserved by Taproot's aggregated-key direction. The 1 MB cap Satoshi described as a temporary anti-spam measure has been preserved for over a decade. Layer-2 architectures — Lightning, Liquid — have been positioned as scaling solutions despite operating as separate networks anchored to but architecturally distinct from the chain.
The August 2017 events were not a §11-style mining attack on transaction history. No party attempted to overtake the chain through accumulated hashpower; no party attempted to reverse recorded transactions through mining a longer chain. The UASF operation succeeded by capturing the economic-recognition layer above §11's defense — exchanges, businesses, and payment processors aligned with the UASF coalition publicly committed to following the UASF chain, making the existing-rules chain economically untenable for miners. This is structurally an attack on §1's anti-intermediation purpose (coordinating institutional layer reintroduced) and §12's low-coordination principle (high-coordination operation organized through specific channels). §11's broader principle that honest nodes following the existing rules collectively constitute the system's security applies in the broader sense: the existing-rules miners were the honest nodes, and a cooperating group succeeded at imposing new rules over their resistance through a mechanism §11 did not directly model.
The discourse surrounding BTC has explicitly retired the payment-system framing in favor of a store-of-value framing for institutional balance sheets. Saifedean Ammous's 2021 SALT podcast statement ("Bitcoin coming into those companies from the balance sheet, not from the point of sale"); Robbie Mitchnick's 2025 BlackRock framing on CNBC ("we don't see Bitcoin as a payment system"). The whitepaper's title — "Bitcoin: A Peer-to-Peer Electronic Cash System" — has been operationally retired by the institutional layer while the brand identity remains attached to the new use case.
The chain operates technically. The market capitalization is real. The institutional weight is overwhelming. But measured against the whitepaper, BTC is not the system the whitepaper specifies. The name persists; the substance has shifted.
The chain's central interpretive claim does not survive comparison with the whitepaper, and the perception of BSV as Bitcoin is not broadly held outside its own community.
BSV claims to restore the original Bitcoin protocol. The substantive content of that claim is articulated extensively in the public writings of Dr. Craig S. Wright, the figure around whom the BSV interpretive frame was constructed. Read against the whitepaper, those writings describe a different system.
Wright's blog states: "Bitcoin does not remove the need for all third parties" (against §1, which specifies removing trusted third parties). "In the new privacy model created with Bitcoin, transactions are no longer private" (against §10, which specifies pseudonymous keys per transaction). "Everything can be audited" (against §10's firewall between identities and transactions). "The myth that Bitcoin is designed to be censorship-resistant is just that" (against §11's honest-majority security principle). "A court order against four Bitcoin nodes may result in a transaction being required to be frozen and then reallocated" (against §1, which makes non-reversibility the property Bitcoin displaces). "What many regard as an immutable blockchain is not actually immutable at all" (against §11's proof-of-work immutability mechanism). The full pair-by-pair comparison is in the BSV companion document.
The Teranode infrastructure is real engineering. The multi-gigabyte block demonstrations are real. The on-chain scaling capacity is real. The chain operates technically. But the interpretive claim on which the chain's identity rests — that it represents what Satoshi specified Bitcoin to be — depends on a description of Bitcoin that the whitepaper does not support. The chain exists; the claim that constitutes the chain's identity does not match the source document the claim depends on.
BSV also lacks broad perception. Outside its own community, BSV is not widely understood as the legitimate Bitcoin even by observers who hold no investment in the BTC-vs-BCH question. The chain's position is contested at the level of public recognition as well as at the level of substance. Both axes of the second category — neither real nor perceived — are present.
The chain closest to what the whitepaper specifies is the chain whose perception lags furthest behind its reality.
The protocol that emerged from the August 2017 chain split, operating today as Bitcoin Cash, retains the whitepaper's load-bearing specifications at every point examined. §1's non-reversibility is preserved (no RBF; first-seen-safe applied at the protocol policy level). §2's coin-as-chain-of-signatures architecture is preserved (no SegWit witness segregation). §7's pruning architecture is intact with the original header-commitment property. §8's SPV verification mechanism (BIP 37) remains operational. §10's fresh-keys-per-transaction discipline is supported by the protocol; address-reuse is a user-behavior gap, not a protocol-level inversion. §11's security model operates with the rules the honest nodes were defending in August 2017. The block-size upgrade Satoshi described the path for in October 2010 was implemented, raising the base block size to 32 MB.
The empirical record matches the specification. Transaction analytics through May 2026 show 81% of payments in consumer-payment value bands, median payment $2.61, throughput well below the chain's 32 MB capacity ceiling because the user base is what it is rather than because the chain cannot accommodate more. BCH operates as a peer-to-peer payment system in the sense §1 describes — at the scale a payment system operates at, with the cost structure a payment system requires.
BCH is not perfect against the whitepaper. The address-reuse problem is present in default wallet UX. The L1 has not yet implemented native privacy primitives that would compensate for user-behavior gaps. CashFusion exists as an optional mechanism but is not in default flow. These are user-experience gaps, not protocol-level departures. They are addressable through wallet improvements without protocol changes. No chain in 2026 is perfectly aligned with every specification of a 2008 document; of the three chains, BCH is the only one whose departures from the whitepaper are user-behavior gaps rather than protocol-level inversions.
The perception of BCH is the structural problem. Most people who hold opinions about Bitcoin in 2026 have absorbed the framing that BCH "forked off" Bitcoin in 2017 and is the departure, while BTC is the continuation. Vol.13 documents at length how this framing was constructed — the asymmetric use of "fork" as terminology, the captured information environment that excluded dissenting analysis, the dismissal of substantive critique through identity attacks rather than engagement with substance. The result is the third-category position: the chain most aligned with the whitepaper is the chain least perceived as such.
A chain that both implements the whitepaper's specifications and is widely perceived as doing so does not exist in 2026.
BTC has the perception but not the substance. BSV has neither. BCH has the substance but not the perception. No chain currently occupies the first category — where what the chain is and what the chain appears to be are aligned with the whitepaper.
This absence is the structural condition the Deviant project is positioned in response to. The work is not to argue that BCH is perfect, or that BTC and BSV have no merit as engineering projects. The work is to surface the gap between what each chain is against the whitepaper and what each chain appears to be in the dominant discourse, and to enable the perception of BCH to catch up with the reality of BCH. When the perception of a Category 3 chain begins to catch up with its reality, the chain moves toward Category 1. This is the structural move the project exists to support.
The reading the framework produces is direct, and it differs from the dominant discourse around Bitcoin in 2026 in ways that are verifiable from the documentary record rather than dependent on interpretation.
Of the three chains, BCH is closest to the original. Not perfectly aligned, but closer at every load-bearing point examined in this corpus. The protocol-level specifications hold; the user-level §10 discipline depends on wallet UX that has not yet been built to enforce fresh-keys-per-transaction by default. The user-behavior gaps are addressable through improvements in default wallet design without requiring protocol changes.
BSV is not what its name claims. The interpretive frame the chain rests on describes a system that contradicts the whitepaper on §1, §10, §11, and the broader question of Bitcoin's relationship to authority. The technical engineering is real; the identity claim depends on a description of Bitcoin the whitepaper does not support.
BTC is no longer Bitcoin in the sense the whitepaper specifies. The protocol has been modified at multiple load-bearing points. The August 2017 events succeeded not by overwhelming the honest miners through superior hashpower but by capturing the economic-recognition layer above §11's defense. The discourse has been captured to make the modifications appear as continuity rather than as departure. The chain that appears to be Bitcoin to most observers in 2026 is not, in the structural sense that matters, what Bitcoin is specified to be.
The four-category framework does not produce these findings through interpretation. It produces them by applying a discipline that holds what is distinct from what appears to be, applied to material the reader can verify directly. The whitepaper exists; it is nine pages; anyone can read it. The chain implementations exist; their consensus rules are documented; their on-chain behavior is observable. The match or mismatch between specification and implementation is verifiable from the chains themselves. Nothing in this reading depends on the reader trusting the author.
What the reading does require is the willingness to hold the four categories distinct in the face of a discourse that systematically conflates them. The captured information environment's most consequential effect is not what it says about each chain — it is the way it makes the distinction between what is and what appears to be feel unnecessary to maintain. Once that discipline is set aside, the four categories collapse into one, and the reader cannot tell which chain is which.
The discipline is the corrective. Hold the four categories distinct. Read each chain against the whitepaper. Apply the framework to the appearances rather than to the chains directly. The findings emerge from the application; they do not require any external authority to confirm them.
This document does not ask the reader to trust the synthesis. It asks the reader to perform the discernment. Read the whitepaper. Verify each chain's consensus rules against it. Apply the four-category framework to what is found. Arrive at whatever finding the application produces.
If the finding matches the one in this document, the framework is doing its work. If the finding does not match, the reader has identified where this document is wrong and can act on that information. Either outcome is what the discipline is for. The unacceptable outcome is the one in which the reader accepts the dominant framing without applying the discipline — because that is the condition under which Categories 3 and 4 are sustained, and under which the gap between what is and what appears to be becomes the default state of public understanding.
This synthesis is short by design. The documentary substrate it rests on is in two longer companion documents.
Vol.13 — Bitcoin's history and the block-size war. The full protocol-and-institutional analysis of how BTC was modified, including the documented changes to §1, §2, §7, §8, §10, and §11; the August 2017 chain split read against §1, §11, and §12; the §7 scaling argument and Satoshi's October 2010 upgrade pseudocode; the Lightning trajectory and the gold-standard parallel; the institutional layer surrounding the development direction; and the constructed discourse that has sustained the perception of continuity despite the departures.
Companion — What the BSV — Bitcoin Satoshi Vision actually says about Bitcoin. The seven-pair comparison between Dr. Craig S. Wright's published writings about Bitcoin and the whitepaper's text. The structural finding that the Satoshi Vision Wright articulates describes a different system than the whitepaper specifies.
The reader who wishes to verify the synthesis above has the substrate available in those two documents and in the whitepaper itself. The substrate is the work; the synthesis is the distillation. Both have their place. The corpus is built so each piece can be read independently and so each piece supports the others.