That’s a good take, I can see why you’d want to avoid polluting relays with events that would be muted anyway.
I don’t like making wallets even more complicated than they are though..
I think we want wallets that reject receipt from the mute list and not clients just hiding it for us
Discussion
the mute list is public and the address is set by the nostr profile, I don’t think anything from the receiver would need to be done differently for the zap implementation of the receiving wallet to respect the mute list