You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when a TX is being submitted mining stops completely. If a TX reaches max retries, it will spend the remaining time of that minute trying to find a hash. It would be optimal if in the background (whilst the tx is being submitted) the next hash was being mined in the background.
The text was updated successfully, but these errors were encountered:
I'm not sure this is actually possible. I think maybe until you submit a solution, you get the same challenge as before. I don't fully understand it yet though.
Currently, when a TX is being submitted mining stops completely. If a TX reaches max retries, it will spend the remaining time of that minute trying to find a hash. It would be optimal if in the background (whilst the tx is being submitted) the next hash was being mined in the background.
The text was updated successfully, but these errors were encountered: