Avatar
Chris
e3f652671f86e30a0f14ee58c769b6cef411c25d8f0ba6485993e6cb74834bc0

Love all the talk of future Coldcard features in this episode, but the one I want the most is still missing from the list. The ability to export a secure note which has been encrypted with deterministic entropy so it can be decrypted on any Coldcard with the same seed & passphrase. This would be huge for inheritance planning.

https://fountain.fm/episode/9TpAKbyGusTkGm6PEmZo

nostr:nevent1qvzqqqpxquqzq36d5sxprr39urnytwyg6vas9k0qkagefv5d6ktrq5p2sk089hhrxpwtqc

Replying to Avatar Emre Yılmaz

I was using [Wallet of Satoshi](https://www.walletofsatoshi.com/) at first, but then I realized it does not support [NWC](https://nwc.dev/), so I found [Alby](https://getalby.com/). It’s great, but I didn’t want to make that many payments (I’m a developer but a newbie in [Nostr](https://nostr.com), more of an explorer).

Thanks to Alby, they have an open-source [AlbyHub](https://github.com/getAlby/hub). I had a Raspberry Pi 3, so I updated it and installed AlbyHub, then connected my wallet to my Alby account.

Still, I didn’t like depending on other domains. Alby gave me the address `fallingwhimsy946296@getalby.com`—ugly, right? So I started researching how to have a custom [LN Address](https://lightningaddress.com/). Alby offers this if you buy their cloud hub, but as I mentioned, I didn’t want to spend money for this exploration.

After reading some Lightning Network documentation, I realized that LN supports [well-known URLs](https://docs.lightspark.com/lightspark-sdk/lnurls).

I then accessed Alby’s well-known URL for my account: `https://getalby.com/.well-known/lnurlp/delirehberi` and got the correct configurations for the callback setting and updated identifier.

Next, I created a `.well-known/lnurlp/delirehberi` file under the `static` folder of my Hugo blog. I’m using GitHub Pages to serve my blog. This led to two problems:

1. GitHub Pages does not set correct headers for files without an extension. I tried to solve this using a Cloudflare Worker as middleware to add the `application/json` header.

2. My Cloudflare-GitHub setup was corrupted, affecting the proxy configuration for my root domain.

After some research, I realized the exact SSL configuration matters when using Cloudflare with GitHub Pages:

- Use **Full SSL** on Cloudflare and enable **Force HTTPS** in GitHub Pages.

- Or use **Flexible SSL** on Cloudflare and disable **Force HTTPS** in GitHub Pages.

After making these updates, I enabled proxy configuration for my root domain and added the worker route for my Worker.

Finally, it worked like a charm: [https://emre.xyz/.well-known/lnurlp/delirehberi](https://emre.xyz/.well-known/lnurlp/delirehberi)

So it’s still relying on getalby.com to connect to your node and create an invoice, but this achieves you getting to pick your own lightning address (using your own domain), correct?

Seeing “ask host to claim their podcast to enable payments” on fountain. So no boosts from here either

https://fountain.fm/live/82scdqfEi0P9SIy9bso4

Listening on fountain with no video. Tried listening on truefans. Had no balance and when I tried to send funds to my @truefans.fm lightning address, the .well-known gives a 404 error. Maybe next time

https://fountain.fm/live/82scdqfEi0P9SIy9bso4

It was every service and every country giving that message (tried a bunch to check), but it appears to be working again now; so all good!

nostr:nprofile1qqsqdh0ftupx3njqz29lw09xap2k0wzkw6yw55hjfhx4wd8803g09kgpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3samnwvaz7tmxd9shg6npvchxummnw3erztnrdaksl33zem when trying to pay for a phone number, I get “error creating order” regardless of which service or country I chose. Is there a known outage currently? Has been like this for at least 8 hours (unsure how long as I haven’t used the service for a few weeks prior).

Thanks for thinking through encrypted note export with the team. The ability to use a different BIP-39 passphrase for your note-decrypting wallet vs. your main wallet, but still use the same SeedXOR backups, would be very useful.

https://fountain.fm/episode/qmlyHPliebjOxUvkQnxN

nostr:nevent1qvzqqqpxquqzqnpzaty3k905jqqklfw7egf8ea5y2rjezlee2puxtck4a977lt0flsezhs

In response to SaltyCrayon’s boost, a reminder that if a Podcasting app were to add NWC, you’d be able to connect to at least 15 different wallets, some custodial, some non custodial, plenty that adhere to KISS. You don’t need to interact with Nostr to connect a wallet via NWC. The solution exists.

https://fountain.fm/episode/dAklXcejH5WaStLZBVIE

nostr:nevent1qvzqqqpxquqzqs296ck49p3rh73fyc9wdc4w8xf3tqmjcpxcazxsjgdpzk0asw7npcvqdp

Would still love the ability to export a Secure Note encrypted with bip85 entropy that can be decrypted at any point in the future by a coldcard running the same seed/passphrase combo. A stacker news poll showed over 50% of users would be interested in this feature https://stacker.news/items/853095

https://fountain.fm/episode/Dsu7Q60FZgZWJ99ukodd

nostr:nevent1qvzqqqpxquqzqth5jguzq8qytfpmm4mrefvum4lj6wkm9wekjhs7ehvx5vtmtm8enc637u

New Podcasting 2.0 episode dropped. Testing out Fountain’s new Nostr integration to see if this comment automatically shows up in the fountain app (and maybe other Podcasting 2.0 apps soon) https://fountain.fm/episode/1k8u7PsBU1lXMxT4mMR8

Shame. Thanks for the update. nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm is there any known working extension/browser combo on iOS currently?

Replying to Avatar Keychat

The biggest difference is that Keychat's one-on-one chats have forward secrecy, meaning that if your key file is compromised, hackers cannot decrypt your past or future messages. In contrast, 0xchat's default message encryption (Gift-Wrapped DM) does not have forward secrecy.

“0xchat Secure DM

Currently, we support three types of direct messages (DMs), Please review the provided links for a deeper understanding of each DM type:

NIP-04 DM

NIP-04 DM is the most widely used DM type in nostr, but it is not our recommended option currently because NIP-04 is not private in terms of DMs. Even though the content is encrypted, it leaks a lot of metadata. We do not use this DM type by default but are compatible with NIP-04 DM from other nostr clients.

Gift-Wrapped DM

Gift-Wrapped DM is our default and recommended DM type. By using Gift-Wrapped for event messages, it minimizes metadata leakage. Not only is the message content encrypted, but the sender and the timestamp are also concealed. Moreover, the encryption algorithm employed is the latest audited NIP-44 algorithm.

Secret DM

Secret Chat is our third DM type, an extension of the Gift-Wrapped DM. Since Gift-Wrapped DM does not support forward secrecy, if a user's private key is compromised, all DM messages could be recovered. Therefore, we added a NIP-101 key exchange protocol to ensure each message session uses a different receiver key, securing forward secrecy. Additionally, we have incorporated the option to select a fixed relay for these sessions, allowing messages to be transmitted through a single trusted relay for both parties.”

https://github.com/0xchat-app

Thanks!

Is there a brief summary of what the fees will be for the paid plan? What’s the fee on top of the actual on chain fee for channel opening? Is the fee for initial channel opening the same for future just in time liquidity channel openings? Fee for outgoing lightning transactions, fee for incoming lightning transactions? Any other recurring fees? Thanks!

What if some of the 1BTC was used as smaller bounties for other Nostr clients to implement NIP-17? The more adoption the better. Is this on the roadmap for nostr:npub1n0stur7q092gyverzc2wfc00e8egkrdnnqq3alhv7p072u89m5es5mk6h0?

On top of that, every few episodes they complain how reliant the whole value for value system is on Alby, but they also get triggered by NWC which would allow podcasting 2.0 apps to easily connect to other wallets.

Also, the list of podcast players gets sorted by the number listens in each player for that episode (if the data has been shared with https://op3.dev). Thought that was a nice touch as well.

nostr:npub1uq70uqgas9pyhds2zt57kr9se8rg3s68ztphjnq82ts8rzeknmeql7u0c2 Bravo support would be awesome. Not sure if each federation would need to support it, or if it could be implemented at the app level and then just the lightning invoices get passed along to the federation(s).