[SXC][NSFW] Sexcoin - New Android Client Release!

[CryptoCanary]

Does anyone know how to get in touch with zpool.ca ?

I do. PM en route!

I found crackfoo... is that still the contact?

Correct.

[RatCoin]

Should we start updating our clients with he new Mac? (Mac user here)

When we release, yes. But not yet.

Also, I thought you might like to know. I'm testing the new Mac client right now. It took about 10 hours for it to sync today. However, last night I left it to sync overnight, using its wi-fi connection. When I got up this morning to check it, the wi-fi had cut off when the unit went to sleep, which stopped it dead as far as downloading the blockchain. I set it on a wired connection and it synced as expected.

Thanks Lava for following up on this issue. I am on a MacBook so no hard connections to ethernet.

It took almost like a week right? From my many posts here haha

Regardless I am up to speed.

Thanks and I will wait for the new client.

[lavajumper]

UPDATE on the New Client:

Sexcoin is in the final phases of testing the next client. The Core client is based on Litecoin 0.10.4.0.

This is a repost of this announcement. All information is still pertinent.
Our estimate is the new client will be available for everyone in about 2 weeks.


There will be a "soft fork" to enable some new features, and miners are going to be most affected.
 

The most significant changes:

• Sexcoin will now have a self-reported "Age-Verification" feature, which is carried on the transaction level and written to the block-chain (more on that soon)
• Coin-control is implemented
• Block versions are being pulled straight to version 4, up from version 1 via "Super-majority" soft-fork
• Bloom filtering and other enhancements for thin clients, inherited from litecoin, will be implemented.
• Multi-Sig and other Script enhancements will be inherited.
• There is a proper 'testnet' in operation to test client and transaction code. As of this writing, dnsseeding for testnet will not be available, but the dev team has standing test nodes and a block explorer. This will be documented in the near future
• We will be providing pre-compiled versions for Win32, Win64 and OSX at a minimum.
• The Android version will also be availble shortly after the new Core release to take advantage of the new blockchain features.

As an added bonus, the dev team has a version of P2Pool available which should work "out-of-the-box" for anyone wanting to run a P2Pool. We do not have a pre-compiled widows version of this yet, but hope to be able to provide that in the near future.

We need help letting miners and exchanges know of the upcoming upgrade.
 
IF YOU MINE on a pool that is NOT LISTED, please let your pool-op know!
IF YOU TRADE somewhere that is not listed, please let your exchange admins know!

[lavajumper]

I wanted to take a minute and let everyone know that the delay of this release, announced last year, has been for two reasons:

1. There were some rather scary implications about the timing of the release as far as different versions of miners interacting with different versions of clients. I took the extra time to work through the trouble spots.
2. We wanted to make sure the Dev Team would be available to help with any issues that arose.

We're working on a post which will document some of the issues you may encounter with the upgrade. Look for it in the next couple of days.

I cannot stress enough how important mining support is going to be. Please talk with any miners or pools you may be in contact with.

[sasa9]

Sexcoin

[lavajumper]

DAMN... Kraken, Coinbase, GDAX, Bitstamp, BTC-E all went down at the same time for me. That was some serious shit.

[lavajumper]

Age Verification and Sexcoin

REPOST:

I wanted to take a minute and fill in some information about the age verification feature in the new client.  Age verification is a self-reported verification that is carried IN the transaction and written to the block-chain. This is accomplished through creating a flag field in the existing transaction version field. In effect, the high-byte of the transaction version carries the flags and the low-byte carries the transaction version.

We had a lot of discussion about the validity of 'self-reported' age-verification, and whether it was really worth putting into the client at all. The decision to write the feature in was accepted because self-reporting does provide merchants and end-users a certain amount of protection. If you doubt this, go to porn.com, and initiate a bitcoin purchase. This is processed with a button certifying your age. Pair that with the number of sites you can access with a button-click, and you can see that it does hold weight. In effect, the sender is certifying they are of age. As a merchant, the client has lied to you if they are not, so the client is culpable of fraud.

Also, the way we've implemented the verification actually implies that "better" is on the way. We've been looking at services like Sho-Card and a couple of others that offer very strong verification, and we have left room in the code to be able to 'fold-in' third-party verification schemes in the future. This is what we REALLY want to see.

I think the real power of this layout is that the flag is carried in the transaction, so it can be confirmed any time, by anyone (de-centralized ) in the future that age-verification was provided by looking up the transaction via the block-explorer.

Finally, I want to mention that age-verification offers protection both ways, and in some sense can make the coin useful in tangent with other payment schemes. I do picture a cam-to-cam scenario where both parties send age-verified coins to each other, providing an electronic signature that both are of age. Another scenario would be sending sexcoin with age-verification flags set as a side-transaction, with the bulk of the "traded-value" being doge or litecoin.

[RatCoin]

Well written.

Thanks Lava and Development Team.

[yns1971]

Age Verification and Sexcoin

REPOST:

I wanted to take a minute and fill in some information about the age verification feature in the new client.  Age verification is a self-reported verification that is carried IN the transaction and written to the block-chain. This is accomplished through creating a flag field in the existing transaction version field. In effect, the high-byte of the transaction version carries the flags and the low-byte carries the transaction version.

We had a lot of discussion about the validity of 'self-reported' age-verification, and whether it was really worth putting into the client at all. The decision to write the feature in was accepted because self-reporting does provide merchants and end-users a certain amount of protection. If you doubt this, go to porn.com, and initiate a bitcoin purchase. This is processed with a button certifying your age. Pair that with the number of sites you can access with a button-click, and you can see that it does hold weight. In effect, the sender is certifying they are of age. As a merchant, the client has lied to you if they are not, so the client is culpable of fraud.

Also, the way we've implemented the verification actually implies that "better" is on the way. We've been looking at services like Sho-Card and a couple of others that offer very strong verification, and we have left room in the code to be able to 'fold-in' third-party verification schemes in the future. This is what we REALLY want to see.

I think the real power of this layout is that the flag is carried in the transaction, so it can be confirmed any time, by anyone (de-centralized ) in the future that age-verification was provided by looking up the transaction via the block-explorer.

Finally, I want to mention that age-verification offers protection both ways, and in some sense can make the coin useful in tangent with other payment schemes. I do picture a cam-to-cam scenario where both parties send age-verified coins to each other, providing an electronic signature that both are of age. Another scenario would be sending sexcoin with age-verification flags set as a side-transaction, with the bulk of the "traded-value" being doge or litecoin.

It's great! sexcoin will go to moon! Thanks dev

[Geenstijl]

still serious developments in this old coin. Good to see.

[lavajumper]

Very Important Information!!

The new client is getting ready for release. Here are some of the nitty-gritty caveats and details.

There is the possibility of some pain points during this upgrade:

• Sexcoin has been vulnerable to transaction malleablity. This release addresses that issue. Once miners have updated, old clients will have a possibility (by our calculation about 5%) of creating transactions that will be completely rejected by the network. The way you know this has happened will be evident by this behavior:
  
  An old client sends a transaction which gets broadcast to the network. It is recorded in the wallet as usual, and you see a zero confirm transaction. Because it has been broadcast to the network, the recieving client  also shows an incoming, zero confirmed transaction. So now both the sender and receiver have transactions in their wallets, but with zero confirms. However, miners will reject the transaction and not include it in the blocks they assemble for processing. As time goes on, both wallets retain the record, waiting for it to confirm on the blockchain. This transaction will NEVER make it onto the blockchain. Old clients have marked these coins as 'unspendable' so the coins are tied up in the users wallet. The transaction at the receivers end will show as unconfirmed. This puts both sender and receiver in a unwanted position.
  
  On old wallets, restarting your wallet with the '--rescan' might clear the problem...but not always. The only way I've found to work 100% is to start a new wallet, import the private keys from the old wallet, then let the wallet rebuild with the information from the blockchain.
  
  On new wallets, you can restart the wallet with '--zapwallettxes=1' to clear unconfirmed transactions and free up the coins. This is much easier than having to import private keys, but still takes time.
  
  I have begun work on adapting pywallet to work with sexcoin so we have a tool to deal with this, but will not have it done for quite a while.
  
  IF THIS HAPPENS YOUR COINS HAVE NOT BEEN LOST! They are just inaccessible until your wallet is cleaned up. Its probably a good time to upgrade your wallet
  
  
• Sexcoin has age verification flags in the current transaction version field. The old client rejects any 'transaction version != 1'. ANY age verified transaction, picked up by an OLD miner, will reject the transaction as invalid. See the above scenario. YMMV in this scenario. IF a miner wins a block that is mining with the new client the transaction will be accepted to the blockchain.
  
  The remedy to this is to NOT USE AGE VERIFICATION (Set age verification to 'NONE' ) until a significant amount of miners have switched. This is why we are releasing to miners first.
  
  
• The next Android release will refuse to connect to old nodes. This is the primary reason we are delaying release of the Android client. Once the network has significantly updated, the new Android client will be available.
  

I think when you fully understand the different permutations involved, you can see why the release got delayed for so long. Is it better to get miners first, then users? Is it better to upgrade users first, and pray they don't set age verification? Should we simply release and have everyone explode? Is there some way to code in a solution? This last question is what has taken the longest amount of time. We've attempted code solutions, but at the end of the day, the only effective changes that mitigate lie in changing the code in the old client, which obviously is stupid, if we're releasing a new client.

[lavajumper]

It would be valuable if you could record STD testing in the blockchain. I know adult porn stars and prostitutes in places where it's legal like Amsterdam have to get regular STD tests, recording them in the blockchain would be immutable proof that somebody is free from sexually transmitted disease, seems pretty valuable to me.

This is a REALLY intriguing idea.... hmmmm....

[Timelord2067]

It would be valuable if you could record STD testing in the blockchain. I know adult porn stars and prostitutes in places where it's legal like Amsterdam have to get regular STD tests, recording them in the blockchain would be immutable proof that somebody is free from sexually transmitted disease, seems pretty valuable to me.

This is a REALLY intriguing idea.... hmmmm....

Just in case you missed my reply...

You can do that already - create a text file; make an md5sum of said file, add text file name (as in a URL) and md5sum to the block chain via this tool:

Embed Data in Blockchain https://live.blockcypher.com/btc/embed-data/

[sasa9]

#Sexcoin

[sasa9]

#Sexcoin

[sasa9]

#Sexcoin


Welcome https://vk.com/sexcoin_ru

[Equalizer1970]

UPDATE on the New Client:

Sexcoin is in the final phases of testing the next client. The Core client is based on Litecoin 0.10.4.0.

This is a repost of this announcement. All information is still pertinent.
Our estimate is the new client will be available for everyone in about 2 weeks.


There will be a "soft fork" to enable some new features, and miners are going to be most affected.
 

The most significant changes:

• Sexcoin will now have a self-reported "Age-Verification" feature, which is carried on the transaction level and written to the block-chain (more on that soon)
• Coin-control is implemented
• Block versions are being pulled straight to version 4, up from version 1 via "Super-majority" soft-fork
• Bloom filtering and other enhancements for thin clients, inherited from litecoin, will be implemented.
• Multi-Sig and other Script enhancements will be inherited.
• There is a proper 'testnet' in operation to test client and transaction code. As of this writing, dnsseeding for testnet will not be available, but the dev team has standing test nodes and a block explorer. This will be documented in the near future
• We will be providing pre-compiled versions for Win32, Win64 and OSX at a minimum.
• The Android version will also be availble shortly after the new Core release to take advantage of the new blockchain features.

As an added bonus, the dev team has a version of P2Pool available which should work "out-of-the-box" for anyone wanting to run a P2Pool. We do not have a pre-compiled widows version of this yet, but hope to be able to provide that in the near future.

We need help letting miners and exchanges know of the upcoming upgrade.
 
IF YOU MINE on a pool that is NOT LISTED, please let your pool-op know!
IF YOU TRADE somewhere that is not listed, please let your exchange admins know!

Does this mean that sexcoin will have segwit in it? All the coins that did upgrade to segwit had a massive pump.

[leps]

What is the total coin supply of sexcoin?

[CryptoCanary]

What is the total coin supply of sexcoin?

250 million.

[lyno]

Straight from the future - Sexcoin Intergalactic 


https://i.imgur.com/tItuquL.jpg


[NSFW] Sexcoin Intergalactic is known for excellent service 
http://imgur.com/fPxYeEO