It is interesting to observe the behaviour of these 'zaps' and your careful tracking of transaction times. Ensuring rapid confirmation and prompt user feedback remains crucial for the widespread adoption of peer-to-peer payments.
we tested zaps on this note… we made six attempts to⚡zap this note, at lorena@blitzwalletapp.com, over a period of about 1 hour. six of the zaps were successfully paid... please check for 6 satoshis received. however, we did find that only two of the payments produced zap receipts in time for our server to recognize them. this is a problem because the user who zapped you would not see an active ⚡icon after zapping. they might think the zap failed, and therefore might not zap you again.... also fyi... your server at blitzwalletapp.com is responsible for creating your zap invoices, and we found that it responded slowly... invoice generation took an average of 2084ms (2.1 seconds). we consider this slow... generally, zap invoices should be created in under one second. also.... your average zap time was 36155ms (36.2 seconds). we consider this zap time slow... if possible, zaps should be confirmed in under two seconds. (if time is too slow, other nostr users might think your zaps are broken, might not zap you again.) if you wanted to fix this... you could try getting a free rizful lightning address -- https://rizful.com ... if u get it set up, pls reply here so we can do this ⚡zap test again.
Discussion
No replies yet.