The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.

The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.

Date of Patent:
Apr. 28, 2026

Filed:

Aug. 11, 2023
Applicant:

Nasdaq, Inc., New York, NY (US);

Inventors:

Shankar Raju, Harrison, NJ (US);

Jiayue Chen, Austin, TX (US);

Assignee:

Nasdaq, Inc., New York, NY (US);

Attorney:
Primary Examiner:
Assistant Examiner:
Int. Cl.
CPC ...
H04L 9/08 (2006.01); H04L 9/00 (2022.01); H04L 9/32 (2006.01);
U.S. Cl.
CPC ...
H04L 9/0894 (2013.01); H04L 9/0825 (2013.01); H04L 9/3247 (2013.01); H04L 9/50 (2022.05);
Abstract

A system includes a primary asset custody subsystem in a first cloud computing data center and a backup asset custody subsystem in a second cloud computing data center different from the first cloud computing data center. The primary subsystem includes a plurality of primary multi-party computation (MPC) clusters, where each primary MPC cluster is allocated to an asset owner and includes a primary MPC client and a plurality of primary MPC nodes. The backup subsystem includes a plurality of backup MPC clusters corresponding to the plurality of primary MPC clusters, where each backup MPC cluster is allocated to the asset owner of its corresponding primary MPC cluster and includes a backup MPC client and a plurality of backup MPC nodes. The backup MPC client sends an export public key from each backup MPC node to the primary MPC client, where each export public key is part of a corresponding export public key-export private key pair. The primary MPC client sends each export public key to a corresponding primary MPC node, and in response, receives from each primary MPC node a corresponding encrypted private key share encrypted with a corresponding export public key. The primary MPC client then sends the encrypted private key shares to the backup MPC client, which transmits the encrypted private key shares to corresponding backup MPC nodes. Each backup MPC node decrypts a corresponding encrypted private key share using the export private key from the corresponding export public key-export private key pair to obtain a corresponding backup private key share which can be used if the backup subsystem takes over operation, and to store the decrypted corresponding backup private key share.


Find Patent Forward Citations

Loading…