Re:What Satoshi Did Not Know (2015) [pdf]
by garmaine on Saturday September 05, 2020 @06:57AM
(#24382719)
That’s not what “rewrite history” is generally accepted to mean. Substituting historical transactions with alternatives, and thereby reverting all dependent transactions is rewriting history. By doing so you can invalidate any transaction, so long as you control at least one input in the ever expanding web of prior transactions.
Re:What Satoshi Did Not Know (2015) [pdf]
by colordrops on Saturday September 05, 2020 @12:21PM
(#24384707)
But that once again is only current transactions. It gets exponentially harder to interfere with transactions with each block in the past. And if you just decided to do so with arbitrary hash difficulty to make it faster, it will be very obvious and easy to reject.
https://en.bitcoin.it/wiki/Weaknesses#Attacker_has_a_lot_of_...
https://bitcoin.stackexchange.com/questions/658/what-can-an-...
"An attacker that controls more than 50% of the network's computing power can, for the time that he is in control, exclude and modify the ordering of transactions. This allows him to:
* Reverse transactions that he sends while he's in control Prevent some or all transactions from gaining any confirmations
* Prevent some or all other generators from getting any generations
The attacker can't:
* Reverse other people's transactions
* Prevent transactions from being sent at all (they'll show as 0/unconfirmed)
* Change the number of coins generated per block
* Create coins out of thin air
* Send coins that never belonged to him"