US 12,250,204 B2
Securing attestation using a zero-knowledge data management network
Brett Shockley, Bonita Springs, FL (US); Alexander John Shockley, Denver, CO (US); Michael Joseph Frendo, Boulder, CO (US); Shmuel Shaffer, Palo Alto, CA (US); Kenneth Keiter, Portland, OR (US); and James M. Behmke, Duxbury, MA (US)
Assigned to Journey.ai, Denver, CO (US)
Filed by Journey.ai, Denver, CO (US)
Filed on Jul. 8, 2024, as Appl. No. 18/766,474.
Application 18/766,474 is a continuation of application No. 17/411,201, filed on Aug. 25, 2021, granted, now 12,034,711.
Application 17/411,201 is a continuation of application No. 16/703,853, filed on Dec. 4, 2019, granted, now 11,133,940, issued on Sep. 28, 2021.
Claims priority of provisional application 62/775,302, filed on Dec. 4, 2018.
Claims priority of provisional application 62/852,850, filed on May 24, 2019.
Prior Publication US 2025/0023851 A1, Jan. 16, 2025
This patent is subject to a terminal disclaimer.
Int. Cl. H04L 29/06 (2006.01); G06F 3/06 (2006.01); G06F 21/60 (2013.01); G06F 21/62 (2013.01); G06F 21/64 (2013.01); G06Q 20/38 (2012.01); G06Q 20/40 (2012.01); H04L 9/06 (2006.01); H04L 9/08 (2006.01); H04L 9/14 (2006.01); H04L 9/30 (2006.01); H04L 9/32 (2006.01); H04L 9/40 (2022.01)
CPC H04L 63/0471 (2013.01) [G06F 3/062 (2013.01); G06F 3/0655 (2013.01); G06F 3/067 (2013.01); G06F 21/602 (2013.01); G06F 21/62 (2013.01); G06F 21/645 (2013.01); G06Q 20/38215 (2013.01); G06Q 20/3829 (2013.01); G06Q 20/383 (2013.01); G06Q 20/401 (2013.01); H04L 9/0643 (2013.01); H04L 9/0819 (2013.01); H04L 9/0825 (2013.01); H04L 9/083 (2013.01); H04L 9/0833 (2013.01); H04L 9/0891 (2013.01); H04L 9/14 (2013.01); H04L 9/30 (2013.01); H04L 9/3218 (2013.01); H04L 9/3236 (2013.01); H04L 9/3242 (2013.01); H04L 9/3247 (2013.01); H04L 9/3263 (2013.01); H04L 9/3265 (2013.01); H04L 9/3268 (2013.01); H04L 63/0421 (2013.01); H04L 63/0442 (2013.01); H04L 63/083 (2013.01); H04L 63/101 (2013.01); H04L 63/102 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A method, comprising:
storing information on a third-party server, wherein the third-party server and an attestation service cannot read the stored information;
storing, on the third-party server, a re-encryption key that converts the stored information to a format readable to only the attestation service;
requesting, by the third-party server from the attestation service, attestation of whether the stored information is correct, wherein requesting comprises applying the re-encryption key to the stored information and sending the stored information, in the format readable to only the attestation service, to the attestation service;
receiving, by the third-party server from the attestation service, an indication as to whether the stored information, which cannot be read by the third-party server, is attested as correct by the attestation service; and
providing, from the third-party server, the indication as to whether the stored information is attested as correct by the attestation service to an interested device, without the third-party server knowing the information.