Thanks! I think you'd need a label on the badge so that automated systems know what the badge actually means. That kind of makes the badge an indirect label anyway. I'll have to think about it though. I suppose it actually opens up using more novelty badges for verification though, like a "1 year club" badge for instance, which has some verification value but it's more of a novelty.

Since I've got your attention on the original post, too, do you have an opinion on how to handle "proof" metadata? (URL to a twitter post, proof of fidelity bond, etc?) Just add the relevant tags? For instance, for twitter verification it might be an 'r' tag, and for fidelity bonds the proof might be some new tag type?

Also, where do you discuss nostr dev typically, so I'm not just harassing you ;-) (although my question was BIP-32 related anyway)