Farcaster

if rainbow wanted to subsidize creation of farcaster accounts for users that have not created one yet, is it possible to leverage zkTLS to require users to have specific metrics on their twitter accounts in order to qualify for the subsidization? ie: only subsidize users whos twitter accounts were made before X date, or only subsidize users with more than X number of tweets

can zkTLS be utilized to more easily allow users to port their social graph from twitter to farcaster? ie like follow all the people on farcaster that you follow on twitter?

or is this what Warpcast's latest "Connect your X" experiment is meant to eventually solve for? are the Twitter accounts people connect to their profiles here exposed via API?

Neynar

twitter data is now part of user objects 

might be the first time there is this massive repository of wallet addresses <> twitter usernames 

🪐

yes, connected Twitter accounts that people connect on farcaster are available via API today and will be on the protocol soon.

yes, connected Twitter accounts that people connect on farcaster are available via API today and will be on the protocol soon.

https://warpcast.com/rish/0xff10f276

🪐 Building @neynar, join us in /neynar

There is a trust assumption on merkle though.

zktls would make it trust minimized

Working on building zkTLS infra/products. A ruthless empiricist and meme connoisseur.

http://opacity.network

can you elaborate how the set up where zkTLS minimizes trust would work?

> This enables a proof by committee to prove ownership of a web2 account, and Opacity’s framework expects users to generate ten identical proofs by different nodes in order to claim a web2 account.

What does this practically mean for a user? Do users have to go through Twitter OAuth 10 times, once each with an app for each node or do they need to publicly post some content on Twitter that each of the 10 nodes can independently verify?

https://medium.com/@vinayak_35433/opacity-network-trust-but-verify-eb819ebb0b0a