Would you be willing to confirm your phone number with Warpcast via SMS (wouldn't be publicly visible):

1. Gave you an algo boost
2. You could see other users verified by Warpcast

If it was the only option, and there was no ZK wrapper etc, then I would likely refuse out of principle.

Is there an open source reference implementation of a zk wrapper?

How to zk wrap a centralized check with Sismo, v easy:

Wrapping app:
1 - Sign in w Sismo, using a stealth addr (native feature)
2 - After phone check, the addr is added to verified users
3 - Wait for anonymity set to build

Warpcaster
4 - Request & verify zk proof of inclusion in verified users

happy to chat @dwr.eth

customer support @supercast

trying to sound smart /doingnumbers

I'd say

short term:
- warpcaster host the wrapper app backend (doing the check)
- uses the zk proofs and store them in warpcaster

long term
- a specific KYC/trustful/neutral firm host the wrapper app
- zk proofs verified in hubs and badge/flags added to fid

can the proofs live inside hubs instead of warpcast db?