[PoS+PoW] eXocoin [EXO]-gen 2.0- dev. from scratch! Give-Away | Open Beta

[hala]

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.

[Passion_ltc]

I can't come past block 57.

[mrvegad]

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.

[hala]

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.

 i agree with you.
 according to current status ,  we are wait more 2 weeks ,but the blockchain still has the seriously problem. the dev should use different approach . its more necessary. dont be absent after releasing the client, you can delay to release client for having a good rest.

[gilbertzk3r]

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.

 i agree with you.
 according to current status ,  we are wait more 2 weeks ,but the blockchain still has the seriously problem. the dev should use different approach . its more necessary. dont be absent after releasing the client, you can delay to release client for having a good rest.

Dev is too tired,we need some more patient.

[eXo_coin]

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

[frankkkkkkk]

dev,please answer me,when can i see the final wallet?

[hala]

dev,please answer me,when can i see the final wallet?

  keep silent. wait until dev investigate the issue .

[hala]

everyone should keep silent, I wait too long with hope. wait until dev investigate the issue .

[blackhatzw]

there are always issue in the new launched software, it's normal, found issue then fix them this is the right way.

[rramires]

The greatest truth in software development:
http://en.wikipedia.org/wiki/Murphy%27s_law

[gao_fu_shuai]

f*ck kao cao,when can exo lauth realy?

Go to hell,its your right path.
BTW,if you want sell your stake,PM me.

[hala]

 yeah , I admit we wait too long and have a great hope for this coin , but you must believe the dev team have more pressure , we should understand them.

so just hope them rather than do some meaningless things.

[blauebohne]

From my own experience I can tell: When writing a programme about 80 % (or even more) goes into debugging and sometime it can be really frustrating. Be patient! Remember: exocoin code is written from scratch and great things may take some time.

[hypersire]

From my own experience I can tell: When writing a programme about 80 % (or even more) goes into debugging and sometime it can be really frustrating. Be patient! Remember: exocoin code is written from scratch and great things may take some time.

Totally agree. Let's just have a little more patience - we are very close now and it is obvious that they devs are going to keep working on the bugs until we have a stable client. I rather they take a little more time than release a client that is full of bugs.

[hala]

From my own experience I can tell: When writing a programme about 80 % (or even more) goes into debugging and sometime it can be really frustrating. Be patient! Remember: exocoin code is written from scratch and great things may take some time.

Totally agree. Let's just have a little more patience - we are very close now and it is obvious that they devs are going to keep working on the bugs until we have a stable client. I rather they take a little more time than release a client that is full of bugs.

 I trust dev that they will fix the issue ASAP.

 the great change had happend. 

[rramires]

I do not know if it helps. I left my client running since yesterday in the amazon server and seemed fine. Arrived at block 87.
Now i deleted the blocks, rebooted dai gave the problem mentioned.
My log:
https://mega.co.nz/#!W4JX3TAT!7jwiBJYdwH3EN-vbJZdLjYiBD7Zh57p-d9U3YA9Umg4

[blackhatzw]

From my own experience I can tell: When writing a programme about 80 % (or even more) goes into debugging and sometime it can be really frustrating. Be patient! Remember: exocoin code is written from scratch and great things may take some time.

Totally agree. Let's just have a little more patience - we are very close now and it is obvious that they devs are going to keep working on the bugs until we have a stable client. I rather they take a little more time than release a client that is full of bugs.

agree, I am a tester in Microsoft, generally speaking, we submit more than 5000 in just one release, many of them are urgent, and there are many release until releasing a stable product, so the current status is very normal, we just keep on testing and testing till a stable client.

[rramires]

And yesterday was Friday the 13th. Jason cut the chain.  

[rramires]

From my own experience I can tell: When writing a programme about 80 % (or even more) goes into debugging and sometime it can be really frustrating. Be patient! Remember: exocoin code is written from scratch and great things may take some time.

Totally agree. Let's just have a little more patience - we are very close now and it is obvious that they devs are going to keep working on the bugs until we have a stable client. I rather they take a little more time than release a client that is full of bugs.

agree, I am a tester in Microsoft, generally speaking, we submit more than 5000 in just one release, many of them are urgent, and there are many release until releasing a stable product, so the current status is very normal, we just keep on testing and testing till a stable client.

Exact! And yet the windows says "blue screen" in the hand of the CEO, even after many tests.