Avatar
Tim Bouma
06b7819d7f1c7f5472118266ed7bca8785dceae09e36ea3a4af665c6d1d8327c
| Independent Self | Pug Lover | Published Author | #SovEng Alum | #Cashu OG | #OpenSats Grantee x 2| #Nosfabrica Prize Winner

I’ll settle for the lesser ideal - cheaper booze. Still adjusting to the land of high-priced monopoly wine, after returning from Madeira.

The most important debate to be settled is whether it’s “nostr” or “the nostr”

The most important debate to be settled is whether it’s: NOSTR, Nostr or nostr.

I’m sure we can find a glamorous clock and protocol expert on X.

It would also be very easy for a Lightning wallet to detect that an npub is entered and turn that into a corresponding lightning address so the npub can receive a payment. nostr:note1ymgykwl6cmyd5xxgzue200z5ukdhn98cg6v0rangtveffpt0l3ns8htmus

I was going to add CASHU, but it’s not an acronym.

Fixed it: Chaumian Asset Solely Held by U.

BTC/LN/NOSTR/CASHU

Not yet. Soon.

My motivation was to see how straightforward it was to implement. The following could be added to a NIP:

“The service may recognize the local part of a lightning address as a valid npub.

If the local part is a valid npub, accept payment on behalf of npub, convert amount to Cashu token, send Cashu token to npub using encrypted DM (NIP-04)”

This is what it looks on my side, after redeeming from the DM

Every npub now has an Lightning Address.

Send any amount to:

@openbalance.app and a Cashu token of corresponding amount is immediately by DM to the npub holder, which they can redeem (super slick in Amethyst, as it redeems to your profile address)

For example, sending funds to nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424 would use this Lightning Address:

nostr:npub1mhcr4j594hsrnen594d7700n2t03n8gdx83zhxzculk6sh9nhwlq7uc226@openbalance.app

Back in the ‘hood.

The base layer of trust is computation.