Very excited to finally announce:
[BOLT12 Pay is now available on the StartOS Community Marketplace ⚡]
The goal of the project is simple:
bring modern self-hosted Lightning payments to sovereign node infrastructure.
Features include:
- BOLT12 Offers
- Lightning Address / BIP353
- LNURL fallback
- self-hosted payment flows
- LNDK-powered offer support
Huge thanks to Matt Hill for helping make this possible 🧡
Support / follow the project:
https://geyser.fund/project/bolt12pay
I updated to the latest version available in StartOS, and I get this error when trying to create alias, offers, etc:
Fehler: ERROR: failed to connect tonic::transport::Error(Transport, ConnectError(ConnectError("tcp connect error", 127.0.0.1:7000, Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })))
Strange that update should prevent this error altogether. Try restarting Bolt12 Pay and if this does not help downgrade to version 0.2.108, not 0.2.108:1
I am pretty depressed right now as it seems when the LND package 0.21 beta will be released custom protocol will not work anymore and this leads to breaking my app completely until the upstream LNDK module project will come up with a fix
oh im so sorry, man that is a real bummer
The fix out and is confirmed working.
I made a modified LNDK module , so Bolt 12 Pay 0.2.109:1
will now work with the current LND 0.20.1 and also with the upcoming LND 0.21. that probably will be out this week.
That was a tough coding session. 😅
bravo!!
The fix for Bolt12 Pay working LND 0.21seems found, and I am doing some testing right now
Just double checked Can not reproduce the error my startos app is just working fine
downgrading seems to have fixed it 🤙
I think restart is enough no need to downgrade but will observe and investigate since I got the same error on my umbrel installation.
I am preparing an update for the app description and instructions now, informing that users should stay on LND 0.20.1 beta if they want to continue using this app and not update LND otherwise it will break BOLT12 Pay.
Maybe I can find a fix with Claude code, it says it is not trivial but perhaps doable...
Had the same error on umbrel after a restart of lnd and setting up new channels. After a restart of Bolt12 pay it was resolved for me
this is very cool. I just successfully added an offer for receiving mining rewards on Ocean. Now I wait to see if a payment is succesful, I suppose I would be one of the first receivers of mining rewards using LND. Is there is a reason for the channel needing to be private ? I can receive offers with CLN and LDK when using private nodes.
Sorry...i meant for the channel needing to be public, as I can receive to offers with CLN and LDK when using private channels.
A comment: I am making offers in the 'create alias' section, however I seem not not be able to make offers that have 'variable' or 'any' for the value in the offers (it always defaults to 1 even if i leave blank). This is via the start9 service.
but i was able to successfully make 1 sat payments to these offers that landed in my LND node,which is awesome!
the default is 1 sat minimum for offers to work but any amount will be able to receive afaik, also you can just leave the field of amount empty when creating a new offer, the default address created in setup should work out of the box without fixed amount, you can also create offers using the pay site...you dont have to make a payment web ui for each offer, just create is enough, channel can be private as well afaik, public gives better connectivity for routes onnly, if you use phoenix or phoenixd wallet for testing I would use a private channel to acinq node, to make scessful offer routing... a public channel would drain quickly.
hmm, i am testing with CLN and a coinos.io account. The offers I make in bolt12 pay with no value in the amount only allow me to send 1 sat (does not give the option to put an amount). This is posing a problem when trying to receive payouts from Ocean mining pool as it hits a validation error that wants the amount to not be 1 sat so it can send whatever is owed.
Good to know on the channel being private. Happy to provide more info and help fix just let me know !
Hey, I think I solved the amountless offer problem and made an update that solved the issue, if you want to test, I made an pr for umbrel and startos already. Would you be willing to test the app in advance with me,since I have no ocean mining, i could give you an amountless offer and you could try if ocean accepts it or I could give you the app s9pk for sideload testing on startos...otherwise just wait for the release, tested sucessfully with my phoenix wallet already....
id help, sure. I'm happy to sideload it on my start9, point me to the link 🤙
Yes interesting indeed, I will investigate...
Using phoenix wallet or another Bolt 12 pay instance payment with any amount was no problem. This might actually be a direct channel connectivity problem, since I had the same problem once with Phoenix until I had opened a channel to acinq , then the route was found easily and bigger amounts where possible...
So if possible try 1, 2 sats then 21, 210 and 1000 so on for testing. Try to make a channel to ocean if possible. I still have to try with cln but will have to set up that node first
Seems it just needed time! I tried my offer again and now any amount is being allowed to be paid to the offer. Woo hoo!
If you send me a bolt 12 offer in my nostr as a dm I could assist in testing debugging...npub1uhlrd6umajd0rxv36xsl2qkzz4xgmvy29m39mhn8aqrnz0g7x8rq2rnnh8
did you try the bip 353 default address?
i can't seem to get that to work, but been focused on just getting creation of an offer to work so I have one that I can pay any amount to. Will get there :)