pull down to refresh

0 sats \ 0 replies \ @gbks OP 19 Nov \ parent \ on: Arké and BIP-177 (adding more options) Design
Unicorn at the top? I like it :)
Yes, for very practical reasons. Those were simply screenshots I already had. I try out a lot of wallets and always take screenshots as I go. Should have a bunch more in my photos that I can add.
As for versions, each screenshot can have a date or version attribute. But I don't have the time or ambition to create a perfect historical archive. If others chip in, sure, let's do it. But otherwise I would keep it more casual.
Heads up, this is a prototype demo. I've heard a lot of people ask for something like this over the years, but it's also a lot of work to maintain it. Curious to hear if you think this would be useful and if you would be interested in helping with the content. There's an issue for discussion here.
100%. Such an interesting phenomenon. I find that going back to the foundational assumptions is often a good approach. There is often some basic questionable leap that is being made and then everything on top of that is logical. Easy to look over the leap and get swept up in the logical part.
It is both hilarious and sad that he takes the antichrist stories literal. Someone seems to think they are particularly clever.
Here's what Claude and ChatGPT think is the most likely scenario:
"Strategy survives the next 5 years but as a shadow of its former self, with existing shareholders suffering 80-95% dilution. The company becomes a cautionary tale about the limits of financial engineering, regardless of whether Bitcoin reaches high prices. The complex web of preferred stocks and convertible debt creates a doom loop where each financing makes the next one more expensive and dilutive.
The preferred stock offerings (STRC, STRK, STRF, STRD) are essentially desperate attempts to buy time, but each new debt issue continues to worsen the situation, diluting the equity they've been issuing against"
Odds:
- 25% success - bitcoin reaches $500K+ by 2030, and the math works out
- 50% managed decline
- 25% financial collapse
Whether this is a good analysis, time will tell (I certainly can't).
Fees are getting quite complicated:
https://sdk-doc-liquid.breez.technology/guide/end-user_fees.html
https://docs.spark.money/home/faq#what-are-the-fees-like%3F
Seems impossible to clearly communicate to an end-user...
Claude's verdict: "This is a speculative capital structure built on a volatile foundation. It's optimized for Bitcoin bull markets but dangerously exposed to even modest downturns. A small loss in BTC price or confidence can cause disproportionate system stress. The structure will work until it doesn’t—then likely collapse fast."
Not pondering too deeply, I think there's a good chance this will end in some sort of mess. There's a lot of arrogance around the bitcoin prize, and people don't seem to be able to resist playing financial games until they get hurt. Glad it's being discussed.
Happened to me with Paypal. Small amount, just wanted to try out the feature. Was impossible to get the bitcoin out (self-custodial wallet, fresh addresses, site just threw error messages), support gave the same answers as in the post (security, for my own protection) and offered no solution, had to sell the bitcoin again and left the platform. Good to only keep minimal amounts on platforms and do test-runs before doing anything with even slightly larger amounts.
We're redesigning the Bitcoin Core GUI with a focus on design & usability. Would love to hear your thoughts on it. More info here: http://bitcoincore.app
Generally, you may like what we're doing in Bitcoin Design (https://bitcoin.design).
The answer is obviously yes to anyone who has managed a public project or community. A code repository is for code-related things and some very deep work happens there. The mailing list and other avenues exist for other types of conversation.
I think we're a bit too focused on onboarding UI now. Nonetheless, if all LSPs end up charging a certain amount for first channel open, wallets may want to let users know about that. No one likes hidden fees, especially not the first time you make a transaction. That would not build a lot of trust, no?
Maybe it is possible to just paper over channel fees altogether, routing fees cover it all, and users have a smooth ride. But maybe not. I just don't want to make that assumption without thinking through different scenarios.
Sure thing. It's great if the default works well to onboard people. And maybe once they have a sense for what their needs are, they can go in and fine tune things.
What I am curious about is whether the actual economics and marketplace dynamics will pan out that way. Those might in the end dictate what options users have. Can we already know at this point in time how things will go? Not sure even the teams that run today's LSPs do, considering the tech is still maturing and adoption and usage patterns will likely change.
I've been running Umbrel on a Raspberry Pi for some years and it runs super stable and requires no overhead. I connect to it with Zeus for payments on the go (that part is a bit shaky sometimes due to Tor). It's a nice setup.