In this episode of Tokenized Identity, Titus Capilnean, our VP of Go-To-Market, speaks with Jeremy Dillingham, Passport.xyz. They explore identity use cases and the required levels of verification, bot blocking, Sybils, and KYC requirements for protocols, tokens and contracts.

Jeremy is part of Passport.xyz, which was formerly Gitcoin Passport. Passport.xyz is focused on empowering digital, decentralized identity. Their mission is to help projects find and remove Sybils for various rewards of governance. Passport.xyz makes it as easy as possible for the end user to prove their own decentralized identity, so that they can be part of those projects, governance, get rewards from airdrops, etc. Civic Pass is integrated with Passport.xyz.

00:00 Welcome

01:14 Gitcoin DAO and Passport.xyz

04:48 What should builders need to keep in mind  from an identity and distribution standpoint as they plan an airdrop?

08:20 Eigenlayer’s point system to defend against Sybils

11:07 LayerZero’s Sybil self-reporting system

15:55 Gitcoin’s analysis of the recent zkSync airdrop

18:38 How can we help builders choose the best Sybil protection approach for their use case?

22:41 Should builders focus their verification efforts at the protocol, dApp, token, or contract level?

24:26 Adding friction vs making it an easy user experience

27:16 Best and worst identity verification experiences in your recent crypto journey

28:57 Permissioned smart contracts in a space that embraces a permissionless ethos 

32:00 If regulation isn’t coming anytime soon, how can we in the space self-regulate better?

35:47 Wrapping up

For more episodes, visit our playlist. While you’re there, don’t forget to like, subscribe and share Civic’s YouTube channel.