Topic: [ANN][XST] Stealth-Coin.com | Tor | StealthText, World's first anonymous SMS Tx! - page 113. (Read 748429 times)

You probably dosed too high

Didn't remember a thing! Weird.

Its a trip man... hope you enjoyed it

i'm running 1.2.0.2
and
it says
this version is obsolete upgrade required
whats up with that ?

This release of StealthCoin adds StealthAddresses to perfectly hide receivers in a transaction. StealthAddresses are a type of cryptographic block chain obfuscation where innumerable destination addresses can be created from each public receiving address. The destination addresses can not be linked to each other or to the public receiving address. StealthAddresses produce lightweight transactions, requiring no more storage overhead than standard StealthCoin transactions. Moreover, StealthAddresses are compatible with Proof-of-Stake.

StealthAddresses necessitate a new kind of transaction in the block chain, which all clients on the network must recognize. For this reason, StealthAddresses will not go into effect for StealthCoin until 11:00 PM October 8, 2014 MST. They are, however, fully incorporated into the wallet with release 1.3.0.0.

This release also adds support for leveldb, a super-fast database back-end. Because the leveldb database structure is different from the previous database backend (BSD), an upgrade will require re-syncing the block chain. To make this process easier, links to OS X and Linux/Windows leveldb databases are below. These files may be downloaded and unpacked into your existing application data folder, after removal of the existing database files. Instructions for this process are forthcoming.

Finally, the Tor backend has been updated to the latest version 0.2.5.8-rc, which is a release candidate version. This update should bring minor stability, performance, and security improvements.

Links for the data files, Mac, Linux, and Windows Qt wallets are below. Daemon builds will be made available soon. The github repository will also be updated within an hour. This post, the OP, and the website (https://www.stealth-coin.com/) will be updated as new files are made available.

---

Linux
LevelDB Block Chain Data: https://drive.google.com/file/d/0B8rWObF4xz1YN21ZYVg4SG9CcGc/edit?usp=sharing
Manual Installer (zip): https://drive.google.com/file/d/0B8rWObF4xz1YQk9jV1ZfaE55d3M/edit?usp=sharing

Mac OS X
LevelDB Block Chain Data: https://drive.google.com/file/d/0B8rWObF4xz1YUktlOHFySUdQSVk/edit?usp=sharing
Disk Image Installer: https://drive.google.com/file/d/0B8rWObF4xz1YWk9BT3IwXzhYZWs/edit?usp=sharing

Windows
LevelDB Block Chain Data: https://drive.google.com/file/d/0B8rWObF4xz1YN21ZYVg4SG9CcGc/edit?usp=sharing
Auto Installer: https://drive.google.com/file/d/0B8rWObF4xz1YbEFXQlpUcDg5bTQ/edit?usp=sharing
Manual Installer (zip): https://drive.google.com/file/d/0B8rWObF4xz1YWnBiNGo4R2lpV3M/edit?usp=sharing

We'll update the website and OP within a few hours if it's not already done. It's been busy in the last couple of days, but we'll catch up with the little things soon.

---

Syncing with the New Build Made Easy

1. Back up your wallet
2. Stop the old client
3. Go to the application data directory
4. Remove blk0001.dat, blkindex.dat, database, db.log, and debug.log
5. Download the block chain data with the links above, appropriate to your system
6. Unpack the block chain data into the application data directory
7. Start the new client
8. It may take 2 or three minutes to grab peers
9. The chain may take 5 to 10 minutes to sync

Chandran signatures are a sub-linear ring signature system. The memory requirements scale with the square root of the number of keys in the ring. They significantly reduce the size of the block chain for medium and large-sized rings, of about 25 or more keys.

In crypto-currencies the sender must sign away funds, which accomplishes two tasks. The first is to prove ownership of the funds. The second is to authorize the transaction. The very act of signing a transaction conflicts with anonymity because the signature must be validated with a public key that is included in the transaction, and was the destination address for a previous transaction.

For anonymity, a problem arises: how can the signature be verified without revealing the source of the funds?  One way is to create some ambiguity in the transaction and make a signature that authorizes the transaction without revealing exactly which key was used to authorize it. Because the transaction network is a closed system, ambiguity must be created using elements of that system. These elements amount to the public keys found in the block chain.

A ring signature is one in which a set of these keys is used to sign a transaction in such a way that it is possible to verify that the transaction is authorized but impossible to ascertain exactly which of the keys in the ring had the signing authority.

CryptoNote ring signatures achieve anonymity by making a signature with each key in the ring. But there are two types of signatures in a ring signature. One type is for public keys not authorized to sign the transaction and the other type is for the public key that is authorized to sign the transaction. Outside of the individual who created the signatures, no one knows which signature type was used with which key. It's obvious, then, from where the bloat arises with CryptoNote transactions. A transaction using 100 keys must store those 100 keys and their 100 signatures.

Chandran signatures use the same principle except that Chandran signatures employ signatures of an unknown subset of the ring. Using a subset reduces the amount of storage for the signatures, but creates a new problem in that the identities of the keys sub-ring must be obfuscated. This is achieved by using mathematical proofs to assemble the unknown subset from the full ring. These proofs are called "non-interactive witness-indistinguishable" (NIWI) proofs.  Even though the person validating the transaction can use the proofs to derive a subset of the key ring, this person has no idea what the subset is because the subset has been mathematically scrambled during assembly. However, even though the subset is scrambled, it can still be used to verify the transaction signature and validate the transaction.

Yes.

11750 - I'm keeping my 12k-celebration-picture in reach, this is just the beginning of the mintpal-induced hype we'll get.

Bowl is packed, dunno what to expect. DMT, Yeah buddy!!!

Man I can´t stop LOL

INTERVIEW WITH SOEPKIP, CLICK TO WATCH : :