Right now, the Smart Contract is run once by a miner (A).
If that miner (A) crashes or the execution did not create a new transaction, the next elected node (B) will react and execute the contract. If B's execution also result in a crash or no new transaction, the next elected node (C) will react an so on.
Describe the problem you discovered
Right now, the Smart Contract is run once by a miner (A). If that miner (A) crashes or the execution did not create a new transaction, the next elected node (B) will react and execute the contract. If B's execution also result in a crash or no new transaction, the next elected node (C) will react an so on.
We need a way to avoid that behaviour.
Describe the solution you'd like
No response