请问attestation和W3C的verifiable credential是不是一回事

lisoleg · August 9, 2022, 7:49am

请问TokenScript有考虑和W3C的DID结合起来吗

weiwu.zhang · August 10, 2022, 4:14am

Check this

TokenScript/documents/blob/main/src/faq/attestation_vs_verifiable_credentials.md

# Attestation vs Verifiable Credentials

Attestations and Verifiable Credentials are based on the same cryptographic protocols, with overlapping scope. They differ in the design paradigm and applicable use cases. As a consequence, their data formats differ, too.

Verifiable credentials are centralised around individuals (entities), that is, someone, Alice or Bob, has the credential, such as a verified Facebook user, or qualified for financial services advisory; therefore, they can do something on a certain website. The whole concept doesn't have much to do with tokens, and the web is the main use case.

Attestation is centralised around tokens. For example, a user has an attestation to a Devcon conference. This attestation is used as a token in all practical senses, including on smart contracts and the web.

|                       | Attestation                                                  | Verifiable Credentials                                       |
| --------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
| Core Assumption       | There is a token. No entity assumed.                         | There is an entity - typical, a person. No token assumed.    |
| Additional Assumption | Confidentiality is none-existent. Attestation can be exposed on the blockchain without leaking identity. | The verifiable credential pass between a secure connection (TLS) |
| Cryptography          | Issuing Ceremony. Cryptographic challenge. zk-hiding. Attested Transactions. | Issuing Ceremony. Cryptographic challenge.                   |
| Data Format           | Binary, as each bytes cost gas.                              | JSON                                                         |

## A overlap use-case, to demonstrate the difference.

There are overlapping areas such as a user is able to get a verifiable credential as a Gmail user, and he can be attested as a gmail user with an attestation. In this example overlapping areas:

- Verifiable credential focuses on the web use-cases, where confidentiality is implied. Therefore they do not hide the user's email address as attestations do with zk-proof.

This file has been truncated. show original

I‘m in agreement with W3's DID approach in solving IDENTITY on the WEB (web2).

But we don't mainly work on identity. attestation work focuses on tokens.

There are perhaps 20% to 30% overlapping use-cases, and in these use-cases, we can't take DID directly because existing DID is bloated JSON and assumed confidentiality; we can't take them into a smart contract without exploding gas and causing privacy leak, so it troubles me how to stay compatible with them. Given the overlap use-case is only 20% to 30%, I'd focus on what we do first (attested NFT, tokens issued on attestations, tokens as attestations, cross-chain etc.).

There is one overlapping use case examined in the aforementioned document so you can take a closer look at how these use-cases are handled differently.

I am happy to work with DID on how to get a common format and add zk hiding to protect privacy on a non-TLS, smart-contract context, but I need someone help me to do that, the work is already overflowing in the core use-cases we want to address, such as DevCon ticket token as attestation.

Topic		Replies	Views
TokenScript Weekly meeting #36 Tokenscript Design	0	465	June 4, 2020
TokenScript Weekly Meeting #32 Tokenscript Design	2	484	May 19, 2020
Send with attestation and send to attestation, MVP use-case of attestation Usecases	19	1665	August 17, 2020
A stateless approach to archtect the identifier attestation issuer site Tokenscript Design	2	458	December 11, 2020
TokenScript meeting #39 Tokenscript Design	3	757	July 3, 2020

请问attestation和W3C的verifiable credential是不是一回事

Related topics