STEP 01 / 10
ENCRYPTION
DECRYPTION
How it works
From the sender’s device to the recipient: what happens when data is locked, and what happens when it opens.
STEP 01 / 10
ENCRYPTION
DECRYPTION
No one sees the data before the trigger
No human involvement at unlock
Every step is auditable on the blockchain
Triggers
“Open this bid at 14:00 on 31 March.”
“Release when the match ends.”
Triggered by a single SDK call from your application.
Multi-condition rules for any workflow.
EXAMPLE
IF deadline = 31 MAR 14:00 UTC
AND all bids received
→ UNLOCK
Comparison
| FEATURE | Password-protected file | Escrow service | QTLE |
|---|---|---|---|
| Can it be opened before the deadline? | Yes, by anyone who has the password | Yes, by the escrow provider | No, not even by the operator |
| Who must you trust? | Everyone who knows the password | The escrow provider | No single party |
| Quantum-safe? | Not designed for it | Depends on the provider’s systems | Yes, post-quantum algorithms |
| What happens at unlock? | The password is shared by hand | A person releases the key | Opens automatically, no human input |
| Audit trail | None | The provider’s own records | Every step on the blockchain |
| Can it open on an event? | No | Only after manual verification | Yes: time, event or custom logic |
| Client SDK | None | Varies by provider | Java, Python, TS/JS, Go |
IntegrationPartnershipInvestment