|
Spain is not the place where broken people are being evicted from their apartments?
|
|
|
|
It is really hard to estimate the launch time. Every time we find a bug it needs again investigation, development and testing. But we cannot know how many bugs are left in the product. However, with the latest version 0.59.2 we have a pretty stable status. 0.59.3 will be even more stable. Also, we are running two nodes now with 0.59.3 and they are able to mine (so, yes, they are getting EXO in their wallet). You can test that once we release it.
Changelog of the next version 0.59.3:
- fixed udp reliable (you can now sync up the chain with even huge blocks with poor internet. This was not possible with 0.59.2 and prev. since packets got dropped then silently)
- re-broadcasts of miningResult/send_transaction only after initial verification and not directly
- fix bug in get_peerlist request (leaded from time to time to a crash)
- getPeerIPPorts and similar will no longer return pointers to the internal structs but hard copies. Added more setter to compensate. Clearer code design and fixed a crash issue here with two threads accessing pointers here without critical sections
- change popup title from "error notification" to "success notification" in case it is a positive message
- clear peer traffic user command works now
- fixed a small bug in chain sync process (not critical)
- GUI popup did not stay opened for some errors in sendTransaction() processing (e.g. "you cannot send yourself EXO")
- programmed eXowatcher (checks if the core process is running. If not -> restart after 5secs) and testing on one node at the moment
- added new column in block explorer, indicating if block has been validated through the network or not
- fixed a smaller bug in mining process (leaded to a critical section timeout deadlock)
- fixed a bug in the mining process (no transactions have been initiated previously due to this bug)
all points are done except the first one. Hopefully can finish that within 24 hours. It won't need a chain restart so its the first time that we can let the net run without any down times.
Best regards
eXocoin
#edit: the mining amount is spread equally within the miners. That will be changed of course in 0.6
Good news My client is running two days and have not crash any time.  |
|
|
|
Please send me: EXODrtmenqMeS1S1x3ZFE2m9mhuh5SMwc4ZNdbba  |
|
|
|
Well rome wasnt built in a day. Thanks for the update
As developer i would ask at least six months period for develop a currency from scratch and have something stable. |
|
|
|
I purchased a maximum round 2 eXocoin stake of 1.5 bitcoins that is held in escrow with anon136.
I would like to swap this for an equivalent value of Qora coins with someone who bought a stake in the Qora IPO.
I would prefer to swap with someone who used escrow for the Qora IPO, but if you are a trusted long-term forum user that would be OK
Please make an offer if you are interested.
Why do you think Qora is better than Exo? I had never heard. I saw that you have a topic here: https://bitcointalk.org/index.php?topic=522102.960I downloaded the beta and is in java. Should be "nxt clone" to have been done so quickly. #Edit: That's weird, java and some dlls have probably made in c.
Would have made an interface in java and put the pieces of bitcoin in these dlls? |
|
|
|
An idea. Thinking of what Mendel did with peas: http://en.wikipedia.org/wiki/Mendelian_inheritanceIf you put the temporary command while in beta to accelerate the generation of blocks. Could catch errors in less time, simulating the local network with empty blockchain. For example generate a block per second and miner + faster (all proportional). Am I right or wrong? |
|
|
|
as my previous post client crashes when a lot of transactions are genereated (appended to block?)
to launch client again i must delete the chain, resulting in no balance in wallet and no transactions made in blockchain/history.
Me too, I deleted blockchain in the client that crashed and disappeared a few inputs and outputs. In the other clients who sent and receive values keeps appearing. |
|
|
|
I started testing today V0.59 (local network and deleting the blockchain). It worked for a good time and a one client crash. Last lines of the log: [192.168.1.113:60639]: arriving block id=13 [size=22] ... arrived block has been integrated in chain. However prev. chain is corrupt regarding hashes. This is a critical bug. Please report to devs! Please delete chain and restart Complete Log: http://pastebin.com/TjiUNs6N |
|
|
|
nice If someone else tries this as well: Please note that you might need to wait some time after starting the first node to start the 2nd one who connects to it (at least 10 seconds, but waiting up to 20 minutes can be good to be sure). If the loaded chain is 0 then you should wait at least until block id=5 before connecting anything to it as well. added: Screenshot section on exocoin.orgHi eXo_coin, I continued my tests on the local network and it worked: 1- Deleted all blockchain in chain folder. 2- Waited until the fifth block, then open the other two clients in separate VMs. 3- Connected, generate the exo 10000 in all. 4- I sent values them all successfully. Has a bug: When decrypts the wallet and send values to the other, the value received, but the client that sent crash and close the windows. (testing on windows xp sp3). I was trying to test mining. I left a few hours, but received nothing. The wallet has to be decrypted for mining? I tested decrypted and crash after a time. Must be the same bug that I mentioned above. Is there any number XX block that must arrive before mining or any command that has to take to start? How many open clients do I need for mining? 2 node is fine for mining. You'll have to wait until block 100 (first transaction should be there after block 102), yes the wallet must be decrypted. Strange that you are experiencing crashes with decrypted client. Since I am testing a lot the first step after launching the client is decrypting the wallet most parts of the time So all transaction I have send in the last weeks has been successfully send with a decrypted wallet.... I'll look into it OK, to help understand, the transaction happens usually, the coin.exe keeps running what seems to be the crash in GUI. And this only occurs with an open wallet. http://s12.postimg.org/7z0090671/erro_decrypted_wallet.jpg |
|
|
|
nice If someone else tries this as well: Please note that you might need to wait some time after starting the first node to start the 2nd one who connects to it (at least 10 seconds, but waiting up to 20 minutes can be good to be sure). If the loaded chain is 0 then you should wait at least until block id=5 before connecting anything to it as well. added: Screenshot section on exocoin.orgHi eXo_coin, I continued my tests on the local network and it worked: 1- Deleted all blockchain in chain folder. 2- Waited until the fifth block, then open the other two clients in separate VMs. 3- Connected, generate the exo 10000 in all. 4- I sent values them all successfully. Has a bug: When decrypts the wallet and send values to the other, the value received, but the client that sent crash and close the windows. (testing on windows xp sp3). I was trying to test mining. I left a few hours, but received nothing. The wallet has to be decrypted for mining? I tested decrypted and crash after a time. Must be the same bug that I mentioned above. Is there any number XX block that must arrive before mining or any command that has to take to start? How many open clients do I need for mining? |
|
|
|
everyone knows Qora is created by BCNext, so it hurts if you compare it to emunie without any proof
 Edit: ...and most likely a Nxt Initial Stakeholder is behind eXocoin! I figured something like this since the beginning. I even have a hunch that I will keep to myself. No matter who is but the work he is doing. Someone who did not like some things in nxt, but never managed to convince the team to change plan. Things I do not like the Nxt who seem to be well resolved in the Exocoin: The java client (now with the interface wesley much improved, but that java window open all the time sucks), several others weird clients without the same core, few people with many nxt, making the distribution the most criticized part of the project. |
|
|
|
|
I am developer. Java is completely different from C. Would make a hell of work to adapt code. Perhaps the concept, some mathematical formula, but I would prefer to program from scratch.
Exo is the only currency that is not a clone and it is getting easier to use since the first version.
If nxt with first ugly java client, with all code in a single class, forcing the user to make one ".bat" was a hit, imagine the potential of the exo with all the functionalities promissed on the client.
Just need be thoroughly tested by the community concerned before release and if need be postponed until stay stable. One month more not kill anyone if the product to get better.
|
|
|
|
Wow is getting gorgeous. It will be much better than NXT was at launch. Please send any exo for: EXOExZ2TEsxmhUfY4pyBX4BbU3WdG1Aznmredbgb |
|
|
|
|
Hi, eXo_coin,
I know you have much more important things, but when left over time can do to minimize GUI to system tray. The console could be a GUI tab too.
This makes it easier to keep it working without disturb.
|
|
|
|
i will stay here waiting for exo launch.
today is another beta test i think. any news on launch date. iv heard may 11th which means your waiting a while lol right! Not sure when we will be ready for the delivery today. We will do it like the last time: Going to bed after publishing the update ;-) It surely can take some hours late in the night - please be patient. After some hours of searching, trying and failing we finally have been able to compile a win xp 32 bit version of the miner! It was caused by the (already integrated) openCL initialisation-part of the miner for the GUI implementation. With the latest version you can use the miner on xp service pack 3 (ok, we removed the opencl dependency for the CPU miner build anyway, but it works for the GPU miner then ;-) ) To make it short: All parts of the program can be used from XP32bit SP3 ongoing Thankful, I use XP in VMs of Virtualbox for testing. |
|
|
|
the aim for the next update (if everything wents well):
- improved cpu miner (fixed a potential crash issue there) including the complete process with payout processing (done!)
- stable client (lets see ;-) ) ->have some bugs fixed
- design and information representation improvements in GUI
- minor website design improvement, content updated and reworked
- specific timeline
- using eXoProxy on some VPS' and hidden server in the background (probably 5 proxy + 5 hidden server)
- sending automated mails to all mail applicators (approved/denied with reason)
- get the buggy udp-reliable class working
- much more content in the wiki.exocoin.org (especially sourcecode snippets (!))
eta next update (v0.58): 30th April - we cannot finish it today, I am sorry to say. However, the website changes, mail sendings and timeline can be finished today - wiki partially as well - I guess.
Nice The miner was tested on Win XP? It would be nice to put the link of logo in the first post https://bitcointalk.org/index.php?topic=574490.40The "gvans" logo, was very good, in my opinion. |
|
|
|
|
Show Posts
