Topic: [SXC][NSFW] Sexcoin - New Android Client Release! - page 92. (Read 137873 times)

#SEXCOIN

#SEXCOIN

#SEXCOIN



HELP ME !!!
For Foto
SXC - SE7Yyb3MZvAr1aRyicjev4evnJHHm8rDpM

#SEXCOIN
 



Like Love Good Foto   
HELP ME !!!

SXC - SE7Yyb3MZvAr1aRyicjev4evnJHHm8rDpM

Пoнpaвилocь фoтo?  - SXC :      SE7Yyb3MZvAr1aRyicjev4evnJHHm8rDpM
https://vk.com/sexcoin_ru

Found some symbols that can be used in the forum (have given a couple a tryout in my signature and above header too...)


♀ ♂ ⚢ ⚣

More over yonder: http://unicode-table.com/en/sets/special-symbols/

There is a desire to pay webcam in Sexcoin ?
I can make it...

Any progress on the built-in webcam feature? That would be a game changer.

i was for a while, i had millions of coins! THe new client is pretty sweet. Looking forward to its update.

Also the android client testing is going ok, still not ready for proper usage but its getting there! Lavajumper is the man!

Wait.  You mean to tell me that all of these beautiful women aren't testing the new wallet???   

Is anyone else on TestNet testing the beta version of the new SXC Wallet?

#SEXCOIN

#SEXCOIN

#SEXCOIN

we wait

Sexcoin the next client.  0.10.4.0.

#SEXCOIN

#SEXCOIN

OK,
i test it.

my photos about the test https://bitcointalk.org/index.php?topic=432074.new#new

Update: Testnet connections:

As I posted before, we have a testnet up and running. Testnet's parameters are in line with what will be the standard after supermajority soft-fork is reached. If you need to test custom transaction creation or mining, this is the place to do it. Difficulty is low enough so you can cpu mine, and we have enough testnet nodes for mining to be fairly stable. There is also a testnet block explorer.

Testnet parameters for anyone needing them:

 
sexcoin.conf:

Block explorer: http://betest.sexcoin.info/chain/Sexcointest

The default testnet port is 19560
The default rpc port is 19561

The default data directory is /testnet3

  #SEXCOIN

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.

We are preparing for official release.

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!

If you are getting up to speed, take a moment and review these posts:

https://bitcointalksearch.org/topic/m.16627674

https://bitcointalksearch.org/topic/m.16541662

https://bitcointalksearch.org/topic/m.16702043

Age Verification and Sexcoin

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.