X.KOJIRA.IO
Timeline

Seth For Privacy

[email protected]
npub1tr4dstaptd2sp98h7hlysp8qle6mw7wmauhfkgz3rmxdd8ndprusnw2y5g
Privacy is a human right and necessary for freedom.

- VP of Operations at Cake Wallet
- Privacy advocate
- Host of optoutpod.com, a privacy-focused podcast
Summarizing my thoughts on ecash

For some reason this ecash trend seems to be gaining steam instead of going away, so I'll try my best to detail my thoughts on ecash into one post.

1. The incentives are broken

Ecash finds itself between a rock and a hard place. For users to trust the mint, they need to know that the people behind the mint are trustworthy. If the people running the mint reveal their identities (or even just nyms), they're a trivial target for regulators and law enforcement as it's clear a mint is an MSB.

If the people behind a mint don't reveal their identities or nyms, users of that mint are subject to trivial rug pulls with no recourse. Which do you prefer as a user? Mint operator rug pulls or government rug pulls?

If a mint had been targeted like Samourai Wallet was, instead of just a potential privacy loss, all users would have lost all of their Bitcoin.

2. Ecash is not "self-custodial"

For some reason this concept of ecash being "self-custodial" is a thing, merely because the tokens themselves are self-custodied (and require proper backups of seed phrases etc.) While the lines get a bit weird, it's important to separate two things:

1. The asset people want is Bitcoin, not ecash tokens.
2. The asset people give up custody on is Bitcoin.

The ecash tokens themselves are completely worthless IOUs without the Bitcoin behind them, so even if I can take custody of my ecash tokens, I have 100% given up custody of my sats to a third-party.

Because of this, talking about ecash as self-custodial is disingenuous -- no one wants empty IOUs, they want Bitcoin. When they use ecash they do not have custody of their Bitcoin.

3. Ecash still requires all of the hurdles of Bitcoin self-custody

The hardest hurdle for many people to adopting Bitcoin is the simple first step -- writing down 12 words and making sure not to lose them. With ecash you still have this single greatest barrier of entry as you must backup a seed phrase or secret in order to restore your ecash tokens.

4. There is no incentive for custodians to implement ecash

While a custodian could switch to ecash out of the goodness of their heart, the incentives are broken for custodians. Not only does ecash harm the UX their users are used to (not having to store a secret seed phrase), it also introduces additional infrastructure complexity. Instead of just running a database, now they have to run additional mint software to provide their users with tokens, and handle support cases where users lose their tokens.

In theory a custodian could just also store the seed phrase for their users, but then have we actually improved on custodians at all? They even have custody of the ecash tokens in that case.

5. Custody is a line that cannot be crossed

The core of what makes Bitcoin unique is that we can actually take custody of it ourselves, gaining immense freedom and self-sovereignty through a bit of personal responsibility. Even though I am a massive proponent of building better privacy tools, sacrificing custody to get better privacy is a non-option for me.

Surely we can do better and build privacy tools on top of Bitcoin (or directly into Bitcoin's consensus layer) that allow us to have both privacy and self-sovereignty via self-custody.

I will not give up custody of my Bitcoin, no matter what, and you shouldn't either. "Better custodians" are just custodians with extra steps, and still strip us of self-sovereignty and thus freedom.

6. Time is a more scarce resource than even Bitcoin

Even though I have been very outspoken on what I view as a pointless venture, I am not here to stop anyone from building what they enjoy in the space. Devs working on ecash are free to do so as of course I have no control over them, though I fear that time spent on improving custodians is time that we will not get back. It's clear that the US gov and many in the EU are seeking to ramp up their attacks on Bitcoin privacy and self-custody, and our time to build tools to route around them is growing shorter and shorter.

P.S. - None of what I write is a direct attack on any ecash dev, and I have immense respect and personal relationships with most of the people working on this stuff. Respect for an individual doesn't have to mean I agree with them on every avenue they pursue.

https://i.nostr.build/oM0YW.jpg
Love it, sounds like a solid setup overall!

And no need at all to switch seed lengths, that was never the goal of the article.

If you've got a solid setup with 24 you're set, more for new entrants and defaults to use 12 words 🙂
I generally wouldn't recommend seed splitting schemes as they're very easy to brute force in most common configurations.

Finding the remaining 8 words of your seed wouldn't be very difficult at all (remember difficulty goes up exponentially per additional seed word).

Splitting into 12 word shards would at least be resistant to brute forcing but has other issues. Could do 12 word seed + passphrase, perhaps? Or an encrypted microSD backup?
This article was a passion project of mine as it's something I've long wanted to answer, and surprisingly seems to have no one-stop resource out there.

Let's make 12 word seed phrases the standard across the Bitcoin ecosystem!

Would love to hear y'all's thoughts on this one as it's a pretty divisive topic sometimes, but hopefully this can put things to rest and help simplify people's Bitcoin journey a bit by reducing the size of the secret they have to store.

Steel stampers everywhere will be happy 😅

A huge shoutout to my friend Luke Parker, a brilliant developer and cryptographer, for providing amazing cryptography feedback for me throughout.

Couldn't have done it nearly as well without him, and he always keeps me humble and makes me want to keep learning!

nevent1qqsv44d9zw8…
Absolutely exhausted and don't have the energy to copy paste this from Twitter, but I put together an exhaustive thread on the nightmare fuel that is Ledger Recovery here:

https://twitter.com/sethforprivacy/status/165854465876127…

Nitter: https://nitter.sethforprivacy.com/sethforprivacy/status/1…
Looking forward to leading a Nostr workshop tonight here!

They're building a fantastic Bitcoiner community in Charlotte and I'm really blessed to be able to give back and share what I'm learning there tonight 🙂

#[0]
Not true for the vast majority of users, Tor is not default at all.
Wasabi, which you agree to when enabling CJs in Trezor Suite:

https://i.imgur.com/e05CPNA.png
Buy fireworks or do legal sex work? CENSORED, no privacy for you!
I don't want to give Max a platform, I've already rejected his request to come on directly.
They're not just OFAC compliant, they censor for a variety of reasons:



https://i.imgur.com/83JDb32.png
No, no impact, but you hopefully aren't using Trezor Suite for managing funds, right?

If you use their software you reveal your balance/addresses to them by default.

If you're not using their software (use something like Sparrow!) it's a fine device even though I'd question their ethos now.
Important to know it doesn't change trust in the provider, it just reduces single-jurisdictional or single-datacenter risk of surveillance or compromise.

I think for most people it's overkill in almost any scenario.
Let's make privacy in Bitcoin the standard 🤝

#[0]
Some additional clarifications:

- I *will* be commenting on aspects of Samourai Wallet's approach that I don't like or view as less than ideal.
- I *will* be commenting on aspects of Wasabi Wallet I like or appreciate.
- I *will not* be going into depth on JoinMarket as I don't have a deep grasp on its approach. I'll only cover the basics I know and leave it at that, and likely publish follow up work with more in-depth thoughts.
I said I was biased in response on Twitter as all people are.

I also made it clear I won't comment on what I don't know, and thus have very little to say on JM.

Yet again you have some core hatred for me though we've never met and you've never actually interacted with me online, only thrown shade blindly 🤷‍♂️
It's not a comparison, never said that was the goal.

It's breaking down my understanding of the pros and cons of each.
Somehow it's already Sunday, and thus time for #SkepticismSundays 🤔

The goal of this thread (which I'll post weekly on Sunday's) is for discussing the uncertainties, shortcomings, and concerns some may have about Bitcoin.

NOT the positive aspects of it.

Discussing things with a critical thinking approach and level-headed discussion helps us learn where Bitcoin and it's community can improve and go from there. We had a *fantastic* amount of good conversations last week so I can't wait to see this week's!

What's gotten you thinking, has you concerned, or always irked you about Bitcoin, its ecosystem, etc. this week?
Goal for this week is to put out a blog post with a summary of my thoughts on Samourai, Wasabi, and JoinMarket.

The idea is to be as open and honest about tradeoffs of each as I can, but I admittedly have very little experience with JM so that will be only a short section.

Any specific points of interest you'd like to see covered for any of those three?

Any core comparisons that would be helpful for you all?
Added, thanks!
What relays do you pull from there? Wonder if I should set some specific relays in the Nostr plugin.
😅
So odd, wonder if it is the rate limiting mentioned by #[7]!
Shows for me, let me tweak relay settings for it.
Fully self-sovereign Zaps in pre-release for BTCPay, public release of the plugin update any minute now.

Bounties. Work.

Thanks so much for the hard work on this, #[3], huge step forward in being able to use Nostr the right way!

#[0]
All hail king #[5] 🤯
ITS WORKING 🔥
Think I've got non-custodial fully self-hosted Zaps working 👀

Can anyone Zap a sat to test Zaps to BTCPay Server??
👀

Excited for this both from a personal perspective and for the sustainability of #[1] themselves. Signed up a couple weeks back, can't wait!

#[0]
older →