pull down to refresh

Context:

  1. I don't use SN that much, and honestly, I never zap much generously, either; however, when I have accumulated reward sats or CCs, I have no qualms about zapping less stingily than I usually do.
  2. I had Alby Hub linked for a while, and it went offline recently; I hadn't bothered fixing it because, again, I wasn't using the site actively enough to care, and getting set up on this site was the main reason I had even bothered setting it up.
  3. A few days ago I got a bunch of generous zaps, and began a cowboy streak.
  4. Yesterday I didn't even log in to the site.
  5. When I logged in today, I still had my cowboy hat, so I began commenting and zapping in the hope of keeping it.
  6. I tried a zap larger than my usual dusty amounts, because I have thousands of CCs now, and indeed it failed an NWC request to Alby, so I tried paying the invoice which had an expiration time of six minutes, although the payment was marked as failed within about two minutes, before I had even opened my mobile wallet.
  7. Realized I should disable the NWC Alby connection, and was disappointed to get the notification of losing the cowboy hat immediately after clicking to disable it.

Was that just a weird coincidence?

Also, after disabling the NWC, I could zap a larger amount entirely from the accumulated CCs... and my cowboy hat is still there! Yet the streak is listed as "1 day", and there is not any notice of getting a new one, after the notification of losing the previous one.

What gives?


nevermind I'm an idiot, the notification was about losing the gun, not the hat

obligatory "SN is too complicated, it'll never catch on" because I mean look at the failure of Bitcoin, right?


anyway, the unintuitive thing described in step 6, where the invoice time of six minutes was a lie and the invoice got closed early, is an actual complaint, worth at least consciously dismissing as my misunderstanding of SN's new wallet implementation.

36 sats \ 2 replies \ @k00b 28 Jul

If you saw this fast "expiring" invoice in a qr that popped up, that's a bug. If you saw this fast "expiring" invoice by visiting satistics and clicking on a pending transaction, that's expected:

Once a wallet has reported failing to pay an invoice, we cancel that invoice before generating a new one. We do this because for all we know the wallet's payment is still in flight because the wallet may have a bug that reported failure incorrectly (MUCH more common than it should be); and, paying a bolt11 invoice multiple times can lead to a routing node stealing funds (if it was on a route for a prior successful payment and has the preimage).

reply

thanks for weighing in;

what developers of a system expect is often different from what users do, and if that mismatch is too large, I'd still call it a UX-level bug, even if it's not a failure of any particular "contract" within the design of the code.

reply

fair. we shouldn’t show the QR on the transactions page when a wallet has attempted payment

reply
because I have thousands of CCs now

#1329607

reply