New Algorithm for Generating Cryptographic Keys More Secure Than Today’s Public‑Private Key Systems
Today’s internet security depends on public‑private key systems — but private keys can be stolen, copied, or leaked. I’ve developed a new authentication algorithm that eliminates the private‑key vulnerability entirely. Instead of storing a secret key that attackers can target, this method uses synchronized timestamps and shared transformations to generate short‑lived, one‑time values that never repeat and never need to be stored.
​
The result is a secure system that cannot be attacked by stealing a private key, because no private key exists.
In addition, both parties only need to synchronize their clocks and share a method array during initial setup. After that, they do not need to exchange any information to generate new keys. These keys can be generated as frequently as needed, making the system extremely difficult to decipher.
​
How It Works
-
Clock Synchronization: Both parties synchronize their clocks with a central, trusted NTP (Network Time Protocol) server.
-
Shared Initialization: During initial setup, both parties share the same transformation‑method array and the same random‑number generator.
-
Agreed Key‑Generation Time: Both sides agree on when to generate the cryptographic key (for example, at midnight or at fixed intervals)
-
Key Generation Process: At the agreed moment, each side uses part of its clock data as input to the random‑number generator. The generator produces an index that points to one of the transformation methods in the shared array. Using that method, each side applies the transformation to the clock data to independently generate the same cryptographic key.
-
No communication is required during this process — both sides derive the same key without exchanging any information.
Security in Case of Device Capture
If a device falls into the hands of a foreign adversary, it will be unable to synchronize its clock with the trusted NTP source. When this condition is detected, the device can activate a built‑in protective response — for example, wiping its storage by low-level format and shutting down to prevent misuse.
Dual‑Clock Security Enhancement
For highly secure devices, the system can be equipped with two internal clocks:
-
Clock A: Synchronizes with the trusted NTP server.
-
Clock B: Synchronizes once with Clock A, then runs independently at its own pace.
After the initial synchronization, Clock B can intentionally run faster or slower than the standard clock. Because both parties know the expected behavior of this secondary clock, they can still generate matching cryptographic values — but an attacker cannot.
This design provides an additional layer of protection:
-
The timing pattern becomes non‑standard and unpredictable to outsiders.
-
Even if someone intercepts data, the shifting clock speed makes it nearly impossible to decipher or reconstruct the key‑generation process.
-
A foreign adversary cannot replicate the clock behavior without access to the device’s internal timing model.
This dual‑clock approach significantly increases resistance to reverse engineering, cryptanalysis, and hardware‑level attacks.
​​
​
US Patents: 11,509,463, and 11,438,145
Japanese Patent No. 7618057
European (EP) Patent No. 4324156
Future Innovations:
Seeking business partners to develop this solution.​
For inquiries, please send a USPS registered mail to
ChienSEC LLC
12400 SE 38TH ST #40151
Bellevue, WA 98015
​