Topic: [PoS+PoW] eXocoin [EXO]-gen 2.0- dev. from scratch! Give-Away | Open Beta - page 212. (Read 415634 times)

,
How much are you paying? Considering how the danger of scam is pretty much over now that the dev is still working post-IPO, it would have to be a sizeable markup for me to even consider it.

Anyone selling their stake?

You don't need to hope, it actually is.

I hope that it is becoming more and more good!

Great progress!

It is turning out to be more than I thought it would be.

Definitely exceeding my expectations.

this coin looks promising. I missed IPO. will buy some coins on launch

glad to hear news from dev team.

hope exo could launch as soon as possible.

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

Once the client is running, I create 10 000 test exo, trasnferred a bunch to different accounts.

A few minutes laters, all my exo disappears from the balance along with transaction history.

just tried out the client for the first time today... fantastic progress! keep up the great work team EXO, this has some real potential as opposed to 90% of new coins that are just copy and paste jobs.

Deleting wallet.exo should do the trick. Of course your old address is unusable after that.

Looking forward to seeing more about this project! 

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!

So I am trying to create a new account but the prog won't allow me.

I tried all combinations and formats it has requested, but it still won't allow me to create a new address.

Nothing changed

顶一下先

I generated 10000 coins this morning, and now the network connection is 4, a little less than this morning.
I sent 12.34567 coins out to the above address.

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.

How i am receiving new blocks? Now 52

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