pull down to refresh

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!

reply

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.

reply

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 !

reply

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

reply

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!

reply

Glad to see you are now able to pay offers, for the fixed ammount: I investigated this further and it currently looks like a limitation/interop issue in the experimental LNDK/BOLT12 stack rather than an Ocean issue.

We confirmed that:

  • amountless offers can be created successfully
  • Phoenix correctly recognizes them as amountless
  • fixed-amount offers work instantly
  • but invoice requests for amountless offers currently time out when paying

So at the moment, truly amountless offers do not seem to work reliably yet with the current experimental LNDK/LND implementation.

For now the safest workaround is still using a small fixed amount (like 1 sat minimum), which is why BOLT12 Pay currently defaults to that behavior. ( thats why i hardcoded minimum 1 sat in my app)

I will keep investigating this and may open an upstream LNDK issue since the flow itself should theoretically be supported by the spec.

reply

I have further narrowed down the issue and found a partial solution to create truly amount less offers but still paying them fails, I opened a github issue for the LNDK repo (responsible for offer handling that I had forked and integrated into my app, hopefully they will also help resolving this issue.

reply

If you send me a bolt 12 offer in my nostr as a dm I could assist in testing debugging...npub1uhlrd6umajd0rxv36xsl2qkzz4xgmvy29m39mhn8aqrnz0g7x8rq2rnnh8

reply

let's do that. what client do you use ?

reply

i use amethyst but any nostr client will allow private messages, you just need to sign them

reply

i sent you a DM using yakihonne. Let me know if you didn't receive, ive had issues with yaki and Amethyst talking to each other.

did you try the bip 353 default address?

reply

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 :)

reply

you need a public domain set up for this to make it work

reply

I do have a public domain set up and working, although the DNS part was a little difficult for me to understand so possible i screwed that up.

reply

either use cloudflare or if you dont use cloudflare, set up a sub domain with the build in startos lets encrypt cert, them add a txt record (A) according to your setup as following the startos instructions