>>8112177>>8113277>>8112405>>8113505>mainly to try to find that bug where "duping" occursThis is what it looks like on the history ui.
To anyone else viewing, it looks as if the transactions are "duplicated" and done twice
When the authenticated user does their next tx, they can see that the transaction was reversed / didn't happen, cooldown didn't change, balance and amts reverted etc. and should try again
The reversal is never broadcast, (I doubt it's intentional to begin with) and thus for everyone else viewing its as if the cooldown was bypassed (in reality the reversed tx didn't even happen, thus no cooldown was bypassed. If cooldown bypasses / dupes were doable I think we'd be seeing ppl with more than normal amts of EN2 coins, and while I can see the extra buys happening on the broadcast, I didn't catch anyone with extras in their public wallets, but then again I might have not looked hard enough)
In the meantime scripts that look at the timestamp will simply resend the tx, since for all intents and purposes it didn't actually happen.
On the bright side as far as the logs i've manually sifted through there's no advanatge to be had
The byproduct is simply extra history entries
> when has code ever done exactly what you wanted it to do.multithreading: now it breaks at random times in random places
debugging mutexes and ACID(wikip) issues, 0/10
Would a failed transactions in past hour ticker on the top bar help users identify if their script is messing up?
