US 12,457,123 B2
Secure key and transaction management for multi-party computation systems
Miles Robert Parry, Croydon (GB); Cat-Tuong Le-Huy, London (GB); and Olaf Stelling, Florence (IT)
Assigned to MPC Holding, Inc., Concord, NH (US)
Filed by MPC Holding, Inc., New York, NY (US)
Filed on Mar. 4, 2024, as Appl. No. 18/594,191.
Claims priority of provisional application 63/509,017, filed on Jun. 19, 2023.
Claims priority of provisional application 63/449,876, filed on Mar. 3, 2023.
Prior Publication US 2024/0296445 A1, Sep. 5, 2024
Int. Cl. H04L 9/00 (2022.01); G06Q 20/06 (2012.01); G06Q 20/36 (2012.01); G06Q 20/38 (2012.01); G06Q 20/40 (2012.01); H04L 9/32 (2006.01)
CPC H04L 9/50 (2022.05) [G06Q 20/3674 (2013.01); G06Q 20/3825 (2013.01); G06Q 20/3829 (2013.01); H04L 9/3247 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A method for managing, authenticating, and authorizing transactions utilizing multi-party-computation (“MPC”) across a network, the method comprising:
receiving, by a server and from a primary client device, policy data that defines a transaction signing policy, wherein the policy data comprises (i) a designation of a transaction signing group, (ii) a designation of a plurality of virtual nodes in a cloud environment that are included in the transaction signing group, and (iii) for each transaction class of a plurality of transaction classes, a corresponding threshold number of the plurality of virtual nodes that is required to authorize a transaction request, wherein the transaction request is a member of the transaction class;
receiving, by the server and from an initiator node, the transaction request, wherein the transaction request includes a transaction parameter that indicates a transaction class of the transaction that is a member of the plurality of transaction classes;
in response to receiving the transaction request:
(i) determining, by the server and based on the transaction parameter and the transaction signing policy, a threshold number of virtual nodes amongst the plurality of virtual nodes that are included in the transaction signing group that are required to authorize the transaction request, and
(ii) sending, by the server and to each of the plurality of virtual nodes that are included in the transaction signing group, an authorization request for each of the plurality of virtual nodes that are included in the transaction signing group to authorize the transaction request;
receiving, by the server and from at least a subset of the plurality of virtual nodes that are included in the transaction signing group, authorization data indicating that the transaction request has been authorized by the respective virtual node; and
based on a determination that the authorization data is collected from a number of the plurality of virtual nodes that are included in the transaction signing group that satisfies the threshold number of virtual nodes required to authorize the transaction request, returning, by the server and to a hardware security module (HSM), a transaction payload.