Cryptographic time infrastructure
Time becomes the key.
Encryption defines who may access information.
DateKeys adds a second condition: when.
Protect information now. Make it accessible only at the appointed time.
For a more thoughtful tomorrow
Some
information
is meant
for a later
tomorrow
A truth endures
“The wisest is Time, for it brings everything to light.” Thales of Miletus
Encrypted state
Locked in time.
The information remains inaccessible until the selected moment arrives.
No early access. No manual release.
No premature disclosure.
A new dimension for encryption
Access stops being one question and becomes two. Both have to be satisfied, and only one of them is about identity.
02
- WHO
- Identity, authorization or possession.
- WHEN
- The moment at which access may become possible.
- ACCESS
- Only when both conditions are satisfied.
How time becomes part of access
03
-
01
Protect
Information is encrypted before it enters the time-bound process.
-
02
Define
A future moment or temporal condition is established.
-
03
Wait
The information remains cryptographically unavailable beforehand.
-
04
Unlock
When the required moment arrives, access can become possible.
Information
that must wait.
04
- Digital inheritance
- Information intended to survive its owner.
- Delayed disclosure
- Documents or information that should become available at a future date.
- Embargoed information
- Material that must remain confidential until an agreed moment.
- Escrow
- Information whose availability depends on authorization and time.
- Future communication
- Messages, documents or secrets intended for another moment.
Built around confidentiality
05
- Private by design
- Sensitive information remains encrypted throughout its lifecycle.
- Time-bound access
- Define when information may become accessible.
- No early access
- The system is designed around preventing premature disclosure.
- Long-term thinking
- Designed for information that may need protection for years or decades.
The internet knows how to encrypt information.
It does not yet treat time as a first-class cryptographic condition.
That is what DateKeys is being built for.
People
Ideas
Documents
Memories
Research
A clearer future
Not a timer.
Not a scheduled release.
A timer can decide when software performs an action. DateKeys is being designed around a different idea: making time itself part of the conditions under which protected information can become accessible.
06
Scheduled action
Software performs something at a certain time.
Operational trigger
Service executes an instruction
Often requires trust in the service
DateKeys
Access depends on time, as a cryptographic condition.
Cryptographic availability model
No premature disclosure
Minimises who needs to see the secret
Designed for the long term
Some information must remain protected for hours. Other information may need to wait years or decades.
07
TODAY
1 YEAR
5 YEARS
10 YEARS
25 YEARS+
Different secrets.
Different horizons.
Security without unnecessary exposure
Protecting information should not require exposing its plaintext to intermediary services. Minimise who ever needs to see the secret.
08
Source
Protected
Time condition
Access
Why now
01
More information must outlive its creator.
Digital estates, confidential records and long-term information are growing needs.
02
Identity is well modeled. Time is not.
Cryptography handles who very well. Time remains comparatively underrepresented.
03
Modern systems make new models possible.
Advances in cryptography and distributed systems enable new approaches to time-bound access.
Investors welcome
Building cryptographic infrastructure for time-bound access.
DateKeys is an early-stage infrastructure project exploring a simple idea: information should be able to remain securely unavailable until its moment arrives.
09
This page's scripts have not loaded, so sending will not report back here. Write to hello@datekeys.com instead.