transactionX (ex: which send 10 ether to
minerM), and this is deployed via
minerM on the block #100.
mineM is an attacker, and it is consecutively elected as a leader on block #101, 102 ...
From the example above, attacker realizes that
transactionX sends money to itself and want to re-deploy same transaction on a new block.
minerM or any other miner re-deploy the
transactionX again, even the
userA didn't submit it on the second time?
I know it is now possible but:
[Q] How Ethereum-Virtual-Machine prevents miners to sent the same transaction, as accepted, more than once in different blocks?