Author Topic: STEALTH Status Update  (Read 18595 times)

0 Members and 1 Guest are viewing this topic.

Offline bytemaster

STEALTH Status Update
« on: April 04, 2016, 05:33:54 pm »
I want to take a moment to give everyone an update on where we are with STEALTH.

The hardfork today will allow us to transfer the STEALTH asset to [member=49]onceuponatime[/member] and the blockchain will be fully functional from that perspective.

The GUI release here: https://github.com/bitshares/bitshares-2/releases/tag/2.0.160323-stealth-beta implements an interface and set of functionality that we outlined in the proposal. 

The server-side wallet storage was not part of the proposal, but something we felt was necessary to backup/secure user funds. We do not yet have confidence in the reliability of server-side storage to enable this feature. There is a significant about of liability associated in offering to host/backup user wallets.  We don't want to be responsible for the loss of funds.

With todays hardfork and enabling of the fee-backed-asset along with the windows binaries we will release the STEALTH worker will technically be completed to spec. We were late and over budget so have actually lost money on this worker.

That said, I am not happy with the resulting product and user experience. It is still too hard to use for most people and therefore, it is reasonable to expect few will use it. 

In an effort to make things right for everyone, especially [member=49]onceuponatime[/member], we intend to implement an alternative in the months ahead:

Blind Transfers with Public Accounts

In this mode everyone will be able to tell which accounts are transacting with each other, but be unable to know the amounts involved. The impact is that you would be able to tell if someone sent money to an exchange, but would be unable to know how much. Furthemore, your
account balance would be completely private.

With this mode of operation it is possible to make blind transfers the default mode of operation while maintaining the same interface we have for normal transactions.  A simple checkbox can be used to enable public/free transfers.

This interface will generate many more STEALTH transfers and improve everyone's privacy while at the same time enabling the holders of the STEALTH asset to make more revenue.

We cannot promise a particular schedule for this enhancement, but will state that we intend to work toward it. We want to make sure that people can actually use privacy enhancing features and that [member=49]onceuponatime[/member] has a reasonable chance to recoup his investment.







For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline dannotestein

  • Hero Member
  • *****
  • Posts: 760
    • View Profile
    • BlockTrades International
  • BitShares: btsnow
Re: STEALTH Status Update
« Reply #1 on: April 04, 2016, 05:43:43 pm »
Making transactions default blinded sounds like a great idea, IMO. Currently I think transactions are a little "too public".
http://blocktrades.us Fast/Safe/High-Liquidity Crypto Coin Converter

Offline tbone

  • Hero Member
  • *****
  • Posts: 632
    • View Profile
  • BitShares: tbone2
Re: STEALTH Status Update
« Reply #2 on: April 04, 2016, 06:06:12 pm »
Perhaps [member=49]onceuponatime[/member] will consider immediately selling some of the stealth asset in order to not only recoup a chunk of his investment, but also to raise some funds to speed up implementation of stealth transfers / private balances.  This is a critical feature.  The sooner it gets implemented, the faster the Bitshares adoption rate will increase, and the sooner [member=49]onceuponatime[/member] will be in the black on his investment.

Offline mike623317

  • Hero Member
  • *****
  • Posts: 637
    • View Profile
Re: STEALTH Status Update
« Reply #3 on: April 04, 2016, 06:13:44 pm »

I think that's a good approach BM
 +5%

Offline CLains

  • Hero Member
  • *****
  • Posts: 2606
    • View Profile
  • BitShares: clains
Re: STEALTH Status Update
« Reply #4 on: April 04, 2016, 06:55:57 pm »
Perhaps [member=49]onceuponatime[/member] will consider immediately selling some of the stealth asset in order to not only recoup a chunk of his investment, but also to raise some funds to speed up implementation of stealth transfers / private balances.  This is a critical feature.  The sooner it gets implemented, the faster the Bitshares adoption rate will increase, and the sooner [member=49]onceuponatime[/member] will be in the black on his investment.

Yes, let's do the stealth token sale. If I was onceuponatime i'd give 5% to someone for organizing and outlining properly what needs to be done, including a crowd-sale and an independent stealth wallet with unique branding and marketing. This project needs more than some devs and an investor, it needs a savvy entrepreneur who can take it to the next level. Now that you have the basic tech in place and a token to represent the value of the project, there's nothing stopping you from making this project as big as you want. /2 cents

Offline Tuck Fheman

Re: STEALTH Status Update
« Reply #5 on: April 04, 2016, 06:57:03 pm »
Making transactions default blinded sounds like a great idea, IMO. Currently I think transactions are a little "too public".

 +5%
Lucksacks.com - The Largest Cryptocurrency Freeroll Poker Site in the World!

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4377
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
Re: STEALTH Status Update
« Reply #6 on: April 04, 2016, 07:55:05 pm »
Different voices here:

Who decided that one can add whatever feature to BitShares at will, even it's "for free"?

Why should any new feature split 80% to Mr. Once or the STEALTH asset holder, and let them decide the fee rate beyond the committee (read: stake holders)?
BTS account: abit
BTS committee member: abit
BTS witness: in.abit

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12915
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Re: STEALTH Status Update
« Reply #7 on: April 04, 2016, 08:02:59 pm »
Different voices here:

Who decided that one can add whatever feature to BitShares at will, even it's "for free"?

Why should any new feature split 80% to Mr. Once or the STEALTH asset holder, and let them decide the fee rate beyond the committee (read: stake holders)?
That has been approved by shareholders by means of a voted worker for the corresponding BSIP ... IIRC
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4377
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
Re: STEALTH Status Update
« Reply #8 on: April 04, 2016, 08:14:03 pm »
Different voices here:

Who decided that one can add whatever feature to BitShares at will, even it's "for free"?

Why should any new feature split 80% to Mr. Once or the STEALTH asset holder, and let them decide the fee rate beyond the committee (read: stake holders)?
That has been approved by shareholders by means of a voted worker for the corresponding BSIP ... IIRC

1. Details of the approval? it includes adding any new feature?

2. BSIP10 hasn't been approved? Apparently this feature will reduce the value of BSIP10, which is designed to feed the referral program.

3. All balances hidden? So how will it affect the "rate limited free transaction" feature?

4. This feature is one of the "stable core features of BitShares" mentioned in last week?
« Last Edit: April 04, 2016, 08:16:46 pm by abit »
BTS account: abit
BTS committee member: abit
BTS witness: in.abit

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12915
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Re: STEALTH Status Update
« Reply #9 on: April 04, 2016, 08:46:52 pm »
Different voices here:

Who decided that one can add whatever feature to BitShares at will, even it's "for free"?

Why should any new feature split 80% to Mr. Once or the STEALTH asset holder, and let them decide the fee rate beyond the committee (read: stake holders)?
That has been approved by shareholders by means of a voted worker for the corresponding BSIP ... IIRC

1. Details of the approval? it includes adding any new feature?

2. BSIP10 hasn't been approved? Apparently this feature will reduce the value of BSIP10, which is designed to feed the referral program.

3. All balances hidden? So how will it affect the "rate limited free transaction" feature?

4. This feature is one of the "stable core features of BitShares" mentioned in last week?
Doing STEALTH or not is a client side decision and thus depends on the wallet implementation. Not on the backend code.

Also, not all assets allow blinded transfers for legal and technical reasons .. there are plenty of usecases that cant makt use of stealth.

That said, i understand your frustration that BM again again takes the lead and makes decisions without prior discussion.
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4377
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
Re: STEALTH Status Update
« Reply #10 on: April 04, 2016, 09:25:39 pm »
Different voices here:

Who decided that one can add whatever feature to BitShares at will, even it's "for free"?

Why should any new feature split 80% to Mr. Once or the STEALTH asset holder, and let them decide the fee rate beyond the committee (read: stake holders)?
That has been approved by shareholders by means of a voted worker for the corresponding BSIP ... IIRC

1. Details of the approval? it includes adding any new feature?

2. BSIP10 hasn't been approved? Apparently this feature will reduce the value of BSIP10, which is designed to feed the referral program.

3. All balances hidden? So how will it affect the "rate limited free transaction" feature?

4. This feature is one of the "stable core features of BitShares" mentioned in last week?
Doing STEALTH or not is a client side decision and thus depends on the wallet implementation. Not on the backend code.

Also, not all assets allow blinded transfers for legal and technical reasons .. there are plenty of usecases that cant makt use of stealth.

That said, i understand your frustration that BM again again takes the lead and makes decisions without prior discussion.
As long as changes are not made on the back end, I'm fine.
BTS account: abit
BTS committee member: abit
BTS witness: in.abit

Offline Brekyrself

  • Hero Member
  • *****
  • Posts: 511
    • View Profile
Re: STEALTH Status Update
« Reply #11 on: April 05, 2016, 02:21:09 am »
[member=5]bytemaster[/member]

You mention our account balance can be hidden, how so?  If Account A has 100 bts and blind transfers to account B 100bts with the blind feature, we can still see Account A HAD 100bts and now has 0?  We can easily assume Account B now has 100bts.  What am I missing here?  Is the only way to gain true stealth still through a mixing service?  This appears to be similar to 0.93?

Once a balance is hidden, how will it effect voting?

Can additional features be added to hide things like who we are voting for?  Our white/black lists?  Assets?  Permissions?

Another example is when we browse a user's ID, why does the membership option even appear?  Perhaps removing things like this could minimize data usage and lower latency?
« Last Edit: April 05, 2016, 02:25:23 am by Brekyrself »

Offline Thom

Re: STEALTH Status Update
« Reply #12 on: April 05, 2016, 04:02:03 am »
How disappointing. I was hoping stealth would be approached more carefully than previous UI dev efforts but it appears that wasn't to be. I contributed my perspective, tho limited, early on but it was not considered or discussed. Ultimately it was Once's call to decide if he accepted the design spec. He pushed back at several points, but mostly on the business aspects not much on the UI design.

I wished there were more design discussions before the work began, however as usual there is always pressure to finalize the design and get on with implementation.

Just today I was using the wallet and thinking to myself it is finally (6 months after initial release) looking very good now. There is always room for improvement and unless you have set specific design goals development will never end. Its setting the goals / milestones that provide a way to measure progress and know when objectives are complete. There is a definite lack of such planning by CNX. What is the right balance between agility to react to market forces and the stability of establishing a plan to guide the trajectory of progress? I don't know but I know they haven't found it yet!

Good UI design takes a great deal of planning. Cut that short and the results will not be optimal.

I also agree with abit's comments. CNX can implement a blind transfer feature, but it should not be up to CNX if that feature is deployed into the BitShares. Expectations have already been set and blind transfers were not among them. Rather than giving up and implementing some other privacy feature (and why should we expect that will be implemented any better than the attempt to implement stealth?), why not take some time to see what went wrong and make an attempt to correct those things and go at it again with a better approach? Why divert resources in another direction?

[member=5]bytemaster[/member] - what is it about the UI / UX you don't like? What is so bad it can't be fixed with less effort than implementing a blind transaction feature? I don't see how blind transfers could be done without changes to both frontend AND backend.
« Last Edit: April 05, 2016, 04:06:51 am by Thom »
Injustice anywhere is a threat to justice everywhere - MLK |  Verbaltech2 Witness Reports: https://bitsharestalk.org/index.php/topic,23902.0.html

Offline freedom

  • Sr. Member
  • ****
  • Posts: 303
    • View Profile
Re: STEALTH Status Update
« Reply #13 on: April 05, 2016, 04:26:20 am »
oh, F**K    -5%-5%

Offline btswildpig

  • Hero Member
  • *****
  • Posts: 1424
    • View Profile
Re: STEALTH Status Update
« Reply #14 on: April 05, 2016, 06:01:30 am »
What if Stealth cause more issues (bugs , other negative impact like performance, scalability even user safety ) , some may even been realized after one year , who will pay for fixing the bugs ?

Will that be one of those things where "if you don't pay , the blockchain will suck , so the reality is ...."

So is this really a total private funded project in this aspect ?

Will there be a fund paid by the private money dedicated to maintain all related bug fixes now and in the future if any bug were introduced on the blockchain because of this feature ?
这个是私人账号,表达的一切言论均不代表任何团队和任何人。This is my personal account , anything I said with this account will be my opinion alone and has nothing to do with any group.