Damus
Ben Weeks ⚡ · 2d
Hi nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3uamnwvaz7tmwdaehgu3dwp6kytnhv4kxcmmjv3jhytnwv46z7qpqpsm37hke2pmxzdzraqe3cjmqs28dv77da74pdx8mtn5a0vegtlasaraze8 I'm integrating Boltz v2 reverse submari...
Boltz - Non-Custodial Bitcoin Bridge profile picture
Boltz Mini has a bunch of publicly announced channels and is decently well connected. You are the first to report an issue with it: https://amboss.space/node/03e9c5157126b8049ad235bdade8db97a473b5760b34781b8c870bd2ba34dbfcf8?section=Channels

It must be some limit you are applying locally to your routing that makes the payment fail. Anyhow let's continue debugging this in the support ticket you opened.

And regarding node selection: it's dynamic and we don't plan to expose this. The node we assign to a swap should always work for you and you shouldn't have to care which node. Let's figure out why you can't route to Boltz Mini.
1
Ben Weeks ⚡ · 2d
Wow - thanks for the swift response! x After more testing, I can confirm that reverse swaps (LN → on-chain) of 250,000 sats or less have their invoice issued by Boltz Mini (03e9c515...). At 250,001 sats and above, the invoice is issued by the main Boltz node (026165...). Understood on the dynam...