Look at ntp and the block sizes should be the same size, nodes should also use ping to show that they are responding.
if there are no txs then why does it need to create blocks?
The nodes are pinging each other from time to time.
Well, what is the drawback from generating empty blocks? Especially if time goes by there won't be any empty blockes in the future. Blocks are generated in a fix 10 minute intervall and making any special rule there wouldn't bring advantages.
The overhead of (empty) blocks in one year is only about 1mb.
Let's celebrate 200 pages. I am honored to be a part of EXO and will be stay with EXO to support it as long as possible.
Thanks
200 pages is at least something
The coin will be released when it is ready - those trying to rush this out are asking for a lower ROI.
But everyone hopes that this will be happened within weeks, not months or years
Of course, but I am sure the devs are motivated enough without pressure on here to rush out a buggy product.
Be re-assured that we won't release a buggy version
We could have rushed a somewhat finished product, release that, get all coins from Anon136 and go away easily some month ago without much hassle. Since we did not you can be sure that we want to have a rock solid and great product.
still working on the bug.
As for the chain async: [...]
Must be one of those bugs that you take 99% of the time (days) to find and 1% to settle.
I tested using 3 VMs here since yesterday. I did a macro to click the "generate 10,000" button.
It took a few minutes but then everything synced without error.
[img...]
Thanks and good luck
Indeed, we could not recreate the problem until now in our closed testnets. Before someone is claiming now, how we could solve an issue that we could not reproduce - well, we are quite convinced after several tests that the issue is caused by the amount of many connected clients in connection to at least some initiated transactions. So we changed something in the handling there. Additionally we fixed another thing in the block(chain) classes and added more security features. Most important (maybe) if a chain async occurs again, the network should fully recover itself within a few seconds without any drawback. After that process all clients should be back in sync automatically. That is also good if you think of malicious network attacks. The clients can easier see if the network health is lower than normal. In later versions this could be used to prevent users from initiating transactions or to warn them. The maximal amount of connected clients will be limited as of 0.61 (that obviously does not apply to the official nodes and can be freely set in the options menu).
its not the truth. I think he is watching World Cup and drinking the beer.
well not much time unfortunately
But I watched some at least.
Boy
yes, we are males.
I allready propose to make a correct french translation a month ago, still waiting for dev's answer..
Indeed I forgot about that. Sorry. We got a reply from the original author of that translation and he made me believe that it is not a google translation. But if it is not good enough from your points of view (we do not speak a single word french) then a new translation would be good I guess (with the current, updated information).
[...]
It would be great atleast update first page with that link to sourceforge...
good idea - first post contains now a link to sourceforge and a notification that eXocoin has not already launched.
Also added the link to the wiki mainpage.
Devs should communicate lot more with the community or ask somebody to act as PR Person for this coin! Should they have solutions to the chain async problem today ? Or was that time-estimate again delayed
Absolutely agree. Pr should be done before launch. Many devs ( i dont talk about exocoin) dont understand, that good product is not enough.
As you do not talk about exocoin I don't have to justify ourselves here. Anyway I want to assure that we understand that a product itself is important but that the greatest program is nothing without proper marketing, communication and so on.
Problem is limited manpower and that priorization must apply somehow. Moreover, if you "get stones rolling" and more and more people get attracted but the product itself is not finished/buggy they can get quickly mad. If you loose a customer once he will most likely never come back. So what I try to say: We want to have a finished product first (in terms of stability and releaseability, not talking about marketplace and other on-top features). After a redesign of the website and a good working client on all major distros (windows, linux, osx) it is much easier and successfuller to advertise eXocoin. But you can have a different opinion - this is our point of view.
Current status of eXocoin in general:
As you can see in our bug tracker there are quite some points (and some are still open). With the 0.61 release we will have solved the major bugs and improved the client with some suggestions (if everything goes well).
OSX developement made huge progress as well. We might release the osx client with 0.61 or otherwise with 0.62.
From 0.61 ongoing we will host our download area content within sourceforge for better download performance and public viewable download statistic.
Timeline (oh well, our timelines hardly have been accurate in the past I must admit - maybe we can get better...) :
- coding 0.61 finished: on 30th June
- publishing changelog: on 30th June
- testing everything and fixing issues caused by 0.61: 1st July - 3rd July
- uploading everything, set up the network and so on: late 3rd July
- release of 0.61 immediatly thereafter (3rd - 4th July)
best regards
eXocoin
