When the chain forks, let suppose that the network followed the stronger chain. If some transaction in the stale block is not duplicated in the chain is it reversed?
If the fork extend to some number of blocks, is not clear to me if is possible (and if is easy) a node verify transactions considering two chains, so it make sense to revert transactions from stale blocks.
...
Now say the chain fork at 5 and the old 5-6-7 were overwritten.
1-2-3-4-
5-6-7What happens is this, if your node is up that you sent your transaction out on, it will see the fork and try an resend the transaction
so instead of your transaction being included in block 7, it will be included in a later block.
In the new chain your transaction would be in block 8 or later. (depending on when you brought your wallet online)
1-2-3-4-
5-6-7-
8Now say you had your wallet offline and knowing about the fork, decided you wanted to doublespend.
What you would do is keep your current wallet offline, export your private keys,
create a new wallet & import your private keys into it. Delete your old wallet.
(Even easier just restore the wallet from a backup before you send out the coins on the original fork.)Now you can bring your new wallet online, which won't resend your old transaction.
This transfers your balance but excludes the transactions, so that the transaction is not resend and you double spend.
...
That is not quite correct. When the chain is re-orged, then all transactions in the stale blocks that aren't already in the new chain are returned to the mempool. The result is ultimately the same, but it is not necessary for the wallet to resubmit the transaction.
The double-spend happens when a transaction in the new chain invalidates a transaction that was previously confirmed in the stale branch, and the already confirmed transaction is rejected. In order to do that successfully, that attacker must be able to add blocks more quickly than the rest of the network so that they can force a re-org with a branch containing the double-spending transaction. Such an attack requires more than 50% of the total hash rate, and that is why it is called a 51% attack.
