ZEOS!

eosio smart contracts + Hive = clarion private anonymous version of hive / steemit / voice with eos ubi ...

This is pretty cool,  I can't wait to get in this. Thanks for this info.

Stealth ALPHA testnet released on November 27, 2017: 
http://185.208.208.147:8080/ 
 
DO NOT TRY TO USE REAL FUNDS! 
USE AT YOUR OWN RISK. JUST REGISTER A DUMMY ACCOUNT. 
OUR NEW SERVER IS BEING UPDATED CONSTANTLY, SO EXPECT INTERMITTENT DOWNTIMES. 
 
Screenshots: 
https://steemit.com/cryptocurrency/@agorise/the-agorise-report-c-ipfs-stealth-and-blinded-transactions-pos-systems-mobile-wallets-graphenej 
 
Done (in a nutshell): 
 
* The UI and UX for Blinded, and Stealth Transactions — Some minor UI will have to be added once the receipts/backup schema are implemented towards the end of the project. 
* Range-proofs — users can now send arbitrary Blinded amounts, as the wallet can now “prove” the outputs are in-range (a very wide range that doesn’t reveal value amount or give an idea of bigness or smallness). (Previously, only a single output could be included in a transaction — no “change” — so a user would have to carefully pick the output value to match a combination of previous receipts.) 
* Receipts embedded in transaction — encrypted receipt data is now included in the “stealth_memo” field of the transaction.  (Although neither the CLI nor UI wallet support scanning yet, in the future this field can be used to scan the blockchain for incoming Blinded transactions, eliminating the need for manually sending receipts and for receipt backup. Further on (for Stealth) this data can be embedded and hidden in the range proof to save blockchain space.) 
* Various UI improvements. 
 
Remaining for Blinded tx (in a nutshell): 
 
* Code safety and review — (Mainly asserts on overflows and non-finite group elements, but also some other TODO’s kept for later — don’t wan’t any evaporated funds!) 
* Performance optimization — range proof calculation is currently SLOW.  Substantial optimization can probably be achieved by eliminating duplicated work when applying blinding factors and value offsets to large sets of commitments and BigIntegers. 
* Fee anticipation (so user can see what the fee will be before pressing “Send”) 
* Issue with picking a Blind value when sending Blinded-to-Public; likely a trivial issue/fix. 
 
..and for Stealth tx (in a nutshell): 
 
* Hiding ASSET type, and not just amounts 
* Hiding the metadata 
* Efficient blockchain scanning to detect incoming transactions, making receipts invisible to user. 
* Streamlined and efficient Stealth account generation; deterministic key generation and management; making Stealth account backups beyond the initial Brain Wallet or seed phrase unnecessary.
* Code cleanup. 
* Someone needs to write the BSIP (started here: https://docs.google.com/document/d/1kYuvK-aEsmwMqzWY3IKYhJA9DbcUw8fpsfzeI9gF1go/edit) 
* Hire a professional cybersecurity firm (TAD Group?) for auditing and Certification (Worker Proposal definitely needed) 
* Have the Bitshares core devs merge to master branches, after sufficient public testing. 
 
To report any issues found (feel free to wireshark, and run js console) please try to screen capture them for us and explain in simple detail what to do so that we can try to reproduce an errors or funky behavior. If something in the UI does not make sense, or if Grandma will never understand this, please share your ideas to make it more user friendly. We are open to all suggestions. 
 
As always, our open source can be audited here: 
https://github.com/Agorise?tab=repositories 
 
Current roadmap: 
https://docs.google.com/document/d/12VA48XbccZxYk56j_18ZRIU4fyr2Hui60-hetop-ZDk/edit 
 
Follow product releases and other news from Agorise, Ltd.: 
https://steemit.com/cryptocurrency/@agorise/the-agorise-report-c-ipfs-stealth-and-blinded-transactions-pos-systems-mobile-wallets-graphenej 
 
Telegram chat group: 
http://t.me/Agorise 

", you will be constantly getting returns based on how much you hold."

is it automatic or do you have to claim it in some way. I haven't been able to figure it out through the use of google.

credit where credit is due.

confidential transactions were introduced Jan 8, 2016 (or earlier, did not find an older git) by core developers and are available since then. GUI did not offer this feature, so that's what is/was(?) missing.

love this feature :)

KenCode has an interesting and colorful history. I started looking into it and had reservations on what I found. Ken Code is involved in BlockPay and Stealth, there was talk that "he is a scammer" or "was scammed." I really don't understand all this history, but it brings reservations to me. Do really want the cloak of darkness over the network?  Sunlight typically disinfects. Sunlight gets rid of corruption. Sunlight allows everyone to approve of and know who is good and who is bad and what is actually happening. If we add a cloak of darkness to Bitshares we will never know what is happening. I am not sure I want a potential scammer writing the code that hides him being a scammer.  We as a community need to have that discussion. I understand that some compromise might be needed. Maybe we do a partial stealth  where we only hid a portion of the information. Bob#####45 transfered  23,#### to J######h.

Have you heard what the fee will be for a stealth trans? Great article btw.....thanks

Great project from the sounds of it.  For the non-technical folks what is the biggest difference between blinded transactions and stealth?

I started to use bts and I think is easy and brilliant system

I really like your post ,,,,

bitCNY/bitUSD/bitGOLD + Stealth is a moon shot all on its own :)