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.
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.
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.
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.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Seth Simmons

Seth Simmons Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @sethisimmons

13 Apr
1/ In the latest twist to this odd situation MobileCoin bailed on their own AMA and instead put out a coordinated blog post with Signal:

signal.org/blog/update-on…

2/ The blog post essentially says that now they are open to integrating existing currencies once they reach characteristics only available to centralized currencies ATM, but will integrate MobileCoin in the meantime.

Requirements: Image
3/ It also intentionally mentions Zcash as a future possibility (with speed improvements) without mentioning Monero, who MobileCoin have to thank for their entire privacy protocol.

Full quote: Image
Read 9 tweets
12 Apr
Not sure where all of this “Lightning Network will destroy all outside of #Bitcoin” is coming from lately, but important reminder that if LN succeeds, it can be implemented on #Monero:

eprint.iacr.org/2020/1441.pdf

Monero has *proven* itself capable of implementation of improved tech
This is a big “if”, as there are still serious issues with the LN protocol that, to my knowledge, have yet to be fixed:

arxiv.org/pdf/2002.06564…
arxiv.org/pdf/2003.12470…
arxiv.org/pdf/2006.08513…
eprint.iacr.org/2021/384.pdf
But if all of those issues are able to be resolved (among others), Monero can implement LN on top of a private and scalable base-layer, which would make it *better and cheaper* than LN on Bitcoin.

Bitcoin has proven it cannot iterate, Monero has proven the opposite.
Read 4 tweets
7 Apr
1/ After a good bit of research and some back and forth on Twitter, I wanted to put out a thread with my thoughts on MobileCoin.

Tl;dr -- MobileCoin uses the Monero protocol to provide strong privacy for users, but sadly relies on Intel hardware guarantees and centralization.
2/ MobileCoin chose to build their protocol with the entire Monero protocol stack for privacy, while relying on Intel SGX for validation of transactions:

github.com/mobilecoinfoun…

This reliance means that Intel becomes a trusted participant in the network and assumes no backdoor
3/ Unfortunately, even though MobileCoin based their entire transaction protocol around Monero (rewritten in Rust, which is great!) they blatantly ignored the source of the protocol:

Read 23 tweets
18 Feb
1/ @GrapheneOS crossed the line for the last time last night, and I now have to strongly recommend no one use their OS.

After weeks of reply spam, sockpuppet spam, and DMs, they reached out to *another* #Monero community member I respect via DM and slandered my reputation.
2/ While the OS itself may be fine (I know people using it without issues), I cannot in good conscience recommend something that is led and built by people that would stoop to these levels simply because I chose to use @CopperheadOS and recommend it based on my own experience.
3/ As of today I have removed any mentions of it from my blog, and will solely recommend people use @CopperheadOS or @calyxinstitute if they want to move to a de-Googled and more private mobile experience.

Enough is enough.
Read 5 tweets
16 Feb
/1 @lmessenger pointed me to a PageSpeed analysis of my blog and provided some great pointers on speeding up my static site I'll share below:

developers.google.com/speed/pagespee…

These changes dropped average time to interact from ~4.5s to ~1.5s, a massive improvement in UX.
2/ The first change was to implement browser caching of static files following this guide:

digitalocean.com/community/tuto…

Simply adding the block in my NGINX conf file and adding a line to each server block gave a huge increase in load speed to repeat visitors/assets shared by pages.
3/ The second was to enable GZIP but use server-side pre-compression following this guide:

blog.llandsmeer.com/tech/2019/08/2…

See the following portion of my post on how I built sethsimmons.me for how I do the pre-compression:

sethsimmons.me/guides/buildin…
Read 4 tweets
7 Jun 20
1/ Decided to finally take the leap and test out @SamouraiWallet w/ Dojo end-to-end.

I try to keep an open mind and keep testing out privacy tools outside of #Monero, and had not yet tested the Dojo portion of Samourai.

I’ll detail findings in this thread:
2/ Install was relatively easy for someone with a sysadmin background, but did require generation of *many* passwords and API keys.

Integration with my existing Tor relay/node was vague, need to look into how I can better integrate Dojo into my existing Tor setup.
3/ The actual installation took about ~10m, with the sync of the Bitcoin node kicking off after that.

Once the Bitcoin node syncs up, I’ll report back here in this thread 🙂

Should be ~4-6h from my previous testing!
Read 15 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!