[ANN] Cannabis Industry Coin XCI anon blockchain for the legal marijuana.GUI UPD

[GorillaPool]

Ok, right, Goriilapool is brand new   Will investigate miners loss later maybe will merge redis dbs.
Now it is flushed and running on new redis to avoid wrong tx from wrong chains.
Mine at http://gorillapool.org - Resynced - Flushed -  

[GorillaPool]

Network seems to agree with attacker.
On the other hand just right now network==attacker.

Attacker is moving from pool to pool now, don't agree with you - network =\= attacker.

[GorillaPool]

http://gorillapool.org/ is on right chain because resynced - flushed and


http://gorillapool.org/  - good chain

http://xci.acidminer.org/ - good chain

http://democats.org/blockchain/?name=xcicoin - good chain


http://xci.cryptonotepool.com/ WRONG

xci.ms-pool.net.ua - not working

[niko2004x]

http://gorillapool.org/  - good chain
http://xci.acidminer.org/ - good chain
http://democats.org/blockchain/?name=xcicoin - good chain

In this chain last ~300 blocks was mined by attacker.

[GorillaPool]

http://gorillapool.org/  - good chain
http://xci.acidminer.org/ - good chain
http://democats.org/blockchain/?name=xcicoin - good chain

In this chain last ~300 blocks was mined by attacker.

This is possible but this is the right chain! Resync will show the truth. Just made it and flushed pool redisdb. It is clean that this chain is the right chain. Attacker got about 3000xcI 

[MainCoins]

http://gorillapool.org/  - good chain
http://xci.acidminer.org/ - good chain
http://democats.org/blockchain/?name=xcicoin - good chain

In this chain last ~300 blocks was mined by attacker.

seems to be correct

Code:

# date && for i in http://xci.mypool.name:42004/stats http://pool3.democats.org:7713/stats http://gorillapool.org:8117/stats http://xci.acidminer.org:8117/stats http://xci.cryptonotepool.com:8119/stats; do echo -n "$i: is at " && curl -s $i | jq .network.height; done
Thu Dec 22 13:30:31 CET 2016
http://xci.mypool.name:42004/stats: is at 41921
http://pool3.democats.org:7713/stats: is at 41921
http://gorillapool.org:8117/stats: is at 41921
http://xci.acidminer.org:8117/stats: is at 41921
http://xci.cryptonotepool.com:8119/stats: is at 41659

[niko2004x]

It seems I was right.

Network seems to agree with attacker.
On the other hand just right now network==attacker.

[niko2004x]

It seems now attacker moved to gorillapool.
Could pools just firewall-out nicehash IPs?

[SparkIt]

It seems now attacker moved to gorillapool.
Could pools just firewall-out nicehash IPs?

Indeed.

[GorillaPool]

Now he is on both http://xci.acidminer.org/ and http://gorillapool.org/
Nicehash is changing IP for every new order. We can ban a range of IPs but we should do it together. That would be a good solution for now. BipCoin dev is saying he can help with XCI forking.

[cryptomaxsun]

Help is needed.
From unknown causes the collapse of the wallet.
 how to recover the wallet,  know key?

[GorillaPool]

Small problem: reset 
Huge problem: resync+reset 

[cryptomaxsun]

Small problem: reset 
Huge problem: resync+reset 

Wallet initialize failed: can't load wallet file 'pool.wallet', check password

file wallet: pool.wallet 0 kb
other file   pool.wallet.tmp.73d9-ec4a   8812210 file size

how to recover the wallet?

[MainCoins]

Small problem: reset  
Huge problem: resync+reset  

Wallet initialize failed: can't load wallet file 'pool.wallet', check password

file wallet: pool.wallet 0 kb
other file   pool.wallet.tmp.73d9-ec4a   8812210 file size

how to recover the wallet?

I would try to rename the file: pool.wallet.tmp.73d9-ec4a -> pool.wallet

pool.wallet is  0 kb as you see, so resync would not help I guess.

[aiwe]

If you want to prevent Nicehash to connect to the pools just set up difficulty below 10000 i.e. 9999. But this will not work because there always be some rogue pool which will not change diff., or those nicehash miners can always learn how to set up and run own pool.

[MainCoins]

seems to be synced by now:

Code:

# date && for i in http://xci.mypool.name:42004/stats http://pool3.democats.org:7713/stats http://gorillapool.org:8117/stats http://xci.acidminer.org:8117/stats  http://xci.ms-pool.net.ua:8117/stats http://xci.cryptonotepool.com:8119/stats; do echo -n "$i: is at " && curl -s $i | jq .network.height; done
Thu Dec 22 14:30:34 CET 2016
http://xci.mypool.name:42004/stats: is at 42087
http://pool3.democats.org:7713/stats: is at 42087
http://gorillapool.org:8117/stats: is at 42087
http://xci.acidminer.org:8117/stats: is at 42087
http://xci.ms-pool.net.ua:8117/stats: is at 42087
http://xci.cryptonotepool.com:8119/stats: is at 42087

But I'm still missing understanding what happened (technically) and how to avoid it in the future. If "nicehash" indeed can do such a mess filtering seems to be a temporary solution.

[niko2004x]

Question to xci.cryptonotepool.com owner.
From block ~41400 to block 41555 (where last split occured) xci.cryptonotepool.com mined ~150 blocks on good chain.
Where are they? They are removed from pool statistic now.

[niko2004x]

But I'm still missing understanding what happened (technically) and how to avoid it in the future. If "nicehash" indeed can do such a mess filtering seems to be a temporary solution.

Some 'bug' leads to chain split.
Since chain splited some pools mine on 'bad' chain.
Therefore hashrate allocated to 'good' chain is reduced and difficulty on 'good' chain eventually falls.
Therefore profits/hash on 'good' chain raise above marker average.
Someone sees raised profits/hash and decides to 'pick it up'.
Goes to nicehash for hashrate.
Mines.
Difficulty raises.
Nicehash miner goes away.

[MainCoins]

Some 'bug' leads to chain split.

This is the most interresting part.

Since chain splited some pools mine on 'bad' chain.
Therefore hashrate allocated to 'good' chain is reduced and difficulty on 'good' chain eventually falls.
Therefore profits/hash on 'good' chain raise above marker average.
Someone sees raised profits/hash and decides to 'pick it up'.
Goes to nicehash for hashrate.
Mines.
Difficulty raises.
Nicehash miner goes away.

Thank you, it's clear as well as that without understanding the "bug" in detail it's not possible to fix it.

[atithasos]

The pool http://xci.cryptonotepool.com is synced and flushed