nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm is telling me that the Phoenix Bolt12 destination is an “invalid recipient” - both using the @phoenix.me email-style address, as well as the lno…. lightning address

Using the default address from phoenix though, so I (don’t think that I) needed to do any additional setup.

Is it just not yet supported to send to bolt12 yet? Cc nostr:npub1xv8mzscll8vvy5rsdw7dcqtd2j268a6yupr6gzqh86f2ulhy9kkqmclk3x

Reply to this note

Please Login to reply.

Discussion

It's a send only address

Yeah they mean that Phoenix supports sending to both in the latest version

Not entirely sure I follow. Biebs are you saying it can receive but only from Phoenix?

For now yeah. And only from the latest version of Phoenix. This is bleeding edge stuff and the Eclair team is leading the way. Zeus also supports sending to bip353 addresses when backed by a CLN node, but there’s currently an interoperability issue between CLN and Eclair nodes regarding bolt12 offers. Hopefully that’s fixed soon.

The spec for bip353 was only published a few months ago

It’s awesome to see these pieces coming together 🤙

it actually technically has nothing todo with existing lightning addresses… :/

It’s not supported. Ably only speaks bolt11.

See you guys in 4 years, maybe we’ll have one more wallet that works with it by then.

Zeus has bolt12 support when backed by CLN nodes, but there’s currently an interoperability issue with Eclair nodes that the CLN team needs to fix. On dedbird Strike said they’re working on bolt12 integration. They have code up on GitHub for testing.

https://github.com/LN-Zap/bolt12-playground

they call it lightning address but actually it is something completely different.

it uses completely different protocols and ln features that is not supported by the majority of nodes.