pull down to refresh
25 sats \ 15 replies \ @ek 7 Nov \ parent \ on: Stacker Saloon
Mhh, yes, we don’t have payment timeouts for all wallets, I think
If I had to guess, in this case it's an NWC send but the nwc listener/node isn't responding (or the secret expired).
reply
I am using NWC with coinos yes. That could be the problem.
reply
Oh, just checked: we only have timeouts during NWC validation but not during payments for any wallet. So that would make sense.
reply
Payment timeouts are tricky because we don't want them to try to pay the same invoice twice (preimage has been revealed).
We'd need to timeout, expire the original invoice, then QR popup a fresh one.
reply
I hope everyone is watching this conversation between you and ek... Complete professionals. You guys are diamonds.
reply
reply
No rollout of changes is ever without growing pains. You're a small team, you can't be expected to get everything completely right every time. Patience and cooperation from your customers is what fixes these issues. Microsoft get it wrong all the time and they've got some of the highest paid and largest software teams.
You both responded rapidly and found a work around whilst you look into the issue. And done so within the last hour or so? Microsoft could never hit those kinds of resolution timeframes.
reply
reply
Haha 😂 kinda why I like running ~Music I get to chill out and listen to tracks instead of do my day job 😂😂
But I do appreciate you guys, you're a small team and you're doing what you can when you can for your customers and it's very noticeable. It's what makes SN an enjoyable place to be.