So… still not private by default, and left up to wallet devs to decide on whether to make their wallet z-addr-only or not.
What a terrible decision that continues to hurt the few real people who want to use Zcash to transact.
Enforce privacy by default or GTFO.
What a terrible decision that continues to hurt the few real people who want to use Zcash to transact.
Enforce privacy by default or GTFO.
https://twitter.com/CoinDesk/status/1381631726909284354
To prove my point:
explorer.zcha.in/statistics/usa…
Last month Zcash had 181,568 transactions and only 5,365 of those were fully-shielded.
Less than 3% of Zcash users *actually use* the privacy of Zcash.
Anything less than z2z-only shows disdain for the few users of Zcash.
explorer.zcha.in/statistics/usa…
Last month Zcash had 181,568 transactions and only 5,365 of those were fully-shielded.
Less than 3% of Zcash users *actually use* the privacy of Zcash.
Anything less than z2z-only shows disdain for the few users of Zcash.
It’s also interesting to note that this new wallet SDK seems to imply that users will not be able to tell if their transaction will be fully shielded or not, and it depends on recipients wallet.
Which is… incredibly harmful for end-users if I’m understanding that properly.
Which is… incredibly harmful for end-users if I’m understanding that properly.
The most frustrating part of this is that with the move to a trustless setup Zcash’s privacy protocol actually becomes interesting and is quite strong.
They just choose to ignore the necessity of z2z-only at their user’s expense.
So frustrating to see so much good go to waste.
They just choose to ignore the necessity of z2z-only at their user’s expense.
So frustrating to see so much good go to waste.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
