Podcast Transcript

Verifiable Credentials: Who Should You Trust?

Ankur Banerjee CTO and co-founder, cheqd (at recording)

A valid signature does not establish that a credential’s claims are true. In this interview, published in August 2023, cheqd co-founder Ankur Banerjee explains why verifiers need trusted issuers, why personal details belong offchain, and how social reputation can travel between communities. He describes Creds.xyz wallet backups and asynchronous sharing, then explores identity beyond passports and KYC. Product descriptions and plans reflect the recording period.

  • Published 23 Aug 2023
  • Runtime 27:38
  • Operator
  • Recorded in English
Verifiable Credentials: Who Should You Trust?: podcast episode with Ankur Banerjee, CTO and co-founder, cheqd (at recording)
// The short version
  • At 03:05, Banerjee explains the privacy cost of public NFT reputation. Once a wallet address is linked to a person, its public holdings become linkable too. He describes keeping personal credential details in offchain wallets and using public verification material. The W3C DID privacy guidance also warns against personal data in public DID documents.
  • At 08:13, Banerjee distinguishes a genuine issuer’s credential from a self-written claim. Trusted issuer lists address who is credible for a particular claim. The W3C Verifiable Credentials trust model makes verifier trust a separate decision; a verifiable signature does not establish truth.
  • At 11:37, he describes a browser wallet with end-to-end encrypted backups decrypted on the user’s device. He also describes time-limited links and snapshots for people in different time zones. These product descriptions reflect the recording period; encryption and asynchronous sharing do not by themselves prove selective disclosure or a particular zero-knowledge protocol.
  • At 16:16, he broadens identity beyond government documents. DAO contribution, loyalty membership and shopping preferences are also identity-related data. His token-threshold example relies on a DAO-issued claim and is distinct from legal identity or KYC.
  • At 21:15, Banerjee argues that downloading an account archive is different from moving verified reputation to another service. His example involves proving control of a former social handle. It is a proposed use case; the interview does not establish support for such imports in Threads or Mastodon.

Introduction, cheqd and portable reputation

Watch this part · 0:00

Kevin 0:00 Wavect, the Web3 software company that understands what you want. Hi everyone, welcome at Wavect. Today we have a special guest, Ankur from cheqd. And today we will talk about a super exciting topic, and that’s decentralized identity and how to truly own your data. Thanks, mate, for being here. It’s really a pleasure talking with you.

Kevin 0:25 And starting out, I want to give you the opportunity to introduce yourself as well, to let us know what you’re currently working on and whatever you feel is worthwhile to share here.

Ankur 0:38 Sounds good. And thanks for having me here, Kevin. Very excited to be on your podcast. My name is Ankur Banerjee. I’m the CTO and co-founder at cheqd, not pronounced as "check-D", which some people do. And we are a decentralized digital identity network built on Cosmos SDK. What we are trying to do is to make your data more private, more secure, more portable.

Ankur 1:06 And we can go into a bit more detail on how all of that works. What I’m currently working on, and what is extremely exciting, is we’ve also been working on an associated project called Creds.xyz. And Creds.xyz came from a personal sort of need. It builds on top of the cheqd network. And it’s all about decentralized social reputation.

Ankur 1:31 How do people within Web3 communities can have the ability to carry their social reputation as members within a community or members within a DAO to other communities? And that’s really exciting because we feel that it’s one of those use cases which I think people will immediately recognize, although the broader application of our technology can be quite wide.

Ankur 1:59 And in terms of my passions, I would say I really look forward to building a new web or new internet where people have far more control over their own personal data. I think it’s an absolute shame that this was not part of and not baked into the models of the internet when it first started off, or the World Wide Web, in over the past 20, 30 years.

Ankur 2:26 And I’d really love to see some of these very, very large tech companies get disrupted who are the gatekeepers of our data quite often.

What belongs onchain and what stays private?

Watch this part · 2:35

Kevin 2:35 Love it, great mission. You just mentioned Creds [unclear], and I had a quick look at it as well. And I would be really curious about, you just said you’re tying in or including, from my understanding, on-chain reputation, like when you joined the DAO and contributed to some kind of project. Do you also try to solve the gap between off-chain data and on-chain reputation, or how are you thinking about that?

Ankur 3:04 That’s an excellent question. We do use a blend of on-chain and off-chain reputation or on-chain storage. The way I describe it is, traditionally, if you think of decentralized identity, the way people try and solve it is by putting some information into an NFT or a proof of actual person, or POAP, if you’ve heard of that term, and writing that onto a chain.

Ankur 3:32 It’s very useful for a lot of things that are status symbols. It’s a bit like parking a Lamborghini outside your house or a Ferrari outside your house and making all of your neighbors feel jealous. It’s great for that. But the challenge with the model where NFTs or other on-chain storage have is that it is also public for anybody to go and view and see.

Ankur 3:56 So you could have it in a wallet address that is not tied to you. But if at some point, if somebody finds out that is the wallet address that belongs to Kevin, they’d be able to figure out what NFTs you hold over there. So we use a blend of on-chain and off-chain reputation. It’s built on an international standard that has been built by something called the World Wide Web Consortium, or W3C.

Ankur 4:23 You might hear of that term a lot. And it has involvement from not only Web3 companies but a lot of very traditional Web2 companies like Microsoft and Mozilla and Google and so on as well. And the basic idea here in that on-chain versus off-chain is on-chain you store public keys and public signatures that allow you to check that some data is tamper-proof, and then you store the actual details about, say, your social reputation or your health care or your education record or your employment history, any number of use cases, you store that in off-chain wallets.

Ankur 5:09 These wallets can be a bit like the browser extension crypto wallets that you have. They can be on mobile. They can even be stored on physical cards. I’ve seen that as an example and worked on some projects that did that. They could be printed out or as QR codes on paper for backup to have recovery seeds.

Ankur 5:29 But the general idea is that if you have them in purely stored in an off-chain wallet or identity wallet of some sort, when you go and show this to someone to try and say, hey, my name is Kevin. I live in Germany. I’m the host of this particular podcast. I’ve been doing it for the past five years. You have that in a tamper-proof digital format within your identity wallet.

Ankur 5:58 And when you go and show it to someone, what they’re able to do is they’re able to check the stamp or the signature that exists publicly on-chain to verify that the thing that you’ve just shown them has not been tampered with. The example that I use for this is a bit like if you got a paper bank statement sent by your bank and it had a rubber stamp at the bottom.

Ankur 6:22 So storing on-chain is a bit like the rubber stamp. What does the rubber stamp look like for this particular bank? That is the bit that you store on-chain. But the paper which contains your bank statement and your, let’s say, the transactions that you’ve done and the address that you live in and your name, that is physically just with you.

Ankur 6:42 You get to display and choose whom you share it with. Now, that doesn’t prevent you from publishing some of these digital credentials that are tamper-proof in a public fashion, the same way that you might go and make your Twitter profile or your Facebook profile or certain things within those profiles public and other things private.

Ankur 7:04 You still have the option of doing that, but it just gives a lot more flexibility and control on whom do you want to share certain kinds of information.

Kevin 7:14 That sounds pretty interesting. Always when we talk about identity, just some context, my first touch point with crypto itself was a decentralized identity startup many years ago.

Does a valid signature make a credential trustworthy?

Watch this part · 7:15

Ankur 7:27 Oh, wow.

Kevin 7:28 So, and what I remember, one of the biggest issues, uh, to being or creating a decentralized identity actually is the kind of issuance, like how do you not just certify that the data has not been tampered with, but also is the original data that you issued on chain, is that actually true? Like, what’s your approach with that?

Kevin 7:55 Or is that something where you go a similar approach with Polygon ID, if I’m not mistaken here, where you just have these issuers and they can basically input whatever data they want, and then it’s on their reputation to certify if that information is correct?

Ankur 8:12 That’s an excellent question on how do you even understand whether a digital credential that somebody holds is trustworthy or not. The analogy that I use is if you had a digital credential that said you were an employee of a company issued directly by your employer, that is obviously more trustworthy from a human perspective than you writing it yourself on a sheet of paper with crayon, saying, uh, I am the, you write on a sheet of paper with crayon, I’m the CTO of Twitter, now known as X.

Ankur 8:49 So when people go and see that, they will obviously see, actually, I don’t know how much I want to trust that particular piece of paper. But if you had an actual employee badge or if you had an actual thing that came from somebody reputable, they’d consider that to be much more trustworthy. The way we try and solve that, actually, I’m glad you raised this question, is because we do think this has been a massively missing step within a lot of decentralized identity over the past six or seven years that I’ve been working in this space, but also in which it has existed.

Ankur 9:24 And so what we’ve also designed within the cheqd network, which is our network on which you can publish these on-chain elements, is you’re able to publish trusted issuer lists. So for example, if you wanted to have a credential issued by DAOs on Ethereum, people might create a trusted issuer list of what are trustworthy DAOs within the Ethereum ecosystem and what are their public keys and what are their public signatures.

Ankur 9:57 Similarly, if you wanted to go and check what is the structure of the data inside. So for example, if you have a passport, it’s pretty standardized across the world, what those various different fields and what order they come in. That’s why regardless of the language in which the passport is issued, when you go traveling to, I don’t know, Tuvalu, they’re still able to go and check what is the data inside your passport.

Ankur 10:24 So we also allow people to, in a tamper-proof fashion, go and publish associated elements that solve some of the trust and the reputation problems that you were describing in decentralized identity.

How do encrypted wallets and sharing links work?

Watch this part · 10:41

Kevin 10:41 Okay. You also just mentioned before that you’re able to share data publicly and privately. And I’m pretty sure you’re already expecting this, but most just with the recent hype with all these validity rollups out there, you probably use ZK, right?

Ankur 11:04 Yes.

Kevin 11:04 Okay, cool. So how is that interwoven with the public data? Like, you basically host it off-chain in your wallet, on your app, wherever, on your application, basically, right? And then the user shares these claims, or is that some kind of, what’s the high-level user flow, uh, I could imagine?

Kevin 11:33 Now how does it work to share information, and

Ankur 11:36 Yeah, that’s, absolutely. So there’s two elements of zero knowledge. Um, one part of it is how we, as an example, designed the identity wallet for Creds.xyz. It’s purely within a browser. You don’t need to download an application. You don’t need to download a browser extension. But we designed it very much similar to how password managers work.

Ankur 12:01 So if you’ve used something like 1Password, Bitwarden, what they do is they synchronize your password across all of the three, four, five different devices you have, and you have to enter a passphrase to go and unlock that wallet, but it’s only ever decrypted on your own device. So after a digital credential has been given to you, when we back that up, we back that up in an end-to-end encrypted fashion, very much similar to how WhatsApp or Signal works or how password managers like 1Password and Bitwarden work.

Ankur 12:38 So when it is backed up, it allows you to access and log on and access this identity wallet on any device that you want. However, when the encrypted backup is downloaded, you’re only able to read the contents within it and what these digital credentials contain about your social reputation or other facts about yourself, only if you have the passwords.

Ankur 13:04 The public sharing aspect of this, what we allow people to do is, let’s say you wanted to share maybe a time-limited link, like this link is only accessible for 24 hours, or this link is only clickable five times, or this link I actually want to make public, public, forever in a collection that I have on the website.

Ankur 13:29 What we do at that step is when you’re logged into the Creds.xyz wallet or similar SSI, self-sovereign identity, that is, or decentralized identity wallets, you essentially create a snapshot. It’s the same as generating a QR code for your vaccine certificate, which many people might have had to do in the past two years, and you just go and publish that.

Ankur 13:56 Now that allows you to [unclear] share the link with anybody else who might want to view those details and verify those details, but they will get informed that it was generated on, say, the first of August. And if they access the link maybe three months down the line in October or November, what they might actually want from you is to say maybe generate a fresh link and share it to me again to still prove that you’re controlling and holding on to that wallet.

Ankur 14:28 So it’s a bit of a thing that we did for a UX reason. A lot of decentralized identity wallets right now assume that you are sharing these digital credentials live and in real time with someone. And while that is true in some use cases, we don’t think that’s necessarily true in all use cases. Imagine if you wanted to prove your membership to a DAO to somebody on Telegram, but they are not in the same time zone as you, so they might be wanting to go and look at that eight hours later.

Ankur 15:01 So how do you handle that use case? And what we do for the user in this particular example is we take that snapshot, we host it on their behalf and follow the rules that they might want to apply to that.

Why does identity extend beyond passports and KYC?

Watch this part · 15:18

Kevin 15:19 Okay. One question that comes to my mind when I hear all this is, one issue I personally, or one challenge, let’s put it that way, challenge that identity solutions oftentimes have is why, from a user’s perspective, would I use this? Simply because identity is actually, in the end fashion, like the end result, verified by the government, right?

15:51 Yeah.

Kevin 15:51 Or public institutions and not by companies. So how do you go about that? What’s the pathway for cheqd? Is it like you go into governments and try to integrate it here? Is it some more kind of business use cases? Oh well, it’s a verified employee, whatever. Where is it going? Like, what’s the plan?

Ankur 16:15 I think it’s, uh, we, we have a very broad approach to where it could be applied. We do in fact talk to some very large government agencies, or traditional digital identity, as I call it. So traditional digital identity might be when you’re asked to do a know your customer, or KYC, with a bank or crypto exchange.

Ankur 16:36 Or other examples of this is when you have driver’s licenses and passports. And I think that’s how we typically tend to understand and know the word identity. I think it’s actually a bit broader than that. So in the Creds.xyz social reputation examples, maybe you want to prove when you’re voting within a DAO that you hold more than 1 million tokens in that particular DAO without actually revealing what is the wallet address that it’s contained in and what’s the exact figure.

Ankur 17:10 You just want to prove I have more than a million. Because it is a challenge right now. Most DAOs, they will give you voting rights based on how much you’re staking. And that in itself just says how much money you have. It doesn’t say perhaps maybe you are more important to the DAO for other reasons, such as you’re a good code contributor or you’re a good governance contributor, or maybe you make very insightful comments.

Ankur 17:37 And so for that kind of credential, uh, what we have been building, for example, on the Creds.xyz platform is it’s a credential that will be issued by the admins and the moderators of that DAO. It might be tied through a pseudonymous handle like a Telegram handle or Discord handle. It doesn’t have to be, but it could be, or a wallet address.

Ankur 18:01 And it just states the proof that has been issued by the DAO, which does know what the address is, and says yes, Kevin does hold more than 1 million CHEQ tokens. Now what’s interesting about that kind of identity is it is not actually legal identity, or it’s not actually legal know your customer. It is relatively pseudonymous.

Ankur 18:25 And I think when you actually start thinking along those lines, what you find is identity applies to a broad range of use cases which are not government-issued. The Starbucks loyalty membership card that I have, even though it doesn’t have my name on it, is something that personally belongs to me. It doesn’t go through the same level of governance and assurance checks that maybe getting a passport involves.

Ankur 18:53 There’s still something that is my personal data. Or, for example, if I have certain preferences when buying clothing on e-commerce stores online and buying clothing online, that is also a part of my identity and is also personal data that’s related to me. So when you take it in the broader context, I think the decentralized identity space has been quite focused on government-issued credentials becoming digital, and my sort of, like, you know, hypothesis or challenge on that is, how often do you ever need to show your education degree?

Ankur 19:32 Let’s say if it was issued as a digital credential. I’ve only had to do it once in my life for the first job that I got, and ever since then that has not been a major factor. So the challenge is, I think, when you start thinking of things like know your customer, most people get their first bank account when they’re 16 or 18, and they never have to do a KYC until the moment they buy a house, perhaps 20 years later.

Ankur 19:58 So it just doesn’t happen that often. But what happens way more often is interacting with social media, with messenger applications, with online forums, with online e-commerce. And all of those places, you’re trying to share some kind of personality profile or personality data that customizes the experience for you.

Ankur 20:22 And that, I think, is the much broader vision for what digital identity is.

Can downloaded data move your identity to another platform?

Watch this part · 20:28

Kevin 20:28 That’s an interesting take. I think it’s a little, that that’s just a personal thought on my end. Could it be that this is dependent a little bit more on the use case itself? Because when I think on the big FAANG companies, [unclear] Meta, Alphabet and so on, I don’t, they would have the resources to just use your data in a fully GDPR-compliant manner, if you speak of Europe, for example, right now.

Kevin 21:06 But they don’t, or actually just do the necessary evil for them to still pursue their business case.

Ankur 21:14 Correct. They’ll only allow you to download, they’ll only allow you to download a copy. You can go and under GDPR rights download a copy of your entire Facebook history. But you just get a bunch of spreadsheets, computer-readable files, and images that you’ve uploaded. It’s not very usable. You can’t actually easily take that and say, okay, I’m done with Facebook.

Ankur 21:40 I want to move across to a new competitor platform that has come up on Mastodon. And so you’re absolutely right. The FAANG companies and the large tech companies, what they generally enable is the bare minimum they need to comply with the law, but they don’t actually make your data very portable, or at least not in an easy way that you can move across to something else.

Ankur 22:04 What a lot of decentralized identity allows, to take a social media example, is let’s say I was fed up of Twitter, like a lot of people are. I’m not. I do actually enjoy it. But let’s say I was, and I wanted to shift across to Threads. I might not have access to the same username or handle on a different service because it’s been taken up by someone else, and just the handle being the same doesn’t mean it’s the same person.

Ankur 22:32 And even if I downloaded all of my data from Twitter, you can’t take that across in a portable fashion easily. But what you could achieve with a bit of, like, you know, decentralized identity is being able to say, I’ve set up a new account on Threads or Mastodon. I can validate that I used to be the same person or account, at least, that used to control this handle on Twitter.

Ankur 22:59 And this is a verified import of my 10-year Twitter history. And being able to prove all of those facts to someone. So when you start looking at it that way, I think the, the challenge is that obviously the European Union has been one of the more forward-looking sort of regulatory frameworks within this.

Ankur 23:23 There’s something called the Digital Markets Act, which they recently sort of passed, that is aimed towards increasing competition and this kind of portability, because even they realize GDPR doesn’t actually give people a lot of rights. It maybe helps them go delete their data with the company if they want.

Ankur 23:46 That’s the one thing it gets right. But on everything else, it’s not really informed consent. You just see a cookie banner pop up and everybody just clicks yes, and then you’ve just given them permission to do whatever you want with you, with your data. So, and it doesn’t actually help you move across to a new service quite easily.

Ankur 24:06 So I’m very excited about some of the regulatory changes that are happening, and I think for sure it would be extremely exciting with some of the work that we’re doing with governments as well on being able to have a digital copy of government-approved or government-issued credentials, or maybe government-regulated industries, for example banking, healthcare.

Ankur 24:31 These are all regulated industries for good reasons. But, um, personal challenge I faced is when I go to see a new doctor, they do not have access to my medical files. At best, I get a DVD. What am I supposed to do with that? So I’m excited about those government-led use cases, for sure, because I think they have a high degree of confidence, a high degree of trustworthiness and reputation.

Ankur 24:59 But I’m also extremely curious about what could happen in the more private sector if our data became more free-flowing.

Kevin 25:08 Love that. I think that’s a great ending for that part. If you don’t mind, I’m trying to introduce some kind of a new tradition here, and that would be you asking an arbitrary question to whatever guest is coming next. And it can be anything. It’s probably a good idea to not have it too technical or too niche in some kind of topic, because not every guest is a technical person, but I leave that up to you.

A question for the next guest

Watch this part · 25:09

Ankur 25:42 My question for the next guest would be, what is the most interesting thing you’ve learned in crypto or Web3 in the past year? Something that surprised you and that you didn’t sort of originally anticipate or know about. I find that to be very fascinating when I have that kind of discussion at Web3 conferences or decentralized identity conferences.

Ankur 26:12 So that would be my question for the next guest.

Where to learn more and closing

Watch this part · 26:15

Kevin 26:15 Love it. Hey, thanks, Ankur. It was really a pleasure talking with you. If you have any links for me to share in the video description, whatever, I’m happy to do so. Otherwise, I would say thanks, thanks for taking the time out of your probably very busy day. And yeah, thanks everyone for watching.

Ankur 26:34 So the two links that I’ll send this across to you as well: if you want to check us out, go to cheqd.io. That is our protocol-level network that has 40-plus different partners who are digital identity, decentralized identity vendors. Some of the largest names in the game, they work and build on our network.

Ankur 26:57 So you can go check that out if you’re more technically inclined. Or if you are not that technically inclined or more interested in our social reputation thing, go to Creds.xyz and check out how we are trying to tackle the use cases around being able to take your social reputation and take that anywhere in a private, secure, and portable fashion.

Kevin 27:20 I love it. So thanks, everyone. Thanks, Ankur, again. See you next time.

Ankur 27:28 Thanks, Kevin.

Kevin 27:29 Wavect, the Web3 software company that understands what you want.

Transcribed from the original audio with Whisper large-v3 and AI-reconciled with the original automatic captions. Unclear speech is bracketed; speaker labels and translations are editorial aids. No complete human listening pass. The recording remains authoritative; statements reflect its date. This interview was published in August 2023. Roles, product descriptions, plans, the 40-plus partner count and regulatory opinions reflect the recording period. Banerjee expands POAP as "proof of actual person", but the term usually means Proof of Attendance Protocol. He answers "Yes" when asked whether ZK is used. His subsequent explanation covers encrypted wallet backups and sharing snapshots; it does not specify a zero-knowledge proof system. The verified import of a Twitter history onto Threads or Mastodon is a proposed use case. The interview does not establish support for such imports in those services. Remarks about GDPR, the Digital Markets Act and large tech companies are the speakers' views and are not legal guidance.

Questions this episode answers

No. Signature verification checks the credential’s integrity and its connection to the signing issuer. The verifier still decides whether to trust that issuer for the claim and purpose. At 08:13, Ankur Banerjee contrasts an employer-issued employee credential with a self-written claim and describes trusted issuer lists. The current W3C data model explicitly separates verifiability from the truth of claims.
Banerjee’s design keeps personal credential details in offchain identity wallets and uses public verification material onchain. At 03:05, he warns that public NFTs become linkable when their wallet address is associated with a person. W3C DID guidance says public DID documents should contain no personal data. Decentralized identity does not universally require a blockchain; the exact storage and verification design depends on the DID method and credential system.
A trusted issuer list helps verifiers identify which organizations or communities they accept for particular claims. Banerjee gives the example of reputable Ethereum DAOs and their public verification material. A list is a trust-policy input; it does not automatically make every signed statement true or remove the need to assess the claim’s context and currency.
No. End-to-end encryption protects stored or synchronized content; a zero-knowledge proof is a separate cryptographic mechanism for proving a statement without revealing its underlying secret. The interview’s 11:37 answer discusses encrypted backups and sharing snapshots but does not specify or benchmark a proof protocol. It should not be read as evidence that every shared credential uses selective disclosure.
Not in Banerjee’s example. At 16:16, he distinguishes pseudonymous DAO credentials from legal identity and legal know-your-customer processes. A community-issued contribution or token-holding claim may help with membership or governance, but acceptance depends on the verifier and purpose. The conversation does not establish that it satisfies regulated identity checks.
Banerjee describes credentials that let people carry community reputation or prove previous control of a social account. At 21:15, he contrasts downloading an archive with presenting a verifiable account-history claim. A receiving service still needs compatible formats and an acceptance policy. This proposed direction reflects the recording period; the interview was published in August 2023. The interview does not establish support for such imports in Threads or Mastodon.

Want this kind of thinking applied to your product?

We build MVPs and act as fractional CTOs for founders who’d rather ship than talk.