No. Every node on the network already knows about every tx. The hash of the transactions does not serve to hide the txs or prevent them from interception. It is used ONLY as a....
You say no but then don't prove it. Every node knows about each tx yes, but not the order they will be blocked. So... With CTO they will, and it is more susceptible to fuckery.
knowing the order of txs in a block. That's not how the encryption is used, or even works. Txs are hashed ONLY as part of merkle tree, meaning they only matter for the past blocks.
It's got nothing to do with encryption, but everything to do with determinism. And deterministic systems are more susceptible to attack. This is a fact that you have refused to admit.
The universe is deterministic. Bitcoin uses that determinism via of encryption and game theory to work. Read up and stop using buzzwords like you know what you're talking about.
You're just bleating on off on a tangent. You still haven't admitted that deterministic systems are easier to attack. CTO is another attack on the chain's protocol, like Segwit.
The points you've made don't disprove my statement that random ordering of transactions in blocks makes the system safer so I have no need to. Also learn how to thread replies 👋🏼
Determinism is necessary for literally any computer system. There are some parts of encryption (priv/pub keys) where we DON'T want determinism. For example, you shouldn't...
Yep, the same private keys that are deterministic-ally generated by a pseudo-random computer program, and then deterministic-ally used to calculate a public key and address.
No, you are showing a fundamental lack of understanding of the encryption behind bitcoin and the reason txs are hashed in the first place. There is no possible fuckery behind...
A) verify hash matches the blocks txs B) So the hash can be used to calculate future blockheaders, therefore cryptgrphcly proving the block is built on a valid tx history(merkle tree)