Assuming the latest event is what's valid is how it's handled in nostr:nprofile1qqs2xugc5jyguqkj36rk0syv4tmnkjdtmtperttl7x9rqjy3ustdcvcpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsq3camnwvaz7tmjv4kxz7fwd46hg6tw09mkzmrvv46zucm0d5yx7efd. You could also set the "d" tag to something you can validate was created by your client and filter for only those wallet events.
I am working on adding nut-zap withdraws to npub.cash right now.
nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft I think I accidentally created two wallets, and now I got two 37375 events for my pk. Whats the best way to deal with this? Should senders just assume the newest wallet is the right one to send to?
Discussion
Thanks! I es thinking about the case where to wallet is not generated by the app itself, so it wouldn’t know the right “d” tag.
I think it would be good if those tags were chosen by the user and not completely random. In that case a UI could pop up a dialogue for the user to choose the correct wallet