Thread

LFG 🤙

Thanks! Goal is simple: make Blitz so smooth you’ll want that NIP-05 name + LNURL address to end in blitz-wallet.com 👀

Already ✅😅🤙 Satoshiii@blitz-wallet.com

What’s the new accounts setting in Technical settings for?

It lets you create multiple wallets effortlessly. For example, if you want to set aside funds for your child, you can create a wallet now, gradually transfer funds into it over time, and then share the seed phrase with them when they’re older.

Simplified, it allows you to create multiple wallets within a single app.

Wow that’s really a nice option thanks for the great work you’re doing.

Spark is a trap. Stop being stupid and centralized. https://unlimitedhangout.com/2024/10/investigative-series/the-chain-of-command-how-facebooks-libra-bank-regulators-and-paypal-built-a-new-world-currency/

'Stop being centralized'— typed from someone using a custodial LNURL, the irony writes itself 🤷‍♂️

An anonymous custodial service is nothing like Spark's state chain and its partners, and you know this very well.

From Blinks website: The phrase "Not your keys, not your coin" underscores the importance of owning the private keys to your Bitcoin, emphasizing that without control over these keys, you do not fully own your BTC. This principle is particularly relevant for users of custodial wallets like Blink, where the platform holds the keys and, consequently, control over the funds. To ensure true ownership and security of your Bitcoin, it's crucial to withdraw your BTC from custodial exchanges and manage your own keys directly Spark: https://docs.spark.money/wallet/developer-guide/unilateral-exit Both require some form of permission. One allows you to leave regardless.

At the end of the day, we believe in users having options. Some people want Blink's services, others want the aqua experience, and some might want what Blitz has to offer.

I'd zap this, but my wallet can't do it! 😬 I also tried to work around it via NWC, but they are getting message timeouts when trying to talk to Blitz 😞

Yep, we found that and fixed it after the newest release. Will be fixed next week!