BCH breaks the very first part of the whitepaper, being a t…

BCH breaks the very first part of the whitepaper, being a timestamp server. Transactions are not sorted by time, but are required to be sorted by hash. Obv nodes can decide to change the order if they wish, however BCH enforces hash sorting of transactions in blocks, which breaks the whitepaper. As for BTC, SegWit and Taproot breaks the whitepaper as it changes the transaction format as the whitepaper states that the signature is stored alongside the public key in the transaction, not separately like what SegWit does. As for Taproot, it breaks that each signature is validated separately from each other.