In the world of Bitcoin wallets there is a plethora of security threats that you need to stackrank.
What anti-exfil would do is to break 90% of the current wallets’ UX to solve a fundamentally low-risk threat, relative to other threats. When better solutions exist.
A big no-no.
Introducing a new round trip / new interaction every single time a user signs a Bitcoin transaction is a terrible idea from both UX and engineering perspectives.
It violates Single Responsibility Principle. Coordinator should stay purely coordinating. No more, no less.
Great comment Rusty!
Just the basic idea of identifying that there are 3 groups of people (can afford; can sometimes afford; and cannot afford a UTXO whatsoever) is a huge upgrade over past conversations, which tend to jump straight into technical details and gloss over the actual user profiles and market demand.
Personally, I agree that more research is warranted. I’m not particularly optimistic on UTXO-sharing as a solution for people who can’t afford standalone UTXOs at all because of the group coordination cost, “Tragedy of the Commons”issue (LN counterparties are heavily incentivized to police their LN channel state, whereas in a Timeout Tree you can freeride others to do the policing for you, leading to no one doing it at all), “ghettorization” issue as you mentioned, and the inevitable complexity of any such solution. Secondly, did anyone bother to ask whether users like sharing at all? Why would they opt for a complex sharing solution when they can use something like gold for savings.
I’m slightly more bullish on locally-run ecash mints where people fall back to long-built relationships and hard-earned reputation to prevent cheating. Basically, use the social layer to address a technical limitation.
I like your quote here: “can’t engineer a solution if we can’t think about the problems.” That’s a great way to think about it. As someone else once said, the most common mistake engineers often make is to “optimize for something that shouldn’t really exist”. I’ve seen it happen way too many times, being an engineer myself. Just because UTXO-sharing with large N is possible, doesn’t mean it is ideal or will actually have a market.
In the spirit of thinking deeply about the problem (and not the solutions), it would be wise to also visit assumptions such as there will be 10 billion people who want sovereign UTXOs and the responsibilities that come with it. I think that assumption is highly unrealistic. IMO the actual demand will remain well below 500 million people, realistically more in the range of 100-200 million people. Being your own bank, as it turns out, is quite a heavy burden.
So if you believe in these numbers, Bitcoin does not have a scaling problem. At the very least, it’s not urgent at all. The math might work out by just making current things as efficient as possible.
Thank you !
I’ve been lurking on Damus for a while 😛 Great progress on UI/UX ! Cheers.
Agreed. Bitkey design clearly optimized for usability and I think they swung a bit too hard in that direction. Too many security concerns to be used for large savings. The mobile phone in particular is highly vulnerable. An attacker would know they can get to an owner’s bitcoins through the phone and the phone alone (just by waiting out the Delay and Notify protocol). If popularized, it will incentivize kidnappings.
I wrote a full review of Bitkey here: https://nunchuk.io/blog/bitkey
Two different devices, ideally always geographically distributed.
Author here. Thanks nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m ! Hope you guys can make some adjustments. Cheers.
Calling all self-custody experts!
Have you ever thought about starting a Bitcoin business that focuses on orange-pilling people and helping them self-custody? Putting your passion and skills to good use?
Now you can.
Introducing Byzantine: Collaborative Custody Platform-as-a-Service.
Read more about it here:
nostr:npub1teawtzxh6y02cnp9jphxm2q8u6xxfx85nguwg6ftuksgjctvavvqnsgq5u Verifying My Public Key: "hugohanoi"
I just published ‘Passphrases Are Not the Solution for Bitcoin Custody’.
https://hugonguyen.medium.com/passphrases-are-not-the-solution-for-bitcoin-custody-4f967a339b1b
Yeah we need widespread descriptors support first for safe + interoperable Taproot scripts.
First post. My AMA on Stacker News. Ask me anything about Nunchuk!
