Verifiable Documents Overview
There are 2 type of verifiable documents which uses different types of issuer method, a blockchain issuer method (DNS-TXT) and a DID issuer method (DNS-DID). For the blockchain issuer method (DNS-TXT), the fingerprint of the wrapped TradeTrust file is then committed to a Document Store smart contract on the Blockchain, which serves as an immutable ledger. For the DID issuer method (DNS-DID), the document is signed instead of being committed to the blockchain.
Both the signed and committed TradeTrust file can then be distributed to recipients, who will be able to verify the file on https://tradetrust.io/verify simply by dragging and dropping it into the Web interface.
Types of Verifiable Documents
As of today, we have 2 different types of issuer methods, thus, we have 2 forms of verifiable documents:
- Blockchain (DNS-TXT)
- DID (DNS-DID)
Commonalities
These 2 forms of Verifiable Documents rely on a common trust anchor, which is the use of DNS records. Since DNS records are often considered an authoritative source for a domain name, the DNS entry represents the entity.
For further explanation, refer to their respective sections DNS-TXT AND DNS-DID
Differences
-
Tracking the issuance status of a Verifiable Document
- Blockchain issued documents are issued directly on the document store
- DID issued documents relies the integrity and signature of the document
-
Tracking the revocation status of a Verifiable Document
- Blockchain issued documents are revoked directly on the document store
- DID issued document are revoked through alternative channels
- A Document Store can be specified on the verifiable document, relying on the blockchain