Quote from: reeyon on March 14, 2018, 04:38:56 AM

Dev,

Is joke i totally believe that.
The blockchain stuck at height 16370 and won't move forward.

Code:

12:38:09.114998 INFO ----- BLOCK ADDED AS ALTERNATIVE ON HEIGHT 16370
12:38:09.114998 INFO id: <9c4ef0b46f6828267982d82262bc7877fd8bff7dc01ce18839accf92c8fd6a73>
12:38:09.114998 INFO PoW:
12:38:09.114998 INFO difficulty: 709548
12:38:09.208799 INFO ###### REORGANIZE on height: 16370 of 16370 with cum_difficulty 11506721434
12:38:09.208799 INFO alternative blockchain size: 2 with cum_difficulty 11507431302
12:38:09.209278 DEBUG Key image already spent in blockchain: f360bab12b22ba6fc6b26f14464b8bfb2d6c25b583f381faa7367906123c5eca
12:38:09.209514 DEBUG Key image already spent in blockchain: 1e70fccf16a262de5bb8a3985c255a4000276f041a7b60bd9776fb8aaaadd614
12:38:09.209699 DEBUG Key image already spent in blockchain: bd5c3507a01dc54008a9f750acb585b58286bcba5ce194675247914762f3196e
12:38:09.209976 DEBUG Key image already spent in blockchain: d98712c532df432764cdd0b868dbb5e5d374198f9dce6a524a24f27bd2944b73
12:38:09.210307 DEBUG Key image already spent in blockchain: 6e03703781bf09f99cbde5d4bdcde882c71da0a7c6686e92f687695c13f51279
12:38:09.307383 INFO Failed to check ring signature for tx <856c1834da4683bb72a6a10038c597e98896cb1229e62ea447cc741e44388752>
12:38:09.307522 INFO Block <9c4ef0b46f6828267982d82262bc7877fd8bff7dc01ce18839accf92c8fd6a73> has at least one transaction with wrong inputs: <856c1834da4683bb72a6a10038c597e98896cb1229e62ea447cc741e44388752>
12:38:09.310748 INFO Failed to check ring signature for tx <856c1834da4683bb72a6a10038c597e98896cb1229e62ea447cc741e44388752>
12:38:09.310893 INFO Failed to switch to alternative blockchain
12:38:09.463443 DEBUG +++++ BLOCK SUCCESSFULLY ADDED
12:38:09.463443 DEBUG id:
12:38:09.463443 DEBUG PoW:
12:38:09.463443 DEBUG HEIGHT 16370, difficulty: 709548
12:38:09.463443 DEBUG block reward: 25.0300, fee = 0.0300, coinbase_blob_size: 160, cumulative size: 8662, 152(54/38)ms
12:38:09.464032 INFO Rollback success.
12:38:09.464159 INFO The block was inserted as invalid while connecting new alternative chain, block_id: <9c4ef0b46f6828267982d82262bc7877fd8bff7dc01ce18839accf92c8fd6a73>
12:38:09.464311 DEBUG [198.24.172.10:37373 OUT] Block verification failed, dropping connection
12:38:09.464477 DEBUG [198.24.172.10:37373 OUT] Interrupt connection
12:38:09.464617 DEBUG [198.24.172.10:37373 OUT] writeHandler finished
12:38:11.592984 DEBUG [118.25.12.142:37373 OUT] msg 1:1002
12:38:13.532296 DEBUG Connection to 46.126.95.96:37373 timed out, interrupt it
12:38:13.532587 DEBUG Connection timed out
12:38:13.532754 DEBUG Selected peer: 8087383566627567330 87.76.11.74:37373 [white=0] last_seen: d0.h7.m57.s14
12:38:13.532868 DEBUG Connecting to 87.76.11.74:37373 (white=0, last_seen: d0.h7.m57.s14)...
12:38:13.841879 DEBUG Connection to 87.76.11.74:37373 failed: TcpConnector::connect, connection failed
12:38:15.842334 DEBUG Selected peer: 13007404780682834648 198.24.172.10:37373 [white=1] last_seen: d0.h0.m0.s7
12:38:15.842579 DEBUG Connecting to 198.24.172.10:37373 (white=1, last_seen: d0.h0.m0.s7)...
12:38:18.194067 DEBUG [109.200.155.98:37373 OUT] msg 1:1002
12:38:18.501029 DEBUG [109.200.155.98:37373 OUT] msg 2:2007
12:38:19.601654 DEBUG [109.200.155.98:37373 OUT] msg 2:2004

We had a network attack since only one pool was giving 99% of the hashing power to the network. This has now been fixed with us having 2 pools now! Our old one is at: http://fart.hashingmonkeys.com and our brand new one for the UK is at http://fartcoins.com/pool