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

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

Check this

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.

1 Like