# US 2024/0205203 A1 · Performing concealed transactions using a zero-knowledge data management network

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2024/0205203 A1
- Document ID: US20240205203A1
- Status: Published application
- Kind: A1
- Application number: 18/541,845
- Filed: 2023-12-15
- Published: 2024-06-20
- Earliest claimed: 2018-12-04
- Assignees: Journey.ai
- Applicants: Journey.ai
- Inventors: Brett SHOCKLEY; Alexander John SHOCKLEY; Michael Joseph FRENDO; Shmuel SHAFFER; Kenneth KEITER; James M. BEHMKE
- Web page: https://patentgrep.com/patent/US20240205203A1

## CPC

- H04L 63/0471: {applying encryption by an intermediary, e.g. receiving clear information at the intermediary and encrypting the received information at the intermediary before forwarding}
- G06F 3/062: {Securing storage systems}
- G06F 3/0623: {in relation to content}
- G06F 3/0655: {Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices}
- G06F 3/0661: {Format or protocol conversion arrangements}
- G06F 3/067: {Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]}
- G06F 3/0671: {In-line storage system}
- G06F 21/602: {Providing cryptographic facilities or services}
- G06F 21/62: Protecting access to data via a platform, e.g. using keys or access control rules
- G06F 21/645: {using a third party}
- G06Q 20/38215: {Use of certificates or encrypted proofs of transaction rights}
- G06Q 20/3829: {involving key management}
- G06Q 20/383: {Anonymous user system}
- G06Q 20/401: {Transaction verification}
- H04L 9/0643: {Hash functions, e.g. MD5, SHA, HMAC or f9 MAC}
- H04L 9/0819: {Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) (network architectures or network communication protocols for key distribution in a packet data network H04L63/062)}
- H04L 9/0825: {using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates}
- H04L 9/083: {involving central third party, e.g. key distribution center [KDC] or trusted third party [TTP]}
- H04L 9/0833: {involving conference or group key (network architectures or network communication protocols for key management in group communication in a packet data network H04L63/065)}
- H04L 9/0891: {Revocation or update of secret information, e.g. encryption key update or rekeying}
- H04L 9/0894: {Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage}
- H04L 9/14: using a plurality of keys or algorithms
- H04L 9/30: Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy
- H04L 9/3218: {using proof of knowledge, e.g. Fiat-Shamir, GQ, Schnorr, ornon-interactive zero-knowledge proofs}
- H04L 9/3236: {using cryptographic hash functions}
- H04L 9/3242: {involving keyed hash functions, e.g. message authentication codes [MACs], CBC-MAC or HMAC}
- H04L 9/3247: {involving digital signatures}
- H04L 9/3263: {involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements (network architectures or network communication protocols for supporting authentication of entities using certificates in a packet data network H04L63/0823)}
- H04L 9/3265: {using certificate chains, trees or paths; Hierarchical trust model}
- H04L 9/3268: {using certificate validation, registration, distribution or revocation, e.g. certificate revocation list [CRL]}
- H04L 63/0421: {Anonymous communication, i.e. the party's identifiers are hidden from the other party or parties, e.g. using an anonymizer}
- H04L 63/0442: {wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption (cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30)}
- H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)}
- H04L 63/101: {Access control lists [ACL]}
- H04L 63/102: {Entity profiles}
- H04L 2209/56: Financial cryptography, e.g. electronic payment or e-cash
- H04L 2209/64: Self-signed certificates
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

The techniques herein are directed generally to a “zero-knowledge” data management network. Users are able to share verifiable proof of data and/or identity information, and businesses are able to request, consume, and act on the data—all without a data storage server or those businesses ever seeing or having access to the raw sensitive information (where server-stored data is viewable only by the intended recipients, which may even be selected after storage). In one embodiment, source data is encrypted with a source encryption key (e.g., source public key), with a rekeying key being an encrypting combination of a source decryption key (e.g., source private key) and a recipient's public key. Without being able to decrypt the data, the storage server can use the rekeying key to re-encrypt the source data with the recipient's public key, to then be decrypted only by the corresponding recipient using its private key, accordingly.

## Claims

### Claim 1

A method for performing a transaction between a first party and a second party, the method comprising:
storing, by a third party service, first party identifying information, wherein the first party identifying information is inaccessible by any party other than the first party;
obtaining, by the third party service, first account information of a first account corresponding to the first party;
obtaining, by the third party service, second account information of a second account corresponding to the second party;
obtaining, by the third party service, a value to transfer from the first account to the second account as the transaction;
obtaining, by the third party service, verified approval of the first party to complete the transaction; and
instructing, by the third party service in response to the verified approval of the first party, an account-maintaining entity associated with the first account to complete the transaction without sharing the first party identifying information or the first account information with the second party.

### Claim 2 (depends on 1)

The method as in claim 1, wherein the transaction is a financial transaction and the value is monetary.

### Claim 3 (depends on 1)

The method as in claim 1, further comprising:
sharing, by the third party service, the first party identifying information with a regulatory party in response to an authorized trigger, wherein the first party identifying information is converted into a format accessible only to the regulatory party.

### Claim 4 (depends on 1)

The method as in claim 1, wherein the first party identifying information comprises personally identifying information (PII) and the authorized trigger comprises a value greater than a threshold value.

### Claim 5 (depends on 1)

The method as in claim 1, wherein the third party does not have access to the first party identifying information.

### Claim 6 (depends on 1)

The method as in claim 1, wherein the first party identifying information is attested to by an attestation service.

### Claim 7 (depends on 1)

The method as in claim 1, wherein the first party is a buyer of an item and the second party is a seller of the item.

### Claim 8 (depends on 7)

The method as in claim 7, wherein the third party service and account-maintaining entity are unaware of the item.

### Claim 9 (depends on 1)

The method as in claim 1, further comprising:
storing an invoice for the transaction at the third party service without the third party service having access to read the transaction record.

### Claim 10 (depends on 9)

The method as in claim 9, wherein the first party can read the transaction record.

### Claim 11 (depends on 1)

The method as in claim 1, further comprising:
obtaining, by the third party service, a conversion key specific to the particular recipient from the first party;
obtaining, by the third party service, a request to share the first party identifying information with a particular recipient;
converting, by the third party service based on the conversion key, the first party identifying information into a format readable only by the particular recipient; and
sending, from the third party service, the first party identifying information in the format readable only by the particular recipient to the particular recipient.

### Claim 12 (depends on 1)

The method as in claim 1, further comprising:
obtaining, by the third party service, source-encrypted first party identifying information from the first party, the source-encrypted first party identifying information comprising first party identifying information encrypted by the first party with a source encryption key of the first party, wherein the third party service is unable to decrypt the source-encrypted first party identifying information;
storing, by the third party service, the source-encrypted first party identifying information;
obtaining, by the third party service, a recipient-based rekeying key from the first party, the recipient-based rekeying key established through an encrypting combination of a first party decryption key of the first party and a recipient public key of a particular recipient;
receiving, by the third party service, a request to share the first party identifying information with the particular recipient;
re-encrypting, by the third party service, the source-encrypted first party identifying information with the recipient-based rekeying key, the re-encrypting resulting in recipient-based encrypted first party identifying information that is the first party identifying information encrypted with the recipient public key of the particular recipient, wherein the third party service is unable to decrypt the recipient-based encrypted first party identifying information; and
sending, by the third party service, the recipient-based encrypted first party identifying information to the particular recipient to cause the particular recipient to decrypt the recipient-based encrypted first party identifying information using a recipient private key of the particular recipient to obtain the first party identifying information.

### Claim 13 (depends on 1)

The method as in claim 1, wherein the third party service maintains the first account information prior to initiating transactions.

### Claim 14 (depends on 1)

The method as in claim 1, wherein the third party service obtains the second account information in response to initiation of the transaction.

### Claim 15 (depends on 1)

The method as in claim 1, wherein the transaction is performed on a device of the first party.

### Claim 16 (depends on 1)

The method as in claim 1, wherein the transaction is performed as a joint collaboration between a device of the first party and a device of the second party.

### Claim 17 (depends on 16)

The method as in claim 16, wherein the transaction is initiated on the device of the second party, and wherein the device of the first party provides the verified approval of the first party to complete the transaction to the third party service.

### Claim 18 (depends on 17)

The method as in claim 17, wherein the device of the first party is selected from a group consisting of: a smartphone; a tablet; and a memory device.

### Claim 19 (depends on 1)

The method as in claim 1, further comprising:
storing, by the third party service, second party identifying information, wherein the second party identifying information is inaccessible by any party other than the second party; and
sharing the second party identifying information with a regulatory party in response to an authorized trigger, wherein the second party identifying information is converted into a format only accessible to the regulatory party.

### Claim 20 (depends on 1)

The method as in claim 1, wherein the transaction is a loyalty program transaction or a marketing campaign transaction, or both.
