FAQ
Who is ComPilot for?
ComPilot is the right tool for you if you are building:
- An established Web2 application, and you are looking to expand into Web3. You want to provide your customers with full digital ownership of their identities and assets without compromising the great UX you built for Web2.
- A decentralized application, and you want to embed compliance without introducing centralization.
- A Web3 wallet, and you are looking to integrate additional functionalities like the seamless generation or management of Verifiable credentials.
What does ComPilot allow you to do?
ComPilot will allow you to:
- Integrate complex compliance workflows based on verifiable credentials.
- Preserve the self custody and security of the consumers’ identity and assets.
What is the difference between verifiable credentials and verifiable presentations?
These concepts are part of the emerging decentralized identity ecosystem, and are based on the W3C reference. The difference between a Verifiable Credential and a Verifiable Presentation (VP) lies in their purpose and structure.
A Verifiable Credential is a tamper-evident digital statement or claim made by an issuer about a subject (also called a holder). The credential contains specific information or attributes about the subject, such as their name, age, or qualifications. VCs are digitally signed by the issuer using cryptographic techniques, making them verifiable and secure.
For example, a digital driver's license is a verifiable credential. It is issued by a trusted authority (the Department of Motor Vehicles) and contains information about the license holder, such as their name, date of birth, and license type.
A Verifiable Presentation is a digital container that a holder (subject) uses to present one or more Verifiable Credentials to a verifier. The presentation is also digitally signed by the holder, providing proof of the holder's possession and control over the presented VCs. VPs can also support selective disclosure, allowing the holder to share only specific pieces of information from the original VCs with the verifier, based on the verifier's requirements.
Continuing with the driver's license example, when the license holder presents their digital driver's license to a bar to prove they are of legal drinking age, they create a verifiable presentation containing the necessary information (date of birth) from the original VC (the digital driver's license) and sign it to prove their possession and control over the license.
In summary, a Verifiable Credential is a signed digital claim made by an issuer about a subject, while a Verifiable Presentation is a signed digital container that a holder uses to present one or more Verifiable Credentials to a verifier.