Execoin: | First Open-Source Stealth Wallet Released! | Fast | ASIC-proof

[NineEleven]

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!

ExecoinJ has been updated, would appreciate if you try it and give a feedback!

Just updateded my wallet and resync from scratch

Started  my ScryptN rigs @3.6 MHS and found block 307795 and 307796


Seems ok

[gyruss]

ExecoinJ has been updated, would appreciate if you try it and give a feedback!

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.

[execoin]

ExecoinJ has been updated, would appreciate if you try it and give a feedback!

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 testing!!!

>I notice that ExecoinJ does not seem to have the logic implemented to calculate the reward of a block (GetBlockValue).
True!
>Is that necessary or does the standard getBlockInflation() in ExecoinJ work?
getBlockInflation() is enough.
Please upgrade with jar rebuilt from ExecoinJ, wipe the chain and resync.
New version of ExecoinJ shouldn't go that far (323,000 or so), difficulty retarget algo (DGW) parameters have been changed and new version shouldn't accept blocks from nodes that haven't been upgraded. New version may stuck on higher block earlier received from old nodes, but it could not advance and download/accept blocks from old nodes. The same applies to any client.

[jwinterm]

Why still frozen on poloniex if things are moving again?

[gyruss]

Thanks for testing!!!

>I notice that ExecoinJ does not seem to have the logic implemented to calculate the reward of a block (GetBlockValue).
True!
>Is that necessary or does the standard getBlockInflation() in ExecoinJ work?
getBlockInflation() is enough.
Please upgrade with jar rebuilt from ExecoinJ, wipe the chain and resync.
New version of ExecoinJ shouldn't go that far (323,000 or so), difficulty retarget algo (DGW) parameters have been changed and new version shouldn't accept blocks from nodes that haven't been upgraded. New version may stuck on higher block earlier received from old nodes, but it could not advance and download/accept blocks from old nodes. The same applies to any client.

Great. I wiped the chain and resync'd, still got up to 323093. I see on http[Suspicious link removed]coin.net that the highest block is 307924. I'm going to wait for a bit to retest. I may be just connecting to a bad node. For the record, I am currently playing around with WalletTemplate. It's taken quite a bit of work to just get going on it, so I'm not counting out an error with my own shenanigans. Will keep you posted.

[cyberguru]

Just as a precaution we removed dynamic block reward code completely and increased number of blocks considered in DGW to 60.

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

[execoin]

Just as a precaution we removed dynamic block reward code completely and increased number of blocks considered in DGW to 60.

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

KGW has been replaced by DGW v3. Solves Time Warp Vulnerability in KGW. In addition, DGW is much more responsive (mitigates multipool issues better) and up to 50 times faster (this is important for non-C++ SPV clients in Java and Python language).

Base reward reduced to 20 coins per block. This reward then reduced gradually by 2.5% every week.

[cyberguru]

Base reward reduced to 20 coins per block. This reward then reduced gradually by 2.5% every week.

Sound's ok & simple.  In 3 months, exe will beat vert....

[execoin]

If your wallet shows "Out of Sync" and "0 hour(s) behind" at the same time, as a temporary workaround you can create execoin.conf file, and put the following lines into it:

listen=0
connect=95.85.26.197
connect=107.170.240.30
connect=162.243.136.142
connect=128.199.233.179
connect=198.211.100.64
connect=192.241.152.198
connect=107.170.79.10
connect=37.139.3.206
connect=188.226.169.188
connect=107.170.227.175
connect=128.199.221.109
connect=107.170.227.176
connect=188.226.169.189
connect=192.241.128.215
connect=107.170.79.12
connect=107.170.12.174
connect=188.226.130.205
connect=95.85.39.247
connect=192.99.166.230
connect=192.99.166.231

These are all working nodes above.

[execoin]

Execoin has been restarted from block 307770, bugs are fixed.
Please update your wallets (important!) and resync.
Source code is on the Github, Windows wallets have been updated  (Mac's one will be updated later).

If your wallet shows "Out of Sync" and "0 hour(s) behind" at the same time, as a temporary workaround you can create execoin.conf file, and put the following lines into it:

listen=0
connect=95.85.26.197
connect=107.170.240.30
connect=162.243.136.142
connect=128.199.233.179
connect=198.211.100.64
connect=192.241.152.198
connect=107.170.79.10
connect=37.139.3.206
connect=188.226.169.188
connect=107.170.227.175
connect=128.199.221.109
connect=107.170.227.176
connect=188.226.169.189
connect=192.241.128.215
connect=107.170.79.12
connect=107.170.12.174
connect=188.226.130.205
connect=95.85.39.247
connect=192.99.166.230
connect=192.99.166.231

These are all working nodes above.

We updated ExecoinJ Java library, SPV clients (Exelite, Android and Electrum) will be updated later.
http://explorer.execoin.net shows actual state of the network.
Just as a precaution we removed dynamic block reward code completely and increased number of blocks considered in DGW to 60.
Please help the developers by means of informing exchanges, pools, node OP and merchants about restart.
Your help will be greatly appreciated!

[Lovok]

Lovok's EXE P2Pool node (http://lovok.no-ip.com:9173) now with updated wallet and resynced.

Please avoid using nodes with unknown wallet version (unupdated) as it causes problems to whole p2pool network.

[oni4an]

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

Thanks.

[maxsinner]

Just as a precaution we removed dynamic block reward code completely and increased number of blocks considered in DGW to 60.

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

KGW has been replaced by DGW v3. Solves Time Warp Vulnerability in KGW. In addition, DGW is much more responsive (mitigates multipool issues better) and up to 50 times faster (this is important for non-C++ SPV clients in Java and Python language).

Base reward reduced to 20 coins per block. This reward then reduced gradually by 2.5% every week.

Is there a minimum reward or you are reducing it by 2.5% every week even if te rewards drops below 1 coin per block? If the latter is the case, then it might make sense if you go PoS at some point?

Could you please also correct OP with the right information? We have currently:

Technical Details

    Algorithm: Scrypt-Progressive-N with optimized schedule (scientific name: scrypt Salsa20/8(N, 1, 1), PBKDF2(SHA2))
    Symbol: EXE
    Max Coins: 84 million
    Block time: 45 seconds
    Subsidy: halves every 840,000 blocks (~437 days)
    Difficulty Re-Target Time: Every block (Kimoto Gravity Well)
    Block Rewards: 50 coins per block

[CryptoLTD]

My wallet is stuck @ 311803, with the following nodes in conf file:


connect=95.85.26.197
connect=107.170.240.30
connect=162.243.136.142
connect=128.199.233.179
connect=198.211.100.64
connect=192.241.152.198
connect=107.170.79.10
connect=37.139.3.206
connect=188.226.169.188
connect=107.170.227.175
connect=128.199.221.109
connect=107.170.227.176
connect=188.226.169.189
connect=192.241.128.215
connect=107.170.79.12
connect=107.170.12.174
connect=188.226.130.205
connect=95.85.39.247
connect=192.99.166.230
connect=192.99.166.231

Any one have any advice?

[Rednocker]

Repair Poloniex please 

[CryptoLTD]

Repair Poloniex please 

exchanges wont come back online untill things are fixed

[CosaNostra]

Hi everybody!
Can you please tell me where to get correct Windows wallet?
Thanks!

[CryptoLTD]

Hi everybody!
Can you please tell me where to get correct Windows wallet?
Thanks!

Not sure..the one I Downloaded last night is stuck. Even after creating my own conf as directed by the dev, as seen a few posts ago.

[CryptoLTD]

Something is definataly not right as the 'offical pool' is showing block #309320 here -->  http://pool.execoin.net/index.php?page=dashboard

Yet my wallet is showing stuck for 12 hours at block 311803.

Looks like there is more work to be done.

[oni4an]

my wallet is ok