I can't come past block 57.
block 58 is quite big. How long did you tried it? Did you have tried to restart again or to delete the entire chain folder?
So it aint working ? Devs should use different approach with new version and stay online after releasing for while.
This.
I am starting to question how serious the dev is about this. Not being here when a new version is released to answer questions isn't a good move, doesn't build community spirit which a coin needs in order to be successful.
dev is busying in the product , he works day and night ,so the client had a great change .
dev should need time to have a sleep after releasing software, as he said, he will back after 12 hous. In other words, you cannot do things well
if your lack of energy
But, the blockchain is broken down quickly , just about 40 block id = 6 hours. Are the dev have a stress test ? I am a little suspect.
I was involved with another coin project where there was only one dev and it was more complex then exo and whenever he would release a new beta the dev would be up for 24hrs. Maybe if the exo dev would be online when people are testing a new beta then maybe he would be able to get a better idea of what is happening. Testing this on the dev computer is a lot different then having it run on 20plus computers.
due to various issues we have made the night before through to get the update released. Besides, our log files will help us to see what happened.
The blockchain got a async between block 45 and 46. We will collect our error logs and investigate again. Sorry that this problem occured again.
tried to send 999.99 but the client sends 1000.88
888.998 889.88
888.889 888.7
111.991 112.81
11.9 11.9 ---- this is ok
11.199 11.199 --- this is ok
11.99 12.8
88.98 89.78
11.91 12
11.92 12.1
11.93 12.2
11.933 12.23
11.934 12.234
Confirmed, the first few give the same result here
Had a similar thing with
1.001 1.1
1.01 1.1
Interesting. This surely is a result of changing the internal storage of the amounts away from double. We did not found such a glitch in our tests but we -as it seems- changed something after the test. We will look into this of course. Thanks for reporting.
After investigation of logs we'll give you a new status update. Although the chain is broken all of your initiated transactions (and those which will be initiated now or in future) should be still there.
a sidenote: you will experience that from time to time you will regain the green check arrow. Although this is an advantage (syncing up after a broken state) to the latest tests it did not fixed the issue at all (and it does not happen so often than we expected).
regards