Avatar
optout
b190175cef407c593f17c155480eda1a2ee7f6c84378eef0e97353f87ee59300
freedom tech ⚡ freedom money

Set a receiving LN address (LNurl), and enjoy the inflow of zaps B)

I was wondering about generalizing the lightning 'channel' construct to 3 (or more) parties. I found an answer on stackexchange! I will keep digesting this... Even if it's not possible, it would improve my understanding of other L2 options.

I realized I don't know much about the essence of eltoo.

nostr:note1zqtgen4j6l7qdtv77vf3dfxk2axad3pxumtza09a0w7e6kw5lh5s3g8sgn

https://bitcoin.stackexchange.com/questions/116257/why-arent-3-party-or-more-channels-realistically-possible-in-lightning-today

nostr:note1u2m00m5rhgqtuz325l0ukceq5qasqeuwdreq2npws906m24g6pyqvu3tjp

I was wondering if the lightning channel construct could be generalized to 3 (or more) parties; I've found the/an answer in this bitcoin.stackexchange.com question.

Really exited about that, but from what I got nsecBunker is MUCH more than a keeper of a pleb's nsec, but can cater to an entire organization (e.g. company account), and as such it is more complex.

I've got to check it out in more detail ;)

I wonder if NIP89 could be also used for linking to a NIP46 Nostr Connect keystore mobile app?

nostr:note1u3d0zljl0c2ycde5wcnysd70gfd96pme9vkd8awr8lmyzgvvgrqq385kzs

Got thinking about Nostr Connect (NIP46) setups, triggered by nostr:npub1nqulzcxcj0d2uesusstgupl5du8pa96xl6uy8xndweeckjkn964qjs23sn .

There are two apps involved:

[1] client app (wants to sign, has no sec key)

[2] keystore app

Different setups are possible:

- client in browser, keystore in browser extension (like Alby)

- client in desktop browser, keystore in mobile app: display/scan QR code

- client in mobile browser, keystore in app (same device) -- ? maybe deeplink+NIP89 app handler

Manually swtiching to the app and copypasting connect string is a fallback, but terrinle UX.

nostr:note14m7zjf6puz23ml8xr02ryqlu9m6sesmj3rnklwqjychtfzqznglq5gxt60

NIP-89 rules!

People often nuke their Nostr contact list. This can happen e.g. when a client uses a not-recent version of the contact list, and reposts it.

For examples, check out messages of this bot:

nostr:npub19urfrvp4hpvgelwnmlfpzk2neuw6h2rgmwmr6f0pula87fvleqfs3krmt8

nostr:note1sz2k8dnr4658qt2z4nf2hsdh79e6k6nvs0vrhpm5aet4nzpfpmps847t3u

nsecbunker by Pablo, keeper of nostr keys

nostr:note1dzpa5f7par0er6zzy7s80q98gzlmhnmmpy5dafmteguk9pg77v6s7t5xnj

Nostr Army Knife, little tool to parse any nostr ID. https://nak.nostr.com

nostr:note1qxcpmx5zs6j6wpzftpaw7t3vmzqxhfvv6528h9r6tk8rgh5mf5yszpkhds

Primal caching server. There was an explanation on the OSS caching servers by Primal.

Bitcoin must be *both* sound store of value *and* medium of exchange.

Without the second, it's like a deserted castle where nobody visits,

without the first, it's like a castle built on sand.

Fire up your old miners in the basement, the BRC20 crowd is streaming sats to the miners!

Time to plug those dusting old miners 😎

Was picked up my Restore-follow-list bot (wip) 😎

Can't zap!!! 💀

Is WoSatoshi having issues?