[NSFW] Official Sexcoin Thread - New MANDATORY upgrade: KGW Timewarp attack FIX

[Gunna01]

I got this from debug.log:

"block height unreasonable (480523) from 24.128.247.77:9560, disconnecting"

out of sync...

I'm also getting this error but mine says:

Sanity checking: 74.122.234.52 9560
block height unreasonable (481434) from 74.122.234.52:9560, disconnecting.

Download the 'block height fix' client fix: https://bitcointalk.org/index.php?topic=252896.msg4564457#msg4564457

I'm running the fix already

Cheers

[Gunna01]

My client keeps losing connection to the network if I run it as as server for solo mining with - server on the shortcut, BTC and LTC clients do not do this.

I just installed last night, let it sync and now it says 0 connections to sexcoin network. It may change to 1 active connection for a few minutes but then it drops.

....

Edit: I also get the errors without trying to run in server mode as well. Getting pages and pages of the error in debug log.

Try deleting your 'peers.dat' file and restarting the client.

Edit: Sorry saw there was an unlimited .exe to use. Cheers

Edit 2: Used the unlimited .exe and same results as below

Just tried and same issue:

Sorry for the long cut and paste:

Verifying last 2500 blocks at level 1
 block index            9717ms
Loading wallet...
nFileVersion = 60401
 wallet                  176ms
Loading addresses...
Loaded 0 addresses from peers.dat  0ms
mapBlockIndex.size() = 480672
nBestHeight = 480671
setKeyPool.size() = 102
mapWallet.size() = 0
mapAddressBook.size() = 1
ThreadRPCServer started
send version message: version 60011, blocks=480671, us=0.0.0.0:0, them=0.0.0.0:0, peer=127.0.0.1:0
Done loading
ThreadDNSAddressSeed started
Loading addresses from DNS seeds (could take a while)
0 addresses found from DNS seeds
ThreadDNSAddressSeed exited
ThreadMessageHandler started
ThreadSocketHandler started
ThreadOpenAddedConnections started
ThreadIRCSeed exited
ThreadOpenConnections started
socket select error 10022
trying connection 46.39.246.24:9560 lastseen=358359.4hrs
refreshWallet
Flushed 0 addresses to peers.dat  8ms
socket select error 10022
ipcThread started
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
connection timeout
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
trying connection 68.52.140.186:9560 lastseen=358359.4hrs
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
connection timeout
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
trying connection 84.253.217.35:9560 lastseen=358359.4hrs
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
connection timeout
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
trying connection 67.191.160.195:9560 lastseen=358359.4hrs
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
connection timeout
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
trying connection 223.27.19.38:9560 lastseen=358359.4hrs
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
connection timeout
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
trying connection 74.122.234.52:9560 lastseen=358359.4hrs
socket select error 10022
socket select error 10022
socket select error 10022
connected 74.122.234.52:9560
send version message: version 60011, blocks=480671, us=0.0.0.0:0, them=74.122.234.52:9560, peer=74.122.234.52:9560
client version passed: /Sexcoin:0.6.4.1/
Added time data, samples 2, offset -1 (+0 minutes)
Sanity checking: 74.122.234.52 9560
block height unreasonable (481852) from 74.122.234.52:9560, disconnecting.
disconnecting node 74.122.234.52:9560
socket select error 10022
socket select error 10022
trying connection 23.94.28.23:9560 lastseen=358359.4hrs
socket select error 10022
socket select error 10022
socket select error 10022
socket select error 10022
connected 23.94.28.23:9560
send version message: version 60011, blocks=480671, us=0.0.0.0:0, them=23.94.28.23:9560, peer=23.94.28.23:9560

[niceman]

You can mine SexCoins (SXC) at www.CoinMine.PW.

• Self-created, optimized software
• Dedicated Xeon server, SSD, 1Gbit Ethernet, EU based
• Autoswitch port to mine most profitable coins
• PPL(10 MIN)S payouts

More info: http://www.coinmine.pw/about.php

[lavajumper]

Edit: Sorry saw there was an unlimited .exe to use. Cheers

Edit 2: Used the unlimited .exe and same results as below

Just tried and same issue:

Sorry for the long cut and paste:

Verifying last 2500 blocks at level 1
 block index            9717ms
Loading wallet...
nFileVersion = 60401
 wallet                  176ms
Loading addresses...
Loaded 0 addresses from peers.dat  0ms
mapBlockIndex.size() = 480672
nBestHeight = 480671
setKeyPool.size() = 102
mapWallet.size() = 0
mapAddressBook.size() = 1
ThreadRPCServer started
send version message: version 60011, blocks=480671, us=0.0.0.0:0, them=0.0.0.0:0, peer=127.0.0.1:0
Done loading
ThreadDNSAddressSeed started
Loading addresses from DNS seeds (could take a while)
0 addresses found from DNS seeds
ThreadDNSAddressSeed exited
ThreadMessageHandler started
ThreadSocketHandler started
ThreadOpenAddedConnections started
ThreadIRCSeed exited
ThreadOpenConnections started
socket select error 10022
trying connection 46.39.246.24:9560 lastseen=358359.4hrs
refreshWallet
Flushed 0 addresses to peers.dat  8ms
socket select error 10022
ipcThread started
socket select error 10022
connected 23.94.28.23:9560
send version message: version 60011, blocks=480671, us=0.0.0.0:0, them=23.94.28.23:9560, peer=23.94.28.23:9560

I'm double checking the build... keep watching here.

[Sexcoin69]

New pool http://sxc.broken-arrow.pl/

[lavajumper]

Edit: Sorry saw there was an unlimited .exe to use. Cheers

Edit 2: Used the unlimited .exe and same results as below

Just tried and same issue:

Sorry for the long cut and paste:

Verifying last 2500 blocks at level 1
 block index            9717ms
Loading wallet...
nFileVersion = 60401
 wallet                  176ms
Loading addresses...
Loaded 0 addresses from peers.dat  0ms
mapBlockIndex.size() = 480672
nBestHeight = 480671
setKeyPool.size() = 102
mapWallet.size() = 0
mapAddressBook.size() = 1
ThreadRPCServer started
send version message: version 60011, blocks=480671, us=0.0.0.0:0, them=0.0.0.0:0, peer=127.0.0.1:0
[......]
socket select error 10022
connected 23.94.28.23:9560
send version message: version 60011, blocks=480671, us=0.0.0.0:0, them=23.94.28.23:9560, peer=23.94.28.23:9560

I'm double checking the build... keep watching here.

Ok, rather than trying to figure out what might have happened, I just rebuilt the GUI versions ( Both limited and unlimited) and checked the links.
Download the client again ( sorry ),stop your client, replace sexcoin.qt.exe with the new one,  delete your 'peers.dat' file and start the client.

[affan]

I got this from debug.log:

"block height unreasonable (480523) from 24.128.247.77:9560, disconnecting"

out of sync...

I'm also getting this error but mine says:

Sanity checking: 74.122.234.52 9560
block height unreasonable (481434) from 74.122.234.52:9560, disconnecting.

Download the 'block height fix' client fix: https://bitcointalk.org/index.php?topic=252896.msg4564457#msg4564457

Download the 'block height fix' client fix  : http://www.sexcoin.info/Sexcoin-0.6.4.1-win32-RC1.zip   ?

[lavajumper]

Scroll to the bottom of the 'clients' section.

or:

http://sexcoin.info/sexcoin-qt-0.6.4.1-RC1-BlockLimit498000.zip

in the zip file is a replacement for 'sexcoin-qt.exe', overwrite your existing 'sexcoin-qt.exe' with the one in the zip file.

[affan]

Scroll to the bottom of the 'clients' section.

or:

http://sexcoin.info/sexcoin-qt-0.6.4.1-RC1-BlockLimit498000.zip

in the zip file is a replacement for 'sexcoin-qt.exe', overwrite your existing 'sexcoin-qt.exe' with the one in the zip file.

Ok , works fine now... thank you 

[Gunna01]

Edit: Sorry saw there was an unlimited .exe to use. Cheers

Edit 2: Used the unlimited .exe and same results as below

Just tried and same issue:

Sorry for the long cut and paste:

Verifying last 2500 blocks at level 1
 block index            9717ms
Loading wallet...
nFileVersion = 60401
 wallet                  176ms
Loading addresses...
Loaded 0 addresses from peers.dat  0ms
mapBlockIndex.size() = 480672
nBestHeight = 480671
setKeyPool.size() = 102
mapWallet.size() = 0
mapAddressBook.size() = 1
ThreadRPCServer started
send version message: version 60011, blocks=480671, us=0.0.0.0:0, them=0.0.0.0:0, peer=127.0.0.1:0
[......]
socket select error 10022
connected 23.94.28.23:9560
send version message: version 60011, blocks=480671, us=0.0.0.0:0, them=23.94.28.23:9560, peer=23.94.28.23:9560

I'm double checking the build... keep watching here.

Ok, rather than trying to figure out what might have happened, I just rebuilt the GUI versions ( Both limited and unlimited) and checked the links.
Download the client again ( sorry ),stop your client, replace sexcoin.qt.exe with the new one,  delete your 'peers.dat' file and start the client.

Appreciate the help - client is sync'ing again. Getting 2 and 3 connections to the network

[Nerull]

first tip sent in http://www.reddit.com/r/girlsgonesexcoin/

sxc on the way up!

[coinpool_de]

first tip sent in http://www.reddit.com/r/girlsgonesexcoin/

sxc on the way up!

Yes hope it will go Up again !! To 0,00050000

[coinpool_de]

Why join Coinpool.de?
Backups every 60 minutes of the databases and wallets to protect your earnings.
24/7 support Just write us a mail at info (at) coinpool.de
All servers with a DDoS protection.
Low fees
Get bonuses in our special offers
Stratum Vardiff
Fast servers Xeon 4 x 3,2Ghs 32 GB Ram, SSD
Manual and auto payout
10+ Mining pools out of one Hand (SHA and scrypt)


http://sxc.coinpool.de

@ existing users: if you have problems to login. Please reset your password or write me a mail.

[rapidfire187]

This fucking coin is broken once again... Isn't there going to be a permanent fix for this synch issue?

[LittleDigger]

This fucking coin is broken once again... Isn't there going to be a permanent fix for this synch issue?

Yeap I couldn't sync, so I went to sexcoin.info, went to the cleints section and downloaded the blockheight check disabled client, which "fixs" the issue.. No more downloads...

The permanent fix would be to swap from the litecoin network to a unique network,and lava figured it out ,coded it in, and it tested fine.. But it requires a hardfork..

We discussed this in the development team, I was for simply offering the one client, Lava wanted the blockheight check enabled client.. My view was he was putting a time limit on the hardfork, and every time that limit was missed people would get pissed off when they couldn't sync, his view was if they couldn't sync they'd have to download the new client for the hardfork, which would make life easier for us..

So there you go... Now you know the why of it....

[0rganic]

This fucking coin is broken once again... Isn't there going to be a permanent fix for this synch issue?

Yeap I couldn't sync, so I went to sexcoin.info, went to the cleints section and downloaded the blockheight check disabled client, which "fixs" the issue.. No more downloads...

The permanent fix would be to swap from the litecoin network to a unique network,and lava figured it out ,coded it in, and it tested fine.. But it requires a hardfork..

We discussed this in the development team, I was for simply offering the one client, Lava wanted the blockheight check enabled client.. My view was he was putting a time limit on the hardfork, and every time that limit was missed people would get pissed off when they couldn't sync, his view was if they couldn't sync they'd have to download the new client for the hardfork, which would make life easier for us..

So there you go... Now you know the why of it....

Unfortunately, maybe I am just dumb, I am not a geek or read code, just a newbie, just purchased sexcoins last year, it took me over

three days to get the wallet to open and sync.


To be honest it has only worked for thee days I did one test transfer from Cryptsy in November last year with only 10 coins, it worked fine for two days,

but I have left a substantial amount of coins with cryptsy,I was too scared to put them in the wallet. In the interim of that time I  have been

to embarrassed to bother you guys again, and I believe Lava is working on a new client, notwithstanding the fact I have made over thirty attempts to

synch the wallet again, and have trial Winzip and rar file downloads all over my Fxxking laptop  . Even though I do not mine or know what a block

chain is even if it kicked me in the  nuts , I have managed to utilise other wallets of other coins, maybe they are just user friendly, and when

I say user friendly, I mean your average person  who does not know software or  has a degree in computer engineering.



I am not knocking you guys, because I can see the amount of effort you have put into this project, but maybe you should step outside of the IT community

that you inhabit, and maybe realise that the majority of people do not have a clue of what you are talking about. Not only do they not have a clue, they are

not that interested to delve under the hood so to speak.



Crypto currency is an exciting adventure, money and finance is evolving, and I want to be part of that, but Jesus guys.... I don't want to

become a rocket scientist to use it.



It's Monday morning and I am pissed off after another attempt of trying to get this wallet to work, winzip trial has now expired.

Please oh pretty please do not refer me to the thousand of links  that you have, I can see them,
 

Very simple, if you cannot provide an easy tutorial guide for dummies like me to utilise your wallet, I will sell my substantial amount of coins and

not disturb you anymore.



    

[styleruk]

Organic

Crack it on the opening line there!

Crypto currency is tricky to the un-initiated and whilst I'm not a rocket scientist I enjoy tinkering with the PC and getting it to do stuff faster, this is why I do it and not to make a ton of money (that is a side effect).  I think a lot of people do this for a hobby.
I suggest you wait for the dust to settle when cryto currency can be bought at your local post office and buy some then.

:-)
(no offense, I understand your frustrations)

[0rganic]

Organic

Crack it on the opening line there!

Crypto currency is tricky to the un-initiated and whilst I'm not a rocket scientist I enjoy tinkering with the PC and getting it to do stuff faster, this is why I do it and not to make a ton of money (that is a side effect).  I think a lot of people do this for a hobby.
I suggest you wait for the dust to settle when cryto currency can be bought at your local post office and buy some then.

:-)
(no offense, I understand your frustrations)

No offence taken  what's a post office?

[styleruk]

Organic

LOL, sorry.  In the UK we have little shops that sell stamps and stuff!

[0rganic]

Organic

LOL, sorry.  In the UK we have little shops that sell stamps and stuff!

 LOL Sorry I am based in the UK also, no offence just my sarcasm