Why is nostr:npub1m0ney2gz8r4przevwl6hmsr63m9ckcy3skllakl4mqemnc65pwfsv4dqkw focused on building a product based around a KYC-friendly geofenced custodial wallet?

What is the barrier to getting BOLT-12 finished and removing the web server obstacle to non-custodial static Lighting addresses? Is this something we’ll see before the end of the decade?

Honestly that question is something I ask others. I’m not involved with node implementation development (not the main ones at least) so I’m not sure.

If the market/network choose it, and users want those features and capabilities then absolutely we would support it.

Reply to this note

Please Login to reply.

Discussion

I feel like we’ve been hearing about this for several years but there doesn’t seem to be any announcements or progres being made. Who is working on it, and are there others available to help? Seems like a worthwhile effort to progress beyond LNURL.

We can actually make strides on the nostr side by requesting invoices over NWC 👀

This might even be better for decentralization than bolt12. In bolt12 you still need a way to hit a node for the invoice, which isnt always possible if the node is behind a firewall.

In the NWC case a node could listen for invoice requests using a relay as a proxy.

Oh that’s interesting 🤔

Is this something standardized somewhere?

I’ve suggested it a few times but haven’t got around to writing anything up if someone else wants to take a stab at it

Luckily NWC was updated to support any kind of command so it should be doable

Okay I need to dig more then. Dammit, too many things to dig more into :/

I know the feel 🥲