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

[lavajumper]

I posted this on the Sexcoinforum, and decided it was a good idea to post it here also:

Lavajumper is coding.

I've decided to stay off the boards because I realized that my priority has to be the client. I don't have a lot of time, and my day job has become very demanding. So, I'm faced with the decision to either: a) quit my job to handle all the communications or b) prioritize.
I have chosen to prioritize.

So realize this: Sexcoin is a long-term project, if you're looking to get rich overnight, this is probably not the coin you want. In our early strategic planning, we developed a 2 YEAR strategy. We are not just on track for that strategy, we are ahead.

It makes me very happy to see all the ideas and discussions here. Both the negative and the positive.

I'm going to lay out parts of the 'roadmap':

First, Read this:
https://bitcointalk.org/index.php?topic=252896.msg3793944#msg3793944


The roadmap looks something like this, after the release of the new client:

 

• a webmaser kit ( Drop-in addon for a shopping cart )
• developer sdk  ( so people can integrate sxc however they want )
• paper wallets
• qrcode network
• plug-in architecture on the client ( People can write addons for the official client )
• escrow service
• sxc->fiat exchange ( kind of like coinbase )
• thin-client, ( 0 block chain, with a 'blockchain service' )
• Cam-chat client ( the official client will have two flavors, one SFW, one NSFW )

If you think about this list, it requires a good deal of both work and planning. Our planning is such that our goal for the client we've been talking about will be the last 'hard-fork' required for a long time. So any changes made now, in addition to fixing stuff, also has to keep in consideration that any of the things listed above won't require another fork.

There are some things above, that the dev team is working on that we simply cannot discuss, because of the sensitivity of some of the negotiations. Other things on the list above we don't feel comfortable 'farming out' to just anyone.

Still there are other things on that list that ANYONE can do, without a lick of help from the dev team.

Also, there have been many excellent ideas presented here in the forums recently. I consider all of them, with an eye on the client code, and how it will fit into this plan. i.e. the discussions of AVS, Anonymity strategies, recurring payments. But all of these are major decisions about the coin and the client, so they need to be both discussed and considered over a period of time, not shot-gunned into the client.

Over the course of sexcoin, I have developed a great deal of respect for LittleDigger. I don't think anyone here realizes how much he has contributed to the growth of this coin, and also how many times he has probably saved it from extinction. I code, but LittleDigger has the pulse of the coin, and where it needs to go. NONE of these things happen overnight. Remember that there are challenges that sexcoin faces, which other coins simply don't have to deal with. This makes for a longer strategy, a longer consideration period, and a longer negotiation for almost every BUSINESS aspect of the coin.

[lavajumper]

We're approaching Yet Another Blockheight Fix point.  ( 480000 )


I've uploaded two fixes for the block height issue this time. One limits the block height to 498000, the other has the block height limiter disabled.
(The reason I choose these block heights, is that it is the current height of the litecoin blockchain at build time )

For people not familiar with the problem: http://www.sexcoinforum.org/index.php?topic=316.msg1045#msg1045
The last fix I put out threw the limit forward to 480000, we're approaching that also.
My plan for this is that until I get the new client released, I'll put up new builds, for windows, that will keep throwing the limit further. If you don't want to keep living under the ticking clock, use the 'limit disabled' client.

The block height limiter is an extremely effective means to preventing the misreported 'out of sync' message, so I would encourage its use, but I do understand its a PITA to keep downloading/copying the file at each limit.

You do not need to do anything except replace the sexcoin-qt.exe file. Some people may need to delete 'peers.dat' and restart the client.

Head over to http://sexcoin.info, click on the 'Clients' area and scroll to the bottom. Choose your poison.

[mrbickle]

We're approaching Yet Another Blockheight Fix point.  ( 480000 )

Does this fix only apply to qt builds like the last one?

By the way, great post, planning and decisions. Maybe you could add some of the roadmap in the official website or the first post of the thread. I think a good communication from the devs is really important for any coin. Makes people confident with the project :-)

[lavajumper]

We're approaching Yet Another Blockheight Fix point.  ( 480000 )

Does this fix only apply to qt builds like the last one?

Yes, there were also a couple of precompiled ubuntu clients that had the limiter in them. All the linux builds on sexcoin.info now have that code disabled. If you built your own from the github source, it was disabled. The last block-height fix for windows was the build that has the 480000 limiter active.

By the way, great post, planning and decisions. Maybe you could add some of the roadmap in the official website or the first post of the thread. I think a good communication from the devs is really important for any coin. Makes people confident with the project :-)

Agreed, and thanks for the positive attitude, its very appreciated

We plan to sticky the roadmap on sexcoinforums. I'll look at sexcoin.info, and see where a good place to put it would be.

[Baleinium]

We're approaching Yet Another Blockheight Fix point.  ( 480000 )

Does this fix only apply to qt builds like the last one?

Yes, there were also a couple of precompiled ubuntu clients that had the limiter in them. All the linux builds on sexcoin.info now have that code disabled. If you built your own from the github source, it was disabled. The last block-height fix for windows was the build that has the 480000 limiter active.

By the way, great post, planning and decisions. Maybe you could add some of the roadmap in the official website or the first post of the thread. I think a good communication from the devs is really important for any coin. Makes people confident with the project :-)

Agreed, and thanks for the positive attitude, its very appreciated

We plan to sticky the roadmap on sexcoinforums. I'll look at sexcoin.info, and see where a good place to put it would be.

Really cool, thanks Lava. Personally I see Sexcoins as somewhat of a gamble (as are all cryptos!) but the competent team behind it makes it worth it for me to invest in it. You guys have had many opportunities to dump your coins and cash out big, but the fact that you still continue to work hard even after the price has gone down makes me believe that this project will go far.

[nejat76]

How about getting some advertising space at pxlcoin?

http://www.pxlcoin.com/
https://bitcointalk.org/index.php?topic=418088.0

ps: I can donate all my mined 8 coins to the fundraisal if any one setup.

[Sexcoin69]

Commercial Site: http://143vpn.com/ NEW
Commercial Site: http://www.trade4bitcoin.com/  NEW

Added to the OP

[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.

Debug log shows:

trying connection 23.94.28.23:9560 lastseen=358354.2hrs
socket select error 10022
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
connection timeout
trying connection 176.241.31.176:9560 lastseen=10.2hrs
connection timeout
trying connection 39.68.7.131:9560 lastseen=8.6hrs
connection timeout
trying connection 124.202.191.133:9560 lastseen=80.7hrs
connection timeout
trying connection 111.85.202.137:9560 lastseen=588.7hrs
Flushed 7529 addresses to peers.dat  25ms
connection timeout
trying connection 176.182.235.187:9560 lastseen=8.6hrs

Windows 7, no firewall on and not blocking outgoing ports on my modem.

Also CGminer crashes if attempting to mine the P2Pool listed in the OP, lavajumpers site doesn't crash cgminer at all

Please see this thread, worldcoin had the same issue and litecoin had it early on too with the socket error i am getting: http://worldcoinforum.org/topic/549-fresh-wallet-installed-wont-sync/

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.

[affan]

I got this from debug.log:

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

out of sync...

[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.

[mrbickle]

I got this from debug.log:

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

out of sync...

Read this post:
https://bitcointalk.org/index.php?topic=2528sg4564457#msg4564457

By the way, now almost instant payments (just 5 confirmations) in:

http://sexcoin.ecoining.com

[lavajumper]

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

[lavajumper]

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.

[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   ?