pull down to refresh
105 sats \ 9 replies \ @OT 28 Apr \ on: BOLT12 Suggestions? lightning
I think coinos is probably the easiest at the moment. Phoenix has bolt12 but there's something that doesn't match up and so won't work at the moment (I think it was the description).
Best if you run your own Core LN node, but that might be a big commitment for a small payout.
Does Coinos support the signing of configuration messages? I couldn't find that there...
Yeah, I think I'm going to go the Core LN node route. I'm running a Lightning Node on my Umbrel right now, but from what I see, I'd need to run a Core LN node. I have a commitment to keep my channels open until late May, and to your point, yeah, it would be a big commitment on many levels to switch over right now. I'm kind of fine making a tradeoff for something a little more turnkey, in the mold of Coinos or Alby, just to get things going for now until May when I'll have more options available.
reply
Yes visit coinos.io/sign to get a legacy address you can sign with
reply
reply
So if I understand correctly:
-- Get Bolt12 Offer from Coinos
-- Sign in Sparrow or Electrum (I have to study how that works, and I might be mis understanding that)
-- Take output and paste into OCEAN
Thanks for your help!
reply
Probably best to simply follow their instructions and click on the wallet that you'll use:
I used Sparrow to sign an address. For bolt12 Coinos worked for me so it should for you too.
reply
Yeah, I've read the docs, but it doesn't seem like using a BOLT12 offer from Coinos and then signing with Sparrow is working.
reply
It shouldn't be an issue, I'm pretty sure others have had success doing that.
For what I know, the issue is that you are trying to place a BOLT12 invoice that is generated by a different wallet (coinos in this case). You'll be maybe able to sign the message anyhow, but for OCEAN will be a mismatch because the BOLT12 invoice should be signed with the same wallet that generated the btc1 address used as mining username.
reply
Yup, that's pretty much what I'm seeing now. Thanks for confirming!
reply