The Gordian Envelope Smart Document is a powerful new method of data storage and transmission that focuses on protecting the privacy of its contents through cryptographic functions such as signatures, elision, and inclusion proofs.
But what does that mean? Why would you use it? To answer these questions we’ve written a set of use cases that not only demonstrate many innovative uses for Gordian Envelopes, but also show precisely how those Envelopes would be structured — because these use cases aren’t theoretical, but instead real possibilities with the current iteration of the Gordian Envelope specification.
Most of the following use cases are offered progressively: additional use cases build on earlier ones, expanding the fundamental ideas with new functionality in each example. (That functionality is listed as part of each use case’s name.)
For a broader overview of these use cases and some discussions of what they have in common, see our use case overview.
Educational use cases demonstrate how Gordian Envelope can transmit sensitive student information, including educational credentials.
The first set of use cases demonstrates how recognized issuers can create and use credentials.
- Danika Proves Her Worth (Credentials, Signature) — Issuing authenticated credentials with Gordian Envelope
- Danika Restricts Her Revelations (Elision) — Using elision to allow a holder to selectively hide Envelope contents.
- Thunder & Lightning Spotlights Danika (Third-Party Repackaging) — Adding content to an existing Envelope & republishing it.
Individuals may instead want to create peer-to-peer credentials.
- Omar Offers an Open Badge (Web of Trust Credentials) — Creating a credential based on personal authentication.
Another possibility for credential release is through large data dumps that allow the user to stay in control over whether they’re ever revealed.
- Paul Privately Proves Proficiency (Herd Privacy) — Creating highly private credentials.
- Paul Proves Profiency with Improved Privacy (Herd Privacy with Non Correlation) — Using design formats to improve herd privacy.
- Burton Bank Avoids Toxicity (Herd Privacy with Selective Correlation) — Avoiding toxic data by selective correlating unrevealed information.
Wellness use cases demonstrate how Gordian Envelopes can protect highly sensitive information while still supporting its sharing in a variety of ways.
How to structure and protect sensitive data with Gordian Envelopes.
- Nadia Gets Fit (Metadata) — Creating a structure for sensitive data.
- Nadia Protects Her Privacy (Encryption) — Protecting sensitive data with encryption.
- Nadia Protects Her Key (SSKR) — Ensuring the resilience of closely held data.
The value of Wellness information is that it can help you improve your health. Gordian Envelopes can make sure that doesn’t compromise your privacy.
- Nadia Hearts Her Doctor (Elision) — Eliding data so that you don’t pass on person or health information that could be detrimental.
- Nadia is a Bit Remote (Multi-Permit) — Using multipermits to give third-party monitors regular access to your data.
- Nadia Steps Up (Signature) — Using signatures to prove the provenance of your data.
- Nadia Foils Fusion (Salting) — Using salt to prevent sensor fusion.
Your personal health data can also help our society (and its public health), and Gordian Envelopes can ensure that your privacy is still safe.
- Nadia Gets Clinical (Elision, Third-Party Encryption) — Contributing to a clinical trial and protecting everyone with encryption.
- Nadia Proves Her Worth (Proof of Inclusion) — Proving your contribution with hash-based elision.
- Nadia Becomes a Number (Anonymization, Provenance) — Blurring data while maintaining its provenance.
- Nadia Goes Viral (Herd Privacy) — Contact tracing without the privacy problems.
Software use cases demonstrate how the structure of Gordian Envelope can innovate procedures requiring signing, such as software releases.
Gordian Envelopes can automate releases of data over time by creating and updating a root of trust within the Envelope.
- Casey Codifies Software Releases (Multiple Signatures, Structured Data) — Structuring release data and authenticating it with multiple signatures.
- Blockchain Everyday Confirms Casey (Repackaging Data, Third-Party Verification) — Adding additional levels of data verification by repackaging Envelopes.
- Casey Chains His Software Releases (Chained Data) — Using Envelope structure to automate the release of future data.
- Casey Checks Compliance (Attestation, Metadata) — Adding signed metadata to a structured data set.
- Casey Changes Up His Software Releases (Chained Changes) — Using structured data to announce changes in trust over time.
Authentication can be combined with elision to allow for signing that is pseudonymous yet validated.
- Amira Signs Anonymously (Anonymous Signature, Web of Trust) — Using a Web of Trust to verify a signature made pseudonymous through elision.
- Amira Reveals Her Identity (Progressive Trust) — Removing elision over time to gain reputation from previously published works.
Data distribution is crucial for a variety of use cases, from the supply chain to the medical industry. The use cases in this section take as an example the distribution of user data based on a WebFinger-like protocol, highlighting the advantages of building a privacy-first data structure.
The most fundamental usage of Gordian Envelope is to publish verifiable data that is entirely public.
- Carmen Makes Basic Information Available (Structured Data) — Using Gordian Envelope to release structured data.
- Carmen Makes CryptFinger Verifiable (Signatures) — Adding authentication to allow for data portability.
- Carmen Adds Chronology to CryptFinger (Timestamp) — Easily expanding verifiable data with improtant metadata.
Building on the elision capabilities of Gordian Envelope can produce data that is not (initially) viewable by everyone, but which remains provable and ultimately releasable.
- Carmen Protects CryptFinger (Elision) – Eliding data for some viewers and not others.
- Carmen Makes CryptFinger Provable (Inclusion Proof) — Using inclusion proofs to purposefully allow selective correlation.
- Carmen Makes CryptFinger Progressive (Progressive Trust) — Building a progressive trust algorithm using selective correlation.
A herd-privacy variant of CryptFinger’s design can allow users to maintain their privacy as much as they wish, as discussed in this overview.
There are many other options for cryptographic data distribution, building on signatures, provability, repackaging, and encryption permits, as is discussed in this further overview.
Although the financial industry can make many uses of Gordian Envelopes to preserve assets, these use cases concentrate on self-sovereign control of assets: how an individual can use Gordian Envelopes to make sure he doesn’t lose them.
Envelopes can simply and securely store digital assets.
- Sam Stores a Secret (Secure Storage with Metadata) — Using metadata in an Envelope to increase the resilience of stored assets.
- Sam is Salty about Compliance (Non-Correlation) — Salting data to eliminate correlation dangers.
- Sam Gets Paranoid about Privacy (Wrapped Encryption) — Improving privacy at the cost of resilience.
However, resilience can be further improved with Gordian Envelope permits.