Individual post zapping :: There is currently no reason to zap an individual post since nothing post-specific unlocks as a result of the zap. Funds all going in the same wallet anyway so why is this feature even necessary? I’ll tell you why: 1. Primal wants paid content in future—ie Zap to unlock. 2. Primal wants metrics on posts that lead to zaps. Primal can get around 2 with timestamping metrics and zap correlation. So, I’m suspecting this is all about 1 above. — Strike’s hidden KYC submission: No, not “ask Strike”. It’s up to the front end to be transparent about instigating the KYC API, not the backend. — Primal locks posts: You say posts need to be locked because posts can be zapped. No. Posting is independent from zapping, if I haven’t added a wallet, users can’t zap me anyway. Simply remove the zap button for users without wallets. I suspect posting is locked in order to incentivise users to add this KYC’d Strike wallet. — Strike not disclosed clearly :: Agreed — Other wallet options not present :: I don’t know any. What I do know is that optionality is freedom. Sacrificing freedom on a freedom focused NOSTR front-end is not congruent, hiding that provider (see above, makes it even worse. Primal could also implement both Damus’s approach and their current approach concurrently. ie, select another wallet provider, and sorry, you can’t zap posts. — Damus’ approach :: at the top of this post. — ** next post is what I suspect is going on in summary…