The whitepaper describes nodes validating transactions and blocks before extending the proof-of-work chain.
Consensus & securitySourced answer
Can nodes reject a longer proof-of-work chain and still claim Bitcoin rules?
“Honest nodes follow the longest proof-of-work chain. Rejecting a reorganization because it is called dishonest replaces consensus with authority.”
Short answer
The answer without the theater.
The whitepaper describes nodes accepting valid blocks and extending the proof-of-work chain. Proof of work does not make an invalid transaction valid. The contested BSV question is broader: current rules also define legal and commercial obligations, directive mechanisms, and possible block invalidation. Calling an attacker dishonest is not enough; operators need precise, published validity and intervention rules with observable incident handling.
What is true
The objection's strongest ground
- The whitepaper's node steps require transactions and blocks to be valid before proof-of-work ordering matters.
- BSV's published rules add an explicit legal and institutional layer to node conduct.
- A post-hoc label is not a usable security control; detection thresholds, authority, communications, and recovery behavior must be known in advance.
What remains unresolved
Do not claim more than the evidence
- This brief does not determine whether a particular historical reorganization contained invalid transactions or breached a contract.
- Following more work alone does not solve eclipse attacks, double-spend exposure, or application confirmation policy.
Inspect it yourself
A better next move than arguing
- Compare whitepaper steps 1–6 with the node's current chain-selection code and configuration.
- Read which NAR events can lead to block invalidation and who may issue the directive.
- For every historical incident, publish block hashes, chainwork, invalidity claim, decision authority, timing, and operator action.
Open to better evidence
What would change this answer?
Clear ex-ante rules, public incident data, and independently reproducible node behavior would reduce ambiguity. Secret, retroactive, or inconsistently applied rules would make the criticism stronger.
Evidence behind the answer
What the cited sources establish
The current NAR permits directives that can include invalidating specified blocks after defined events.
Source desk
Read the underlying material
PrimaryBitcoin: A Peer-to-Peer Electronic Cash SystemThe original paper; read its proof-of-work, incentives, privacy, and SPV claims in their own terms.Satoshi NakamotoPrimaryNetwork Access Rules — Part III, Enforcement RulesDirective events, restrictions, and permitted steps including freezes, reassignment, peer controls, and block invalidation.BSV AssociationPrimaryBSV Alert System documentationTechnical description of signed informational and directive messages delivered to nodes.BSV AssociationPrimarySV Node configuration referenceCurrent operator-facing configuration surface, including chain and policy controls.BSV Association