At 5% solo mining is reasonable decision.



I think, it's a security issue. Coin stay low, so admin pool activity stays low. Admin need to confirm all payouts manualy... It's just therory . BTW, when pool admins switch pay off, they know when to put buy orders on market... .


Not so bad idea, if you quit, someone else can mine more easily.

BTW, Ive switched mining for monero & vert, selling them & buying exe. It's more profitable, for long term. Emission of coin decrease 2,5% / week. Practicalyy we don't have inflation. In period of month, coin gain 25% of value / satoshi, . Cryptsy market was incorrect, no deposits was there. Poloniex show the truth. next 3 months, will show the future of this coin.

whats happen with official pool? Stratum subscribe time out error appears....

Thanks I was able to run dumpprivkeys() from console and got the keys.

Can you tell me where I can download Electrum-Qt?  I downloaded Electrum-EXE 1.9.8.4 but it not connecting to the servers. 

And When I go to Wallet->Private Keys->Import it gives me this warning

Imported keys are not recoverable from seed. If you ever need to restore your wallet from its seed, these keys will be lost.

Are you sure you understand what you are doing?

Clearly i don't so please advise if that is what I should be doing? 

But WHY qt-wallet loose sync frequently.

Just import one priv key to wallet and soon it show just ok. After fifteen minutes I look agen and think I send coins to other address. What hell... wallet is out of sync.
348292 and now waiting estimated block number 363763. (Edit: just now 5.50AM GMT)

With different times, different numbers it loose sync. Sometimes restrat help shortly, sometimes it soon return this kind of state when it get more connections.
Now there is one connection and situation is "out of sync" and this totally wrong block count what it is waiting. Where from it get this wrong data?

Agen day what I can not move my coins due to this hassle with sync.

Two days ago I send over 10k EXE and it fails. Wallet tell balance zero after send and block chan Explorer tell coins sit still in  addres and have not moved. After hours waiting and in this time walllet was also later sunc, I stop waiting. (transfer status in wallet was just ?).

I delete wallet dat (name it agen) and start new. Agen it get sync, then Private key in and it show agen balance. I send agen it to this other address. wallet then zero balance, this ok, and show transfer status ?. Agen wait long time, restart wallet two times. Some times it sync. But coins did not go to other address where I send these.
Agen wallet dat rename and start new. Import priv, agen it show balance ok. This time wallet stau sync and I send coins and this time it success.

What are these sync drop outs with wrong block numbers from some node?

If this can not solve it destroy this coin. What there so difficult to keep nodes in sync so that there is not agen and agen this wrong fork on the air. Who is running this wrong fork and why?

Wallet sync issue is NOT solved.

Still frequently it get some wrong block count from somewhere.
Wallet tell  somettimes out of sync and is waiting some "futuere" blocks. But current block is same what is block Explorer.

It have happend so many times that this is perhaaps some kind of attack...  please shoot down these assholes or we can wait infinite to get example cryptsy back.

We do not need more and more C class exchanges but we need these some  A  class exchanges work. Two good is better than handfull bullshit.  They can not open depsit wallets agen if wallet is every night out of sync.

Just now, here qt-wallet have zero active connections. This happend several times per day. Sometimes it run several hours until it tell out oof sync and waiting some future block number. (example now it waits 361802 what is totally wrong)

I haven't heard a word from the dev if this will ever get fixed felt scammed into transferring all of my coins into a wallet they know wouldn't work after fork. 

Soon it looks like "How easy is destroy one coin" case. This do not feel good at all.

Now I understand why Cryptsy, Bitrex, Comcort etc do not start agen full service with EXE. Also if this hassle continue I believe Poloniex need interrupt EXE.
How to continue if wallet do not sync reliable. Now example in my case there is three connections to Network but it stay block 337469 (now 45 hour beghind)

Well I deleted block chain n chainstate from my app data roaming, put in my old wallet..and re-synced.. this new fork isnt recognizing my old coins, even from a fresh qt and syncing.. I think i'm done here. If im having this issues, so will exchanges. Some one message me if this ever works again.

I installed this  electrum-exe . org/stealth/ but it always offline.   How do I get it to sync with the network?

Well I deleted block chain n chainstate from my app data roaming, put in my old wallet..and re-synced.. this new fork isnt recognizing my old coins, even from a fresh qt and syncing.. I think i'm done here. If im having this issues, so will exchanges. Some one message me if this ever works again.

Because it's a command line option that you use at launch?

repair Poloniex.com, http://www.coinwarz.com/cryptocurrency

Thanks.

Well.. Im synced again..but my old coins are unconfirled..and my new coins are confirmed.

So, what's is "the main difference", made in last hardfork? Need numbers & info about inflation, please.

For a moment, i'ts sounds, like a tons of chip coins, with multipool "time wrap" fixed

Cool, thanks for the update. I notice that ExecoinJ does not seem to have the logic implemented to calculate the reward of a block (GetBlockValue). Is that necessary or does the standard getBlockInflation() in ExecoinJ work?

Looks like I will have to wipe my chain and resync. Just re-running put me at 323,000 or so. I'm retesting now!

Thanks again.

Thanks for the update. A couple of question:

• Will the restart happen at 307770
• Will you also be updating the SPV code (ExecoinJ)? I've been experimenting with it and get up to 307769, and then a bunch of non-connecting block errors.

Thanks again!