Hey nostr:nprofile1qqstxwlea9ah3u6kjjszu6a7lrnhqkfh8eptp2z6v0e9558tlkkl2rgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshszxnhwden5te0wfjkccte9ekkjmnfvf5hguewvdshx6p07xr4s5 - 97k outbound lightning payment pending for 4 days. 👀

Reply to this note

Please Login to reply.

Discussion

😬

LMAO

?

Are you paying a 97k invoice with the ecash in your minibits?

If so just redeem the ecash and then break it up into smaller LN payments to your LN wallet, that many sats could be too much for the minibits channels to handle in one request.

ecash mints are not LSPs, you can"t expect the same spending as Phoneix or some other provider

I was trying, yes.

I do think leading mints should be able to handle a 100k sat invoice. It was received fine with a similar amount.

what even is a leading mint?

Minibits is a wallet, and it kindly also hosts a mint which you can opt into connecting with. Just cause it is popular as a mint choice does not mean it has the infra to support hundreds of users using it like an LN wallet...

In future we might see mints that can give 'assurance' that your 100k LN payment will not bounce/have channel capacity. Minibits makes none of those assurances, you are projecting the LN usecase onto a ecash.

Not wanting to sound obnoxious but ecash does not fix all the things. LSP and liquidity provision is a problem with lightning that is being inherited.

Hey, please dm me the invoice / payment_hash. I'll check on the lightning node for the state of the payment.

Pending state is always a result of that intermediary or receiving node is not able to settle already initiated payment where the path was discovered and locked.

Cool. YHM.

Any luck?