pull down to refresh

**Bolt12 Pay 0.3.0

**.

The project is now available in both the official Umbrel App Store and the Start9 Community Marketplace.

Major additions include:

  • ⚡ Transaction History with automatic synchronization from LND
  • Payment classification (BOLT12, Lightning Address, LNURL, NWC, Keysend, Zaps and BOLT11)
  • Native Onion Messaging support for LND 0.21 while remaining compatible with LND 0.20
  • Improved Nostr Wallet Connect integration
  • Numerous UX improvements and bug fixes

The new Lightning Activity view automatically keeps track of incoming and outgoing payments while preserving metadata that normally isn't available directly from LND.

This has been a fairly large release and required a lot of testing across Umbrel, StartOS and both LND 0.20 and 0.21.

I'd love to hear feedback from people running self-hosted Lightning nodes.

Project update with screenshots:

https://geyser.fund/project/bolt12pay/posts/view/5965


@Alex71btc Hey, tinkering with the latest version of bolt12 available in Start9 (0.2.116:1). The first offer I made works just fine (can send to it no problem). Then, the subsequent offers I make are about twice as long in character length, and none of them seem to work when trying to send to them (seems coinos or my CLN node timeout due to the length of the offer perhaps?). Why does that happen, the offer length suddenly becoming so long?

reply

Hey, that should not happen, will check.
Sometimes offer strings are longer when adding a lot of text in the description and has a fixed amount. But latest version should be 0.3.0:6, not 0.2.116.

There was a huge start os update today with new versions of basically all apps, did you get that one?

reply

Hey,

After seeing your comment,I updated to the latest start OS version, and thus I also updated to the latest bolt12 version: 0.3.0:6.

The problem persisted. I tried to make a new offer with no description in it, and still the offers created are too long and seem to be rejected by coinos / my cln node as too long.

reply

I will investigate further, just am very busy otherwise atm.
But yesterday we at least made a fix for the DNS resolve for Bip 353 Lightning addresses and regular lnurl lightning addresses.
That's up now and working again with lnd 0.21.1
Will get back as soon I found out about your issue...

Also please open a github issue here:

https://github.com/Start9-Community/bolt12-pay-startos

and describe the bug, we have an AI assisted, very capable dev account for StartOS now, who solves bugs with ease ( helix-nine) .It could very well be that he/it quickly finds the root cause ...!

reply

OK, will do!

reply

Will investigate and get back.
Also they seem to have broken the latest version in general, since lighting address resolve or DNS resolving times out in general.... there was another update by the start os team, they implemented and didn't get back to me for testing...that changed the port behaviour, so the app is broken for now.
Usually they will fix things quickly though, i will keep you updated.
Th umbrel app still works normal

reply

Hey unfortunately after testing on StartOS (Offer strings still work with 0.3.0:6 , LND 0.21.1, just lighting address is broken), I could not reproduce the issue! Creating all sorts of offers and paying them works just fine , no matter if it are amountless offers, a certain amount, no desciption or long description. Also creating multiple new offers, did not alter funktionality.

Offer strings appear to have the normal lenght to me.

Which LND instance are you on? LND 0.20.1 still or lower?
Did you already update to LND 0.21 ?

On Umbrel also no offer payment failure at all, neither receiving or sending. So my first guess would be still a channel liquidity or balance issue or a node connectivity issue. Are you tor only? Did you implement any protocol changes in LND.conf?

reply

I am running LND version 0.21.1-beta:8 on Start9. I've got 3 channels i bought from LSPs, not tor only and I haven't made any changes to LND.conf.

What's odd to me is that the first offer I made works just fine, but its subsequent ones that are longer (similar to the screenshot you sent above) and do not work (perhaps the length is not important). And the first offer that I made had the longest description of the offers I made.

reply