you mean to which pubkey senders should nutzap p2pk-lock? they should look at the 10019 kind's p2pk; senders shouldn't even try to look at the 37375 events.
There can only be one 10019 (since 10k <= x < 20k kinds are not param-replaceable)
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
Sorry, I said nut zap but I meant nip-60.
So basically when my app wants to use a logged in users Cashu wallet, but it discovers multiple kind 37375 wallets