eXocoin is not designed to be used by pools at all. And as S3MKi correctly stated it is a slightly disadvantage if there would be any pools. It's a new and innovative mining architecture in that respect. People with great number of GPU will get more coins from mining proportionally. There is no drawback to mine eXocoin for "big players" or for average users. Nearly all (there are limits to both - low/high end of hardware of course somewhere) will get proportional output.


We will take the outcome of this vote in consideration.
best regards
eXocoin

#edit multipool is a different aspect. That cannot be targeted in time I guess. We will talk about this soon.

that's what I tried to express in my latest post #2209. Please re-read ;-) We are considering to do that and I think it is a really good idea.

That would be adequate. We could start on June 1 or/and make a non-linear block-amount function, starting with a bit less, increasing over the time to a max after 6 months. So the total amount would not change but distribution would initially kick in a bit slower/smoother. Anyway, there will be at least a 2 weeks gap no matter when the launch day will be.

Ok, most VPS crashed at some point of time, our local wallets crashed on average after some hours as well. So it is not an issue within the GUI but within the core client itself (GUI builds just on-top). It is caused by one of the parallel threads.

Lets outline the positive aspects first:
-> the mining integration (atleast what is implemented yet) is functional
-> in contrast to the previous update the processing of transactions and integration in blockchain works well as far as I can see.
-> the chain is close to be in sync (see next aspect)
-> invalid messages at certain points of time will not be processed from any node (guards and message checks looks really good now)

What wents wrong at the moment:
-> VPS and clients are crashing from time to time, blockchain is out of sync
      -->from what I can tell: the async is this time caused by the crashed VPS and not due to buggy code directly linked to chain sync but investigation needs some time
     -->that is an improvement from latest versions where chain asyncs occured with functional clients

What can improve the client:
->find and eliminate all crashes in core client. That increases stability and might get the chain in sync at any point of time. Just restarted 3 VPS and we get again 4 official VPS back in sync automatically! That is really a good improvement. The resync/replace mechanism works well as it seems.

We will follow this roadmap:
->rescan the whole code, especially the critical sections, guards and threads, review all delete ([]) and new ([])
->publish large parts of the code in our wiki
->deliver next update, including: bugfix, full operational block explorer search (there was an vector.clear() missing so it shows only one transaction due to boundary checks ->already fixed for next version, allow search for txid, blockid), more functional mining process, allow more than one miner to connect to the client (that is possible, but both miners would mine at the same value ->different seed offsets needed), interest calculation process
->Make final thoughts about API interface, make wiki page especially for potential exchanges to see what the interface will look like.
->Set up UDP server for API remote interface communication, maybe RPC implementation as well
->buy more VPS to set up proxy<->backnet idea (see latest changelog) ->efficient security against early DDoS after official launch
->Unix version will not be delivered before launch  since we already have enough work to compete with. Working on this if we have time or if someone from the community is eager to do this after we fully release the source code (possibly some days after launch). Partial integration of UNIX is already within the code.
->marketplace integration will be targeted after launch as already communicated
->due to the latest problems we must delay the launch. We cannot and we do not want to launch a buggy product. At least the nodes must be able to run some days without any chain async or crash. We want to set a new ETA that is somewhat challenging, but realistic. Delaying an ETA to the next ETA to the next ... is not a good style as well. I am sorry for the delay. I hope you can understand that and see the need to have a stable product at launch.
Besides: This gives exchanges some time to adapt to eXocoin. We would like to have at least one exchange one week after the launch.
->develope GUI  miner using OpenCL early May
->validate all mail applications (small c++ program to download bitcointalkmember list already programmed)


Timeline:
-> next udpate: Hard to tell. The last updates ETAs have been postponed always at least some hours up to 1-2days. That is not a good style but it is difficult to predict. I would say we can deliver an update on monday or tuesday.
-> launch ETA: sunday, 11th May



I hope you understand our changes and see that it is not reasonable to launch eXocoin before May. The new time can be used to make the product more stable, implement the essential missing features and adapt to exchanges.

Thanks and best regards
eXocoin team


#edit: it should use quite exactly 100% CPU on one core from blockstart till found a result. Until the next block it should stay at 0%. With V0.59 you can launch more instances (for one processor one). But that is not essential. The CPU miner will be somewhat a demonstrational purpose as long as we do not have a GUI miner.

going to read the posts here in the thread since my latest post tomorrow - going to answer the PMs from today tomorrow as well.

Just want to say now: The update V0.57 is near to be ready for public testing (most important: we found and fixed a major bug, change the chain sync process slightly and added more guards to validate transactions and blocks). However, we do not have yet everything done that I have announced to have ready for this update. We will take the next hours to continue programming and we are going to publish the update before going to bed (well. that would be latest 2:00:00 GMT if everything wents well) as well. If some features cannot be programmed in time then it will be part of 0.58 but we want to release the next update today.

regards
eXocoin

I'd like to wait for the results / stability of the next update (release: late tomorrow) first before confirming the ETA 30th or not. If it is stable then we are still on track. If not we possibly need to delay it. So let's wait what the next update will look like.

I contacted Poloniex and wait for an answer now.

All PMs until now are processed (checked from page 1 to latest)! If I missed you - please PM me again.

thanks for the celebration  

here is what we have calculated (I'll check those numbers again tomorrow just to be sure):

first round:
65.159 BTC directly
322.450758 LTC directly
90.663216 BTC via escrow (Anon + 3 other escrowed transactions not with him)
341.2812 LTC escrow (all with Anon)

LTC -> BTC conversion rate: 1.5 BTC == 50 LTC

first round total (sum): 175.7345961 BTC


2nd round:
29.8063 BTC escrowed (all with Anon)
87.49165256 BTC directly

2nd round total (sum): 116.6380 BTC

[[sum both stages: 292.3725487 BTC ]]

100,000,000 EXO -> 50,000,000 for mining + 4,000,000 for giveaway after launch and bounties + 4,000,000 for mail giveaway + 42,000,000 for 1st and 2nd stage -> == 100% distribution after 6 months (end of mining).


initial spreading for 1st/2nd stage regarding current spreading plan: 23,500,000 EXO 1st stage + 18,500,000 EXO 2nd stage. To face the fact that there have been more investments in 1st than in 2nd round we have changed the proportions to 26,000,000 EXO 1st stage + 14,000,000 EXO 2nd stage (this procedure has been communicated here: http://exocoin.org/index.php?s=about#timeline (last lines of page)). There have been more email applications lately so their block increases back again a bit to 6%.

That means:
1st stage 1 BTC investor gets:  147,950.3784 EXO
2nd stage 1 BTC investor gets: 120,029.5418 EXO

advantage of being 1st stage investor: 123,26% -> nearly 20% as communicated earlier

Obviously if you invested more or less than 1 BTC just multiply your value with that. E.g. a 0.7 BTC 2nd stage investor gets 0.7 * 120,029.5418 EXO

mail applicants: each valid application will get at the moment 6,000,000 / 1500 people =~ 4,000 EXO (equals a 2nd stage investment of 0.033 BTC)
Note: mail applications have not been verified yet. So the number still can decreases or increases. The possibility to apply for the mail giveaway will end on 23th April 23:00:00 GMT.





Correct me if you find any mistake in the calculation. As stated going to recheck those number and the transaction lists tomorrow again just to be sure.
These information will be displayed on our website as well tomorrow.




The next beta update cannot be delivered today unfortunately. Please wait until tomorrow for the next version. Thanks for patience and understanding!
btw: the used algo for the mining will be a new combination that have not been used before. More information at a later point.


best regards
eXocoin


#edit: Going to answer all PMs that have not yet been answered in less than 12 hours.

We will allow the user to choose between ed25519 ("ec 256 donna") and  X9_62_prime256v1 ("ec 256 nist") and rsa 2048 ("rsa 2048") on each new address creation like it is in our beta versions. So it will not be changed. It is perfectly fine to allow more than one signing method.

I'm in contact with Anon. Just waiting for a final answer to have the exact number for the calculations.

Yeah well, once it is somewhat stable we will have an always running testnet. We do have the hope that the next update will be stable for more than 10 hours. Although we did not spend much time today since it is eastern we found already a critical bug in the block_done_sync thread and fixed it. That caused at least an async on one node, maybe on a second one as well. More about our progress and changelog within the release of the next update (v0.57). Like with all updates so far we do keep the approach to not only have a bugfix update but also show some progress at least with every update. ETA still very late monday or tuesday.


regards
eXocoin

thanks for the positive feedback. Glad to hear that many of you appreciate the work we already put into eXocoin. It is still not releaseable until the chain will not get out of sync anymore. Additionally rechecking every security threating code passages is required and the release of that code passages in our wiki.
The next version ETA late monday or tuesday hopefully contains:
- working CPU miner and (partial) integrated workflow of the mining process (miner.exe will be delivered with this update)
- reworked udp reliable send class
- a step towards interest calculation
- no more stucking on chain sync (well over 50% of the cases should be automatically detected right now, aiming for 100% in that version)
- change address state of an EXO address (you can disable an EXO address. If it is fully disabled it will not used in send_transaction anymore AND cannot receive coins from anyone else). This feature could be used for an IPO for example when you want to close a stage you could simply disable the address. So there are 4 possible values for each address: ENABLED (default), DISABLED (both ways), SEND_ONLY, RECV_ONLY
There might be more use cases for this feature like if you want to control from what address you send your EXO in a transaction (if possible regarding balances of course) or if you are an escrow provider and want to ensure that the escrowed wallet addresses will not be touched in send_transactions. An exchange provider who wants to enforce that the customers use everytime a new EXO address when transfering coins into the exchange then the exchange provider could easily disable an address automatically after the first received transaction. On the sender's side he will get a notification if he tries to initiate a transfer to a disabled address.
- create_checkpoint function (not visible right now, tests in later versions)
- more function in block explorer
- fully functional sign&verify dialog processing in the GUI wallet tab
- bug fix to latest chain async
- bug fix to hala's problem if invetigation finds something


best regards


#edit:
Yes the processing of transactions is buggy since ~10am. All nodes are refusing to process transactions since they are out of sync to each other. That will be investigated thoroughly and hopefully fixed in the next version (see above). Unfortunately as for now it is "normal" that all new transactions are vanishing. All nodes might get completly shut down in the meantime until the next update without further notice.

#edit2: I probably will not look into bitcointalk on easter sunday. Have a good time and see you again on monday
regards
eXocoin

thanks for all suggestions so far. I must say there are quite some good suggestions that would be suitable for eXocoin! I think we should take some more time and then do a vote again. We do not need to change the logo before the official launch I would say. Besides: The current logo is not that bad. The creator of the chosen logo will get a medium bounty on top. Others might get a minor bounty as well.

Did you even read my reply to your last post here in the thread? I told you to please be patient since I am highly busy. I am sorry but I cannot do everything at once.
Secondly, what are you worried about anyway? We already have agreed on the bounty? About what should I have lied? PMs are going to processed in some hours.
Well what is the error message? Do you wanted to create the very first address or a seconds/third.. one? If so you should know that all addresses must have the same passphrase. If not, please post an example passphrase that you have tried.
Ok that is very strange. Did you ever got a connection (in an earlier version maybe)? Also, what OS are you running and do you have a soft- or hadrware firewall? Maybe within a company network? If so, those security solutions might block in AND outgoing connections of that port. If so, please try to open 60637-60642 (udp, not tcp!) to have all ports opened that eXocoin will use.


Good easter time to everyone!

You do not receive blocks but you continue to generate blocks on your own. That is normal

peers.exo looks valid. At least
>>active: 192.3.134.164:60639
>>active: 192.3.52.31:60639
>>active: 192.227.237.33:60639
should respond to you!

It seems that you have been blocked by that nodes. I do not know why at the moment but they are blocking many peers ...
You may close the program, delete the chain folder, wait 20 minutes and retry.
Sorry for the troubles.. working on the next update already.

strange. Please copy&paste the peers.exo (open with normal notepad editor) here.

well that you will not get the 10,000 is normal if you do not have any connection. Besides - the processing of transactions got corrupted becaused of a chain async. But you should have at  least 3 connections. Are you sure that you have updated to V0.56? Check debug-> get version
Only the latest version will get a connection to the network since we use different ports on each new update as for now.

If you have the correct version please try "check peerlist" in the debug tab and see if that helps

Well at least it should not be the cause - the system surely must be capable of dealing more transactions per second. Additionally everything looked quite well even after the blocks containing 70 / 45 / 44 etc transactions. It will take a deeper look into the error.logs and code to say what went wrong.
Thanks for reporting that it uses exponential format. Just changed it to the "normal" representation.

Yes, very likely. Unfortunatly I am getting that as well plus messages like "chain out of sync->skip". Checked the official nodes and those continiously displaying similar messages. Thus: I would say no new transaction will be processed anymore. Well :/ cannot say right now why that happened but I guess we need to wait for V0.57. Since eastern we cannot deliver an update before late monday I think. Restarting the nodes without bug fix does not help much.

#edit exokk and me took the next week holidays. So we will have some more time to work on eXocoin

yeah.. just got a fresh copy and there is no 77 EXO. At least it is a good thing that it vanished in your local copy (of course it would be better if it had been processed but at least it tries to present the real situation )

Lets see if the 78 will come across or not

I see the 100 EXO now in block explorer.
Good news: the chain update did not stuck anymore in my latest tests (got stuck but then moved on after a retry after 5 sec).
Good news: transactions are processed nicely and well in the new queue since latest update.
bad news: nodes are out of sync since ~10 minutes. You may not experience a difference at all since all nodes are still running and processing transactions. However we need to investigate again, of course.

#edit may I am wrong. Cannot see the 77 EXO ... we will give you a status notification what went wrong in some hours
#edit again: it cannot be in block explorer yet lets wait some minutes to get the block into the explorer