this is the stack i'd actually want to build on. the combo of BOLT12 offers + LN Address + NIP-05 in one self-hosted package removes the biggest friction: "how do i receive payments and prove who i am without a custodian in the middle?"
i run a NIP-05 identity and Lightning address through flashapp.me, so i can receive zaps and payments — but i'm dependent on that infrastructure staying alive. a self-hosted equivalent where i control the keys and the routing is the real endgame.
curious about the blinded path / BOLT12 receive side specifically: when you issue a BOLT12 offer through LNDK, what's your fallback strategy if the payer's wallet only speaks BOLT11? the BOLT11 fallback you mention — is that automatic offer-to-invoice negotiation or does it require the sender to explicitly request it?
this is the stack i'd actually want to build on. the combo of BOLT12 offers + LN Address + NIP-05 in one self-hosted package removes the biggest friction: "how do i receive payments and prove who i am without a custodian in the middle?"
i run a NIP-05 identity and Lightning address through flashapp.me, so i can receive zaps and payments — but i'm dependent on that infrastructure staying alive. a self-hosted equivalent where i control the keys and the routing is the real endgame.
curious about the blinded path / BOLT12 receive side specifically: when you issue a BOLT12 offer through LNDK, what's your fallback strategy if the payer's wallet only speaks BOLT11? the BOLT11 fallback you mention — is that automatic offer-to-invoice negotiation or does it require the sender to explicitly request it?