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

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

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.


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.

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.

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.

I'm getting the main website updated. Just re-vamped the 'clients' section and will move onto the 'mining' section next.

Pool-ops are going to get their pools posted on the main site.

http://sexcoin.info , updated.

If you get the new site, there will be a 'client' nav link at the top. If that link isn't there, you may need to clear your cookies/cache or some mess. There are still updates that need to be done. We're working on it.

LOL... self-explanatory!   

http://www.wired.co.uk/news/archive/2014-01/13/dogecoin-and-the-era-of-personal-currency?utm_source=twitterfeed&utm_medium=facebook

I've reopened registration on the Lavapit, no token necessary.

http://lavapit.lavajumper.com

Check your client's block height and the current blocks on http://blockexplorer.lavajumper.com
If your block height is current, your are experiencing the infamous 'desync' problem, where the client misreports its sync status.

The fix for this will be in the upcoming release.

If cgminer finds a block, the wallet and cgminer have found a 'working solution', however, this doesn't 100% insure that the block will be accepted by the block chain. If another miner has found a 'working solution' at the same time, whichever miner can propagate that information to the network fastest gets the block. The winner will get the reward, and the other miner gets an 'orphan'. This is usually registered in your wallet as a mined block with a '?' beside it for longer than 2 blocks.

This is one of the strongest arguments for mining in a pool unless you have both a competitive hashrate and a good solid connection to the network.

To answer your other question, it is possible for someone to 'interfere' with your wallet under a narrow set of circumstances if your wallet is not encrypted or encrypted with a weak password AND someone has obtained your private key. If this happens your wallet is compromised and whoever has the private key can spend your coins at will.

Always keep in mind that mining calculations are NOTHING but an estimate. It is possible to have a run of bad luck, especially when the network hash rate jumps, and fall in way below the estimated reward. This is exactly why I don't solo mine anymore. I figure solo mining would require somewhere on the order of 1% of the total network hashrate to negate the 'bad luck' risk. Some people have this kind of hashpower, I don't. Add into that the flash mining and it really is a strong case for pool mining. I mined litecoin for months in pools and solo and in my entire mining career I have found a grand total of one block for one pool, never one solo. My calculations predict that I would find one block every 9.5 days ( back when difficulty was under 300). So, it seems to me (and this is an uncalculated, unproven opinion) that there is a 'critical hashrate level' that one must achieve in order to solo mine.

That being said, take a look through your debug.log file to investigate what is happening to these blocks. My guess is that they are being orphaned, but its worth looking into.

[EDIT] All someone needs is your private key, which can be obtained if you don't have your wallet encrypted, or encrypted with a weak password. Encrypting the wallet protects your private key.

Something is up with your installation.
It sounds like you _may_ have corruption in your blockchain:

• copy 'wallet.dat' and sexcoin.conf to a safe place
• delete the old installation ( not your wallet backup!!! )
• install new
• start the new client and see if it syncs, if it does.....
• close the client
• copy your old wallet.dat ( the one with your coins) to the new installation, overwriting the wallet.dat that the new install created
• restart client

Other things:
-what block are you stuck at?
-is your wallet encrypted?
-have you run an anti-virus to make sure its not something like that
-have you checked to see if maybe your firewall decided it didn't like crypto-traffic?


If you want to copy your 'debug.log' file to a drop-box or something, I'll be happy to take a look.

Try over at http://sexcoinforum.org. There are a lot of good ideas incubating there.

Another shameless bump....because we are still getting questions.

No need to be sorry, you're thinking in the correct veins. And I think it would be great to have multiple payment processors available. I was worried we had missed something huge

What does that do that coin payments.net doesn't?

Excellent! .... um.... I didn't do shit.

I'm assuming you're on Linux:
Do a log grep -A4 -B4 -i for "blockheight unreasonable". If you get hits for blockheights less than 480000 then you've got a blockheight sanity check problem. Check your source in main.cpp around line 2540, you may need to adjust and rebuild.

If that isn't the problem, double check and make sure you are using the irc connection feature.

If you still have the issues try this:

-delete peers.dat
-use, instead of addnode:
    connect=74.122.234.52:9560
    connect=81.166.156.164:9560
    connect=67.191.160.195:9560

If you are still having problems, I'll be happy to look at your debug.log file. Zip it and send me a link that I can pull it down.

Don't misunderstand me. I wholeheartedly agree with you on this point. And we do have quite a few 'seed-planters'.

Something that anyone that is holding sexcoin can do is send a quick note to the support of any website they like, "When are you going to accept Sexcoin for payment? I want to subscribe but I can't have recurring charges on my CC." If we want grass-roots, all the blades need to sing.