🚨 New Failed Swap at 2025-01-07 11:18:33

āŒ https://mint.bitcointxoko.com -> https://mint2.nutmix.cash Mint Error: Lightning payment failed: HTTP status: . (Code: 20000)

Last 10 swaps involving https://mint.bitcointxoko.com (Success rate 4/10):

āŒ https://mint.bitcointxoko.com -> https://mint2.nutmix.cash at 2025-01-07 11:18:33 Mint Error: Lightning payment failed: HTTP status: . (Code: 20000)

āœ… https://mint.belgianbitcoinembassy.org -> https://mint.bitcointxoko.com at 2025-01-07 07:50:39

āœ… https://mint.bitcointxoko.com -> https://mint.lnw.cash at 2025-01-07 05:06:11

āœ… https://mint.bitcointxoko.com -> https://8333.space:3338 at 2025-01-07 03:52:54

āŒ https://mint.bitcointxoko.com -> http://lbutlh5lfggq5r7xpiwhrajdl7sxpupgagazxl65w4c5cg72wtofasad.onion:3338 at 2025-01-06 23:27:17 Mint Error: Lightning payment failed: HTTP status: . (Code: 20000)

āŒ https://mint.bitcointxoko.com -> https://mint.mountainlake.io at 2025-01-06 20:03:50 Mint Error: Lightning payment failed: HTTP status: . (Code: 20000)

āŒ https://mint.bitcointxoko.com -> https://antifiat.cash at 2025-01-06 17:49:05 Mint Error: Lightning payment failed: HTTP status: . (Code: 20000)

āŒ https://mint.bitcointxoko.com -> https://mint.pailakapo.com at 2025-01-06 13:39:58 Mint Error: Lightning payment failed: HTTP status: . (Code: 20000)

āŒ https://mint.bitcointxoko.com -> https://mint.pailakapo.com at 2025-01-06 05:16:49 Mint Error: Lightning payment failed: HTTP status: . (Code: 20000)

āœ… https://mint.macadamia.cash -> https://mint.bitcointxoko.com at 2025-01-06 03:24:42

Last 10 swaps involving https://mint2.nutmix.cash (Success rate 9/10):

āŒ https://mint.bitcointxoko.com -> https://mint2.nutmix.cash at 2025-01-07 11:18:33 Mint Error: Lightning payment failed: HTTP status: . (Code: 20000)

āœ… https://mint2.nutmix.cash -> https://cashu.boats at 2025-01-07 09:32:18

āœ… https://mint.coinos.io -> https://mint2.nutmix.cash at 2025-01-07 09:17:37

āœ… https://mint2.nutmix.cash -> https://mint.lnw.cash at 2025-01-07 06:07:58

āœ… https://mint2.nutmix.cash -> https://mint.lnw.cash at 2025-01-07 04:10:56

āœ… https://cashu.21m.lol -> https://mint2.nutmix.cash at 2025-01-07 02:44:10

āœ… https://stablenut.umint.cash -> https://mint2.nutmix.cash at 2025-01-06 23:15:05

āœ… https://mint2.nutmix.cash -> https://mint.lnvoltz.com at 2025-01-06 20:42:46

āœ… https://mint.westernbtc.com -> https://mint2.nutmix.cash at 2025-01-06 14:01:10

āœ… https://8333.space:3338 -> https://mint2.nutmix.cash at 2025-01-06 12:49:16

Could failing because the swap amounts are too small to find a route with reasonable fees. We reserve only 1% for routing fees and the small payments <50 sats are paying >2% fees assuming >1 sat fees.

I manually tested with 1000 sat mint/melts with those mints that failed and works flawlessly. nostr:nprofile1qqs9pk20ctv9srrg9vr354p03v0rrgsqkpggh2u45va77zz4mu5p6ccpzemhxue69uhk2er9dchxummnw3ezumrpdejz7qgkwaehxw309a5xjum59ehx7um5wghxcctwvshszrnhwden5te0dehhxtnvdakz7qrxnfk

Reply to this note

Please Login to reply.

Discussion

This sounds reasonable to me.

Would it be helpful to include the swap amount when a swap fails?

Another thing that could be done is to open channels to the other mints so there are no routing fees, although it requires some extra capital.

I don't think this is a reasonable expectation especially if we account for new mints coming online in the future

It could work if mint operators agreed to team up and open zero fee routing channels between each other. If each mint had at least 2 such channels to other mints, all routing between mints would be free.

Added bonus is that channel rebalancing between mints would be free too.

I’m in for this. Where do we connect to negotiate the channels?

Some mint runners list their contact details which you can find from the auditor

https://api.audit.8333.space/mints/

Yes I think that would be helpful. Either that or raise the default swap amount?

I'll include it in the bot reporting but calle controls the actual audit.

Amounts are now included

Amounts are determined randomly and depend on both the sender and receiver wallet balances.

How are the fees set, do you do anything custom in nutshell?

Not in nutshell, we are using a LNbits wallet for Lightning and limiting fee reserves from within LNbits

Shouldn't it be the other way round? The smaller the amount, the higher the chance for success. Do you see any helpful error messages in the logs? I'd like to fix this.

Nope, not the other way around. 1 sat base fee is 2% of 50 sats but 0.1% of 1000 sats. Most noderunners wouldn't want to route dust for nothing.

We are limiting fee reserves to 1%, so payments of over 100 sats with 1 sat base fees route fine

It's not really a problem. Just don't want to look like we are rugging because we are opinionated in how we run our node haha