Updated the
end of 2nd stage investment (we did not say a specific time yet) on our website (about tab): only 0.02 to 1.5 BTC will be considered. No LTC/NXT/... will be accepted for the 2nd stage. 2nd stage investments possible up to
14th April 23:59:59 GMT. If you have send a PM to eXo_coin (see below why) until that point of time you can be granted to invest at the next day and it is still valid. Just PM before 23:59:59 GMT.
ok we are going to check the error logs and chain status on our server. After investigation we will deliver an update or a time frame when the next update will be available. Please stay patient and sorry for the troubles
eXocoin
Already found something. Here is an first explanation and time frame for a solution:
state of the network:- all server are still running and building up the chain (all server are at the same block id, all server are synced regarding network time)
- no server is answering the get_block question from any node anymore because of a specific rule/flag that kicked in
- some peers get blocked since they answering the current block question with -1 which translates to the highest unsigned int on the way to the node and is therefore missinterpreted (easy to fix)
- clients are calculating the latest valid hash. If it does not match their own then they ask the _valid subset_ of nodes to get their block (that is working great)
- clients are asking everyone in a subset parallely. (note: this does not cause any trouble right now. But it is a bad behaviour anyway)
- clients send transactions directly or - if the next block is build within the next seconds - wait up to 10 seconds for the next block (that is working but can lead to an asynchron chain state)
fix/solution:- send transactions directly regardless of time/block status. That causes some more coding since the receiver must store it in a asynchron chain. The sender is transmitting how long the receiver should wait before processing the message (that would enable users to send transactions at a specific later time if wanted, also usefull for the implementation of the standing order feature by the way)
- increasing block time to 5 minutes
- eliminate the specific rule/flag. While doing this the clients must do more work to validate arriving blocks. I am not going to explain it here further but there is some coding work to be done when removing this flag
- clients should stop asking all nodes in a valid subset. Better ask randomly one. If he does not answer go on with the next node.
what happens after the fix?- the "up to 10 seconds wait time in client" would be eliminated. Some transactions get processed faster then.
- server and client node load should decrease drastically (way less get_block queries and block creations), however, this does not caused the troubles we have right now (the server surely must be able to handle a lot of more clients in the future).
- transactions have a higher possibility to be integrated in the right block on all connected nodes = more synchronity
- confirmations of transactions might be delayed to more than one minute (well right now the user does not get a confirmation at all...)
- our nodes should communicate again once they are out of sync. Right now it looks like "flag is set -> do not send block back to node" the next one thinks the same. In the end they cannot sync up anymore once the flag kicks in but continue to build up the chain on and on.
- after calculation of valid block hashes the requestor = client requests the block only from peers that had have the valid result
- the nodes are checking each arriving block if they requested exactly that one (they do already do this once they are synced. But they should do this as well before they are synced starting with block id=1)
- 1 more VPS is available
We are glad that the system is still running and that the cause of these troubles are relatively easy to fix. However some coding must be done so the next update will be available on 14th April we believe. Thanks for your understanding.
#edit if you are still worried that we are going to scam you please be patient and wait for the 6th investment stage that will kick in in ETA late January 2015
