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

[kirivas_s]

is exo ready for release as v0.61 is stable?

[zhile11911]

is exo ready for release as v0.61 is stable?

 there are stable as far as now .

 you should  read the devs latest post

[DishCatcher]

is exo ready for release as v0.61 is stable?

Not yet.
More blocks needed to test the stablity until we reach #500 and dev still have GPU miner unimplemented.

[zhile11911]

Hey...  why am I being left 1 block behind locally?  

 dont know why ? my friend had same problem at block 236 . and he restart and its OK .

 i guess maybe you internet connection is down , or else something is wrong.

#update my block is 232, you should check you internet connection at first.

[eXo_coin]

Hey...  why am I being left 1 block behind locally?   

 dont know why ? my friend had same problem at block 236 . and he restart and its OK .

 i guess maybe you internet connection is down , or else something is wrong.

How does it affect the client / how did you noticed? Don't you have a green check symbol after - let's say - 15 minutes after syncing is completed? What is the output of "get block information" ?
Note, that the latest block in the block explorer should be exactly equal to: block reported from "get block information" minus 1. (Latest block won't show up at any time there).
If so, you may send the err.log file of that program run to admin@exocoin.org if you like. Maybe the log will show what went wrong.

Nice job devs, block 500 would be around this weekend, so could we expect launch early next week? or when v .62 is done?

We'll publish a roadmap later this day or tomorrow, please wait for it

#

So I have to restart the PC force the client to close any time  I want to exit and restart exo client.

This is a screenshot of the error (it goes by very fast so I was barely able to capture it) - Windows 8.1 64-bit:

"Program already launched.  No second instance allowed."

 (... image ...)

The client shows up as a background task yet I am not able to open it from the task bar until I force it to close in Task Manager.

reboot your computer. Problem is already told here, only fix is reboot (or maybe search in to ur taskmanager) i just reboot system

Interesting. How did you shut down the first program instance? Did you closed it properly with the "X" of the gui, or did you closed the console window or something?
Exiting the process in the task manager will work at every time, the reboot is not needed but if you like it is possible of course.
The overall integrity shouldn't be threated if exited with task manager.

Anyway we will take this into our bug tracking system

Hi exo dev, as more and more **coins demonstrate that the coin block time can be reduced to about 1 minute in the present and the future tech, so could eXocoin change the block time 10 minutes to 1 minute?

 which of the future tech ?

 some people told me that the aim of the block time 10 minutes is to a fair POW distribution . everyone has the chance to mining coin. 

 so its not a tech difficulties

Well, what is the real advantage of a 1 minute block time? You think of faster confirmation speeds? We are thinking of a concept allowing faster confirmations than the block time. More to this point later on.

[eXo_coin]

maybe let me add:
it would not be a big deal to decrease the block time (in our closed alpha we usually take 2 minutes), it is just a parameter. Anyway we would prefer to make faster confirmations independed from the block time and to decrease block-syncing load it is better to stick with 10 minutes in our opinion.








#edit: I just added a sleep(5000); before the return in case of the "Program already launched.  No second instance allowed." issue. At least you'll see that error message then in 0.62 before it quits

[LemonAndFries]

So I have to restart the PC force the client to close any time  I want to exit and restart exo client.

This is a screenshot of the error (it goes by very fast so I was barely able to capture it) - Windows 8.1 64-bit:

"Program already launched.  No second instance allowed."



The client shows up as a background task yet I am not able to open it from the task bar until I force it to close in Task Manager.

reboot your computer. Problem is already told here, only fix is reboot (or maybe search in to ur taskmanager) i just reboot system

oh ok, didn't know

[LemonAndFries]

So I have to restart the PC force the client to close any time  I want to exit and restart exo client.

This is a screenshot of the error (it goes by very fast so I was barely able to capture it) - Windows 8.1 64-bit:

"Program already launched.  No second instance allowed."

 (... image ...)

The client shows up as a background task yet I am not able to open it from the task bar until I force it to close in Task Manager.

reboot your computer. Problem is already told here, only fix is reboot (or maybe search in to ur taskmanager) i just reboot system

Interesting. How did you shut down the first program instance? Did you closed it properly with the "X" of the gui, or did you closed the console window or something?
Exiting the process in the task manager will work at every time, the reboot is not needed but if you like it is possible of course.
The overall integrity shouldn't be threated if exited with task manager.

Anyway we will take this into our bug tracking system

I used "X" at first and then noticed the exo icon was still in the System Tray.  So I tried clicking on it to see if the "minimize to tray icon" worked.  It didn't but the icon disappeared.  I tried to restart the GUI but it gave me that error "program already launched."

I then used task manager to kill the exo client and then I was able to restart the GUI.

I did notice that if instead of doing the usual left-click on the tray icon, I did a right-click the menu to reopen the client would pop-up and then I was able to open exo GUI just fine.

[eXo_coin]

ok, thanks for clarification / testing.

We will investigate this. https://sourceforge.net/p/exocoin/tickets/43/


best regards

[eXo_coin]

How does it affect the client / how did you noticed?

I shutdown the client (clicked red X button) and when I fired it up again it wouldn't sync.  

Unfortunately...  I was too eager to get synced again and started from scratch so I don't have an error log to send you.  Everything is up and running now.  If it happens again...  I'll make sure to hold on to the error log.

If you restart the client immediatly after a shutdown, then it most likely wont sync. That is something that we have experienced as well in the past but forgot about it...
I just found the reason for it.       https://sourceforge.net/p/exocoin/tickets/44/
It shouldn't happen again in 0.62 ongoing.
So - thanks

[eXo_coin]

Roadmap will be published tomorrow, not now.

Network still looks good, the official nodes neither report network health warnings yet nor have we experienced any chain asyncs yet.
Anyway, as stated, we want to wait (at least to #500 or something) and don't want to declare 0.61 as stable too early. Also, we need to wait for the start of mining to see if that works as expected, too.


regards
eXocoin

[yweetot]

288

[hala]

sometimes it difficult to sync , it was block at nearly 95% .

 i have to restart (sometimes the sync was ok when opend) , whats worse, i must delete the chain folder and sync from beginning  in sometime.



 the sync took 30 minutes to sync

  

 then i restart and sync is ok immediately

 

[benyate]

Roadmap will be published tomorrow, not now.

Network still looks good, the official nodes neither report network health warnings yet nor have we experienced any chain asyncs yet.
Anyway, as stated, we want to wait (at least to #500 or something) and don't want to declare 0.61 as stable too early. Also, we need to wait for the start of mining to see if that works as expected, too.


regards
eXocoin

we are expecting you to make a decision！

[baby222]

   everything is nice , i think will launch soon , stay turn   

[Youghoor]

Roadmap will be published tomorrow, not now.

Network still looks good, the official nodes neither report network health warnings yet nor have we experienced any chain asyncs yet.
Anyway, as stated, we want to wait (at least to #500 or something) and don't want to declare 0.61 as stable too early. Also, we need to wait for the start of mining to see if that works as expected, too.


regards
eXocoin

thats looks great as with that many will able to know the progress of this coin.

[Fern]

Here is my address EXOy3dptN9qN8NHy4mxrY4FqrYbWqKuysOp8dcke

What's yours? Lets get some eXo sloshing around the crypto world.

[paulchch]

Let's see where this goes!  

[paulchch]

Fern I sent you 5000.  Hmm then 10 minutes later, the app crashed.

[paulchch]

Thanks smaragda.  Came through ok, but I wonder if the crash occurred when you sent the exo to me?