My name is Blue!
Sats cost: 2.415
Remaining balance: 207.585 sats
Hey, can you create an issue for Routstr core for this problem:
• This exact token is the one that hit the 500.
It’s a 404 sat token from https://mint.mountainlake.io
, and the topup attempt is in logs/app_2026-03-14.log:53634 with request ID ef2c0cc1-0484-4165-a3d7-4298348a9b60.
What happened:
logs/app_2026-03-14.log:53636: redemption started
logs/app_2026-03-14.log:53637: swap_to_primary_mint started for amount: 404 sat
logs/app_2026-03-14.log:53642: failure was could not pay invoice: Mint Error: not enough inputs provided for melt. Provided: 404, needed: 412 (Code: 11000)
logs/app_2026-03-14.log:53643: app returned 500 Internal server error
So the 500 was not a generic crash. It was a fee-handling bug in the foreign-mint swap path: the app tried to melt a 404 sat Mountainlake token into the primary mint, but the melt needed 412 sats including fees, so the claim failed.
Separately, I checked the mint live just now and all 5 proofs in this token are currently SPENT. So:
the claim attempt here failed because of insufficient melt inputs
the token is now spent at the mint and is no longer claimable
That combination suggests the token was spent elsewhere later, or the mint/wallet flow marked it spent after the failed swap attempt. The logs here do not show a later successful claim for this exact token.
Here’s another example:
That request ID is the same bug class, just with a different Mountainlake token.
In logs/app_2026-03-14.log:55015, request c8bb32e1-0486-4b5b-b5cd-621b57735274 is POST /v1/balance/topup. The relevant lines are:
logs/app_2026-03-14.log:55017: credit_balance: Starting token redemption
logs/app_2026-03-14.log:55018: swap_to_primary_mint for https://mint.mountainlake.io
, amount: 4200 sat
logs/app_2026-03-14.log:55019: failure is could not pay invoice: Mint Error: not enough inputs provided for melt. Provided: 4200, needed: 4284 (Code: 11000)
logs/app_2026-03-14.log:55020: app returns 500 with Internal server error
So yes, this verifies the same bug:
foreign-mint token
swap-to-primary path
melt quote requires more sats than the token amount because of fees
exception is surfaced as a 500 instead of a handled user-facing error
The smaller 404 sat request and this 4200 sat request fail for the same reason. The only difference is the fee gap:
404 -> needed 412
4200 -> needed 4284
This is enough to confirm the bug is reproducible and not token-specific.
• This exact token is the one that hit the 500.
It’s a 404 sat token from https://mint.mountainlake.io
, and the topup attempt is in logs/app_2026-03-14.log:53634 with request ID ef2c0cc1-0484-4165-a3d7-4298348a9b60.
What happened:
logs/app_2026-03-14.log:53636: redemption started
logs/app_2026-03-14.log:53637: swap_to_primary_mint started for amount: 404 sat
logs/app_2026-03-14.log:53642: failure was could not pay invoice: Mint Error: not enough inputs provided for melt. Provided: 404, needed: 412 (Code: 11000)
logs/app_2026-03-14.log:53643: app returned 500 Internal server error
So the 500 was not a generic crash. It was a fee-handling bug in the foreign-mint swap path: the app tried to melt a 404 sat Mountainlake token into the primary mint, but the melt needed 412 sats including fees, so the claim failed.
Separately, I checked the mint live just now and all 5 proofs in this token are currently SPENT. So:
the claim attempt here failed because of insufficient melt inputs
the token is now spent at the mint and is no longer claimable
That combination suggests the token was spent elsewhere later, or the mint/wallet flow marked it spent after the failed swap attempt. The logs here do not show a later successful claim for this exact token.
Here’s another example:
That request ID is the same bug class, just with a different Mountainlake token.
In logs/app_2026-03-14.log:55015, request c8bb32e1-0486-4b5b-b5cd-621b57735274 is POST /v1/balance/topup. The relevant lines are:
logs/app_2026-03-14.log:55017: credit_balance: Starting token redemption
logs/app_2026-03-14.log:55018: swap_to_primary_mint for https://mint.mountainlake.io
, amount: 4200 sat
logs/app_2026-03-14.log:55019: failure is could not pay invoice: Mint Error: not enough inputs provided for melt. Provided: 4200, needed: 4284 (Code: 11000)
logs/app_2026-03-14.log:55020: app returns 500 with Internal server error
So yes, this verifies the same bug:
foreign-mint token
swap-to-primary path
melt quote requires more sats than the token amount because of fees
exception is surfaced as a 500 instead of a handled user-facing error
The smaller 404 sat request and this 4200 sat request fail for the same reason. The only difference is the fee gap:
404 -> needed 412
4200 -> needed 4284
This is enough to confirm the bug is reproducible and not token-specific.
1🤖1