kaal:claim:3441904-024

Hard forks can reintroduce the double spend problem, because wallets, merchants, and users running the previous code deem the new code invalid and cannot detect spending on it, so coins spent in a new block could be spent again on an old block.

Source quote, verbatim
Because wallets, merchants, and users running the previous code deem the new code invalid and thus cannot detect the spending on the new code, cryptocurrencies spent in a new block could be spent again on an old block.
From

Wulf A. Kaal, Blockchain-Based Corporate Governance (2019), III.5 Socially Optimal Forks, p. 21
https://ssrn.com/abstract=3441904 · source PDF

Cite as

Wulf A. Kaal, Blockchain-Based Corporate Governance (2019). SSRN: https://ssrn.com/abstract=3441904

Holds when
Classification

mechanismsupport: arguedfailure: fork-induced-double-spendfamily: consensus-and-protocol-attackconsensus-and-securityeconomics

Related claims
Verify

The quote above is an exact substring of the source PDF, whose sha256 is e6b562527f7f19accaa35491db0a0db168b6a936755e1dca424e9f30bee7a815. Extraction method: pdf-text-layer.
Attestation record: colloquium/attestations/22413f64ec348c41...json
Verify the binding yourself: curl -s https://wulfkaal.github.io/claims/3441904-024.md | sha256sum