Can anyone help?
#zaps
#bitcoineducation🎓
GM ☕
Can anyone explain why I would get zapped to my old LN address with nostr:npub1hcwcj72tlyk7thtyc8nq763vwrq5p2avnyeyrrlwxrzuvdl7j3usj4h9rq , instead of my new LN address with nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm ?
21 sats were sent to my old LN address recently and I can't figure out how or why .. I changed my LN address around 3 weeks ago .. is it something to do with Nostr clients, relays, updates, or something else?
🤙🏼
#nostr
#bitcoin
#lightning
#corn🌽
Discussion
🤔 When I visit a profile the first post to load is rarely the most recent... wallet addresses not being up to date definitely seems like a bigger issue tho & worth some attention. nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s
It just means that the users' new information isn't widespread and some relays are still on the old one. If the app receives the old info and say the new relay is moving slowly, users trying to zap will send to the old wallet.
Yeah, that makes sense, but I wonder if there is some way for clients to check multiple relays for certain info (or maybe they already do...?) and then alert out if sync relays to the discrepancy?