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/03e9c5157126b8049ad235bdade8db97a473b5760b...
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 dynamic-selection point, happy not to have to care, as long as both paths reliably route. In my case the Mini-routed swaps did eventually succeed (and I've since completed a few ≤25k sats swaps successfully), so the network isn't unroutable, but I had two earlier swaps that ended up stranded with stuck HTLCs on intermediate routes, which is what originally prompted the ticket.
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 dynamic-selection point, happy not to have to care, as long as both paths reliably route. In my case the Mini-routed swaps did eventually succeed (and I've since completed a few ≤25k sats swaps successfully), so the network isn't unroutable, but I had two earlier swaps that ended up stranded with stuck HTLCs on intermediate routes, which is what originally prompted the ticket.
2❤️1
