TRANSACTIONS & WALLETS INFORMATION OF ELECTRONEUM
IMPORTANT NEWS
TRANSACTIONS & WALLETS
We hear you.. and we’re here to help you!
Over the past few weeks, some of you have experienced transactional issues which have generated many support tickets, particularly relating to incomplete transactions.
We are aware of the problem we have now identified the cause and, as a result, we are implementing a number of substantial changes to our back end transactional system. More enhancements are planned over the coming week, delivering significant transaction handling improvements across other areas such as error handling, volume, success rate and scalability.
Before we launched, we had designed the system and, under load, ran various test environments, all of which scaled nicely. Now we’re in a real environment that is much larger than we ever could have imagined, new issues have emerged such as worker nodes occasionally being out of sync but reported as being in-sync; and some transactional anomalies and corrupted wallets have occurred because of this. We are repairing wallets as fast as possible, and appreciate the patience of those affected as we await the time needed to re-build and sync with the blockchain. This sounds a little scary but please don’t worry, a corrupted wallet does not impact your balance on the blockchain – we can always recover it.
So, what else? We’ve made improvements to our node servers and are adding new code to verify, and double verify, that the node is in sync with the master blockchain before allowing a transaction to take place. We also have new code being released that detects and automatically rebuilds corrupted wallets as soon as they’re identified, plus many, many more changes that will enhance speed and function.
Next week, once all these code enhancements have been deployed, we’ll work through any other outstanding anomalies to make sure everyone’s transaction list is accurate and up to date.
During this period, we’d be so very grateful if you could try to avoid raising any more support tickets. This is because, as a known issue being actioned, these will not be registered since the work being done should resolve the issues.