There are four ways to verify the authenticity of any document signed within TWALA. Verify document by:
Logging in to your TWALA Account
Visting TWALA's website.
Scanning the QR code from the document's audit trail. This is designed for printed documents.
Command Line Interface (CLI).
Twala generates the root hash of all the documents signed within the month and sends it to the main public Ethereum. The monthly root hash is tied to the previous root hash making it harder to alter any document recorded within Twala. This process is also known as chained anchoring.
Twala CLI NPM Package: https://www.npmjs.com/package/@twala-io/twala-cli
Document Verification Result
If the document is verified to be authentic and not altered, it will show the following details:
Document Name
Document Hash
Owner of the document (Sender)
Digital timestamp
Signatories - including their digital ID (if with Twala ID), email, IP address
Blockchain block number
Transaction hash
When you have a verified document, it looks like this:
Otherwise, you'll get an error message:
Note:
Users with a check badge beside their names are verified TWALA users. They have created a self-sovereign TWALA ID.