[ANN] Sexcoin - coin for adult industry

[lavajumper]

@kelsy
@joewinkler

just sent some coins for a compatibility test. Can you guys confirm receipt?

ok so thats where that 500 came from.....so yes recieved.

jammin' ! Look for a couple of more

do u need updates on the amounts that came through?

yes please.

[1715342456]

1715342456

[1715342456]

1715342456

[1715342456]

1715342456

[1715342456]

1715342456

[1715342456]

1715342456

[kelsey]

15 then 0.02568.

[lavajumper]

15 then 0.02568.

perfect. Thanks!

[3btc]

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?

[Sexcoin69]

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?

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

add this in your sexcoin.conf file
addnode=46.39.246.24:9560
addnode=68.52.140.186:9560
addnode=84.253.217.35:9560
addnode=67.191.160.195:9560
addnode=223.27.19.38:9560
If you have any other nodes delete them

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

Let me know...

[Sexcoin69]

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

[kelsey]

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

Damn so thats the reason I've again gone so long at not getting a payout I was about to ask if there was any new config settings (thinking it again was at my end).

[Sexcoin69]

A new pool will be ready soon ... only solo mine possible for now
I will send you some coins for the time that you lost here 

[3btc]

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

1 Yep, did it.
2 (Deleting the blockchains so far? Or what?)
3- did but only 5 and 7 worked for some minutes, then it jumped back to previous behaviour.

So, what's happening here?

Update: Okay, after deleting the blockchain folder, it seems to work properly (updating blockchains right now)! Thanks  
Update#2: Nope, after updating that it jumped again to this weird behaviour  
Update#3: Also it jumps now between 334k and 144k blocks left *sigh*

[TheSwede75]

Link for the new client??

Not yet ... it's still in beta
We will release the new version as soon as we are sure that everything works fine

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

[Sexcoin69]

We know the problem ...we are working on it ...
We will soon release the new version

[joewinkler]

@kelsy
@joewinkler

just sent some coins for a compatibility test. Can you guys confirm receipt?

ok so thats where that 500 came from.....so yes recieved.

Yes I can confirm.  Sorry, I'm answering lately. Should I send them back for compatibility test?

[joewinkler]

Link for the new client??

Not yet ... it's still in beta
We will release the new version as soon as we are sure that everything works fine

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

Since I have no sexcoin.conf my wallet is doing fine. Have you tried to delete or rename it? Does it have the same encoding as the original one? (ANSI / UTF-8 / ISO-8859-1 / windows)?

[lavajumper]

@kelsy
@joewinkler

just sent some coins for a compatibility test. Can you guys confirm receipt?

ok so thats where that 500 came from.....so yes recieved.

Yes I can confirm.  Sorry, I'm answering lately. Should I send them back for compatibility test?

Thanks for the confirmation. No need to send back, we have that side covered.
Enjoy the coinage! Consider it a thank you for hanging in there

[joewinkler]

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.

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?

[Sexcoin69]

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

it's working properly again
You are welcome to mine

[kelsey]

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

it's working properly again
You are welcome to mine

my little 20kh/s would never get a share in there atm

[lyno]

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

it's working properly again
You are welcome to mine

my little 20kh/s would never get a share in there atm

I mine with 25kh/s and get about 3.4 SXC per payout

By the way, you should add +0.00002382 to your username (SXC address) to adjust the share difficulty for a lower hash rate. Should not make any difference regarding the payout but gives you a constant share rate.

[lavajumper]

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?

You can solo-mine using connect or addnode.

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)"

listen=1 option (the default) tells Sexcoin-qt to ACCEPT other client network connections in general. It allows people to connect to your client without getting the address from another node on the network, using -connect will negate listen=1.

When mining using connect, your blocks will be confirmed first by the clients you are directly connected to, which will in turn relay the block information to all the nodes THEY are connected to (and so-on and so-on).

All that being said, I have successfully mined, sent and received coins safely with the block chain being reported by my client as out-of-sync.

Also, note above that the P2Pool is working again

Hope that helps!

[flound1129]

Anyone looking to buy some of these?  Cheap!