nostr:nprofile1qqsqfjg4mth7uwp307nng3z2em3ep2pxnljczzezg8j7dhf58ha7ejgpp4mhxue69uhkummn9ekx7mqprpmhxue69uhhqun9d45h2mfwwpexjmtpdshxuet5hgfg9w are we really limited to just nunchuk and BlueWallet for good multisig on mobile in 2026?

BlueWallet is great but “feels” clunky. Nunchuk comes with all this inheritance crap and email signup requirement.

Am I missing something?

Incredible! Thank you!

The use case is that I believe it’s too common that bitcoiners wind up with 5-6 wallet apps on their phone, where the fiat analogue is 2-3 at most, for many people 1-2.

Cove has beautiful UX and so much going for it, and given the top tier hardware wallet support, it strikes me that it’s primarily a savings/hodl wallet versus a spending wallet.

So I figured it would be good to consolidate multiple wallets into Cove, with the majority for monitoring purposes. Hence watch-only suffices. For multi-sig, this is indeed complex and can be handled with nunchuk for people who want to manage multi sig on mobile, or (more likely imo) handled via Sparrow/Electrum.

Hope this helps!

OK, I totally acknowledge that (and agree with the perspective).

Is there—or could there be—a means of “watching” a multisig wallet in Cove? Explicitly I mean no ability to sign and broadcast a transaction; genuinely only watching the wallet?

nostr:nprofile1qqsy8us3d6u5ynddk7lq7yz365hqqsptzd2923fvkgj4eepsady08uspzfmhxue69uhhqatjwpkx2urpvuhx2ucpr9mhxue69uhhyetvv9ujumtfde5ky6t5wvhxxctndqgx2k3m forgive me if I’ve missed something but what’s the status on multisig support in Cove?

Been wanting to migrate my blog to Nostr for years now. We’re just not quite there.

I really want nostr:nprofile1qqs8t4ehcdrjgugzn3zgw6enp53gg2y2gfmekkg69m2d4gwxcpl04acppemhxue69uhkummn9ekx7mp0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0l2sp3z to be great. Early days, but the promise is real: Signal, but better, and with zaps.

This is Christmas.

Are there any solid alternatives to Zeus other than Alby Go? Speaking about essentially a remote control for a node on the go; the original Zeus premise.

Zeus is becoming something like a spork whereas Alby Go just isn’t quite there yet.

Ah, good old post-Christmas late night rabbit holes.

I find Primal + NWC to be the ideal

Hear me out: your nostr keypair doesn’t need to be super-protected and storing it in iCloud/Google Drive behind biometric auth is absolutely fine + delivers a 10x experience for normies.

It should be the default.

All this frostr bunker shit is a total waste of engineering cycles; ya’ll aren’t holding the nuclear codes.

Strong agree. It’s still all too weird. nostr:npub1v5ufyh4lkeslgxxcclg8f0hzazhaw7rsrhvfquxzm2fk64c72hps45n0v5 is improving things significant in terms of easy distribution but getting regular people into Nostr is still far, far harder than it needs to be.

The socials are just opt-in spam now. Like a Hotmail inbox out of control.

The failure to recognise it is the most staggering to me; the unimportant and the deranged is given as much airtime and credibility as the critical and profound.

This is because the old guard have totally lost control and has resorted to simply reading the internet to the elderly.

When we look up from our phones and disregard the spam, signal will cut through.

Decades of underinvestment.

Agree. Encourage your tradespeople to accept Bitcoin *today!*

I don’t understand this direction. Who wants this?

Whoops:

"albyAuthUrl": getalby[dot]com/oauth?client_id=[REDACTED]&redirect_uri=https%3A%2F%2Fgetalby.com%2Fhub%2Fcallback&response_type=code&scope=account%3Aread+balance%3Aread+payments%3Asend&state=unused"

nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm Question (curious, not assuming bad faith): what information are you gathering on each and every AlbyHub instance running out there, including the selfhosted?

For the privacy conscious, this albyauth URL in Get Info is what I’m referring to:

"albyAuthUrl": "https://getalby.com/oauth?client_id=%5BREDACTED%5D&redirect_uri=https%253A%252F%252Fgetalby.com%252Fhub%252Fcallback&response_type=code&scope=account%253Aread+balance%253Aread+payments%253Asend&state=unused%22

*taps mic* Attempt #7 to get into nostr

What about yubikey-as-passkey?

Was thinking for scalability; such addresses could spend without requiring confirmations/“off chain”. I may have gone down a useless mental rabbit hole…

nostr:npub1az9xj85cmxv8e9j9y80lvqp97crsqdu2fpu3srwthd99qfu9qsgstam8y8 noob question. is there an equivalent for RFC 1918 for bitcoin addresses? ie to share UTXOs could we do NAT’s “hack” for IPv4 “to Bitcoin”?

If this has already been investigated, or this is what Lightning is, etc… I apologise for my poor understanding.

I’m conceptually thinking of a defined range of `bc1p…` addresses that represent private space, where a new, “local” address format can transact “off chain”

…maybe this idea is horseshit. IDK.

Damus is just materially better than Primal. So much more fun to use.

This guy has always been full of shit.

Every time nostr:npub14mcddvsjsflnhgw7vxykz0ndfqj0rq04v7cjq5nnc95ftld0pv3shcfrlx has a major Reform figure on his pod, they’re out/sacked/resigned within a week… coincidence?!

Nothing better than some Monday afternoon male astrology, especially when it foretells good tidings!

"the revolution wasn't the revolution i thought it would be"

—every revolutionary, ever.

Amazing and exciting. How are you thinking about Nostr Wallet Connect?

The irony of you making this critique from a primal.net address should be lost on no one.