15 then 0.02568.

Hm, at first I had 1-2 connections only, since two days I have plenty of connections but:

"334015 blocks remaining" & "last received block was generated 12 seconds ago"

Uhm ,what? Like how exactly does this coin work?

pool : http://66.172.10.55:19337/static/
It's not working properly  
Please do not use any more until further notice

1 keep your wallet.dat in a safe place
2 delete sexcoin forder from Roaming

3 add this in your sexcoin.conf file
4 addnode=46.39.246.24:9560
5 addnode=68.52.140.186:9560
6 addnode=84.253.217.35:9560
7 addnode=67.191.160.195:9560
8 addnode=223.27.19.38:9560
9 If you have any other nodes delete them

10 run again the sexcoin wallet
11 exit wallet
12 replace the wallet.dat with the one that you put in safe place
13 run again the sexcoin wallet

Since the old client crashes more often then a stock car it might be a good idea to release the new client ASAP.

I have a workaround for those that do not like the "Synchronizing with network..." issue to be displayed.

First, this is not an attack or malicious act by anyone but more of an oversight when the coin was created. Your wallet is safe and your coins aren't going anywhere because of issue.

Having that in mind, here is at least one way of fixing it until the coin itself (meaning all clients on the network and the block chain) can be fixed which is something we will be working on very soon.

In your sexcoin.conf file, instead of using the "addnode" keyword, change that to "connect". Your config file should look something this ....

connect=46.39.246.24:9560
connect=68.52.140.186:9560
connect=84.253.217.35:9560
connect=67.191.160.195:9560
connect=223.27.19.38:9560
connect=207.29.218.6:9560

So whats the difference between "addnode" and "connect"?
Simply, "addnode" tells the client to add this peer as a node but also try to add them dynamically through the network. The "connect" option tells the client to ONLY connect to these peers and these peers ONLY.

So if you make these changes, please note that at least ONE of these in the list must be up and accepting connections, otherwise you will not be able to connect to the network. 2 of the nodes listed above belong to me and I will try and keep them up as much as possible. One is my personal workstation which gets rebooted every now and again and the other is a new server I added the client to last night, so it should be up most of the time.

A few of us are working on a new client that will be announced very shortly, so hang in there everyone. We appreciate everyone's patience. Feel free to PM me if you have any problems with the above config.

Pool : http://66.172.10.55:19337/static/

it's working properly again
You are welcome to mine

I'm not understanding the whole 'connect-thing': If I want to mine solo, do I need addnode or is solo-mining with a "Sexcoin-qt -connect" possible? If my sexcoin.conf contains listen=1, others who have "Sexcoin-qt -connect" can't connect to my blockchain. So how can I share my own share, if I have found a new block with solo-mining and my sexcoind in connect-mode?

So whats the difference between "addnode" and "connect"?
-"addnode" tells the client to add this peer as a node BUT ALSO try to add them dynamically through the network.
-"connect" option tells the client to ONLY connect to these peers and these peers ONLY.

"-listen   Accept connections from outside (default: 1 if no -proxy or -connect)"