CREDENTIAL ISSUED
Issuer signs a set of identity attributes for a user and gives to user for storage
Getting Started With HederaXBarid E-Seal
Trusted & Protected Document Signing with Hedera Hashgraph Distributed Ledger Technology.
Electronic Signatures Backed by Hashgraph Technology
Not all electronic signature services are created equal, and no one wants to question the integrity of their digitally-signed documents. With E-Seal, every action taken with a document is logged and timestamped using Hashgraph Technology – a more secure database technology - which helps prevent fraud, false signatures, or other types of tampering.
Why do we use DLT for Document Signing?
OPEN STANDARDS
Hedera's credentials follow the decentralized identifier and verifiable credentials standards under development at the W3C.
Auditing & Tracking
Every step of the signing process is tracked and timestamped using DLT, creating a record of activity that is the perfect audit trail.
Fraud Prevention
Because DLT data can’t be modified, records stored in blockchain can’t be changed or tampered with.
Security
With DLT, data isn’t stored in one centralized location, which makes it more difficult to hack.
How the E-Seal Works
Applications issuing credentials to an end user, as well as every event in the credential’s lifecycle, are recorded on Hedera. When a credential is presented to an application or business, supporting information is securely retrieved to either validate or lookup related identity information.
ISSUANCE RECORDED
Metadata for credential recorded via an HCS message
CREDENTIAL USED
User presents credential as part of authentication process at some application/resource
METADATA RETRIEVED
Relying party retrieves timestamped metadata in order to validate credential
CREDENTIAL REVOKED
When necessary, issuer can revoke the credential via HCS message
CREDENTIAL USED
The next time the credential is presented, authentication fails