US 12,225,127 B2Granted

Address verification, seed splitting and firmware extension for secure cryptocurrency key backup, restore, and transaction signing platform apparatuses, methods and systems

AssigneeFmr LLC

InventorsVladimir Tsitrin, Gang Cheng

Life of this patent

Estimating the term…

Loading patent…

Abstract

The Address Verification, Seed Splitting and Firmware Extension for Secure Cryptocurrency Key Backup, Restore, and Transaction Signing Platform Apparatuses, Methods and Systems (“SFTSP”) transforms contract deployment request, transaction signing request, key backup request, key recovery request inputs via SFTSP components into contract deployment response, transaction signing response, key backup response, key recovery response outputs. A contract deployment request message datastructure is obtained. Owner key identification parameters are determined. An owner public key is determined using the owner key identification parameters. An owner address is generated using the owner public key. A salt value is generated. A contract address for the smart contract is calculated as a function of the deployment factory address, the salt value, the contract code, and the owner address. An owner private key is determined using the owner key identification parameters and used to sign the contract address. A contract deployment data datastructure is provided.

Claims13

Dependent claims

A verified address smart contract deploying apparatus, comprising:

at least one memory;
a component collection stored in the at least one memory;
at least one processor disposed in communication with the at least one memory, the at least one processor executing processor-executable instructions from the component collection, the component collection storage structured with processor-executable instructions, comprising:
obtain, via the at least one processor, a contract deployment request message datastructure by a hardware security module (HSM) from a transaction signing server (TSS), in which the contract deployment request message datastructure is structured to specify a set of owner datastructures, a deployment factory address, and contract code for a smart contract;
determine, via the at least one processor, by the HSM, owner key identification parameters associated with an owner datastructure in the set of owner datastructures, in which the owner key identification parameters are structured to specify a keyset identifier and a keychain path;
determine, via the at least one processor, by the HSM, an owner public key associated with the owner datastructure using the owner key identification parameters;
generate, via the at least one processor, by the HSM, an owner address associated with the owner datastructure using the owner public key;
generate, via the at least one processor, by the HSM, a salt value for the smart contract;
calculate, via the at least one processor, by the HSM, a contract address for the smart contract as a function of the deployment factory address, the salt value, the contract code, and the owner address;
determine, via the at least one processor, by the HSM, an owner private key associated with the owner datastructure using the owner key identification parameters, in which the owner private key corresponds to the owner public key;
sign, via at least one processor, by the HSM, the contract address for the smart contract using the owner private key to generate a contract deployment signature;
and
provide, via at least one processor, by the HSM, a contract deployment data datastructure to the TSS, in which the contract deployment data datastructure is structured to specify the salt value, and the contract deployment signature.

10 more elements

A verified address smart contract deploying processor-readable, non-transient medium, the medium storing a component collection, the component collection storage structured with processor-executable instructions comprising:

obtain, via at least one processor, a contract deployment request message datastructure by a hardware security module (HSM) from a transaction signing server (TSS), in which the contract deployment request message datastructure is structured to specify a set of owner datastructures, a deployment factory address, and contract code for a smart contract;
determine, via the at least one processor, by the HSM, owner key identification parameters associated with an owner datastructure in the set of owner datastructures, in which the owner key identification parameters are structured to specify a keyset identifier and a keychain path;
determine, via the at least one processor, by the HSM, an owner public key associated with the owner datastructure using the owner key identification parameters;
generate, via the at least one processor, by the HSM, an owner address associated with the owner datastructure using the owner public key;
generate, via the at least one processor, by the HSM, a salt value for the smart contract;
calculate, via the at least one processor, by the HSM, a contract address for the smart contract as a function of the deployment factory address, the salt value, the contract code, and the owner address;
determine, via the at least one processor, by the HSM, an owner private key associated with the owner datastructure using the owner key identification parameters, in which the owner private key corresponds to the owner public key;
sign, via at least one processor, by the HSM, the contract address for the smart contract using the owner private key to generate a contract deployment signature;
and
provide, via at least one processor, by the HSM, a contract deployment data datastructure to the TSS, in which the contract deployment data datastructure is structured to specify the salt value, and the contract deployment signature.

7 more elements

A verified address smart contract deploying processor-implemented system, comprising:

memory configured to store a component collection;
at least one processor implemented in hardware configured to process processor-executable instructions from the component collection, the component collection storage structured with processor-executable instructions including:
obtain, via the at least one processor, a contract deployment request message datastructure by a hardware security module (HSM) from a transaction signing server (TSS), in which the contract deployment request message datastructure is structured to specify a set of owner datastructures, a deployment factory address, and contract code for a smart contract;
determine, via the at least one processor, by the HSM, owner key identification parameters associated with an owner datastructure in the set of owner datastructures, in which the owner key identification parameters are structured to specify a keyset identifier and a keychain path;
determine, via the at least one processor, by the HSM, an owner public key associated with the owner datastructure using the owner key identification parameters;
generate, via the at least one processor, by the HSM, an owner address associated with the owner datastructure using the owner public key;
generate, via the at least one processor, by the HSM, a salt value for the smart contract;
calculate, via the at least one processor, by the HSM, a contract address for the smart contract as a function of the deployment factory address, the salt value, the contract code, and the owner address;
determine, via the at least one processor, by the HSM, an owner private key associated with the owner datastructure using the owner key identification parameters, in which the owner private key corresponds to the owner public key;
sign, via at least one processor, by the HSM, the contract address for the smart contract using the owner private key to generate a contract deployment signature;
and
provide, via at least one processor, by the HSM, a contract deployment data datastructure to the TSS, in which the contract deployment data datastructure is structured to specify the salt value, and the contract deployment signature.

9 more elements

A verified address smart contract deploying processor-implemented process, including processing processor-executable instructions via at least one processor from a component collection stored in at least one memory, the component collection storage structured with processor-executable instructions comprising:

obtain, via the at least one processor, a contract deployment request message datastructure by a hardware security module (HSM) from a transaction signing server (TSS), in which the contract deployment request message datastructure is structured to specify a set of owner datastructures, a deployment factory address, and contract code for a smart contract;
determine, via the at least one processor, by the HSM, owner key identification parameters associated with an owner datastructure in the set of owner datastructures, in which the owner key identification parameters are structured to specify a keyset identifier and a keychain path;
determine, via the at least one processor, by the HSM, an owner public key associated with the owner datastructure using the owner key identification parameters;
generate, via the at least one processor, by the HSM, an owner address associated with the owner datastructure using the owner public key;
generate, via the at least one processor, by the HSM, a salt value for the smart contract;
calculate, via the at least one processor, by the HSM, a contract address for the smart contract as a function of the deployment factory address, the salt value, the contract code, and the owner address;
determine, via the at least one processor, by the HSM, an owner private key associated with the owner datastructure using the owner key identification parameters, in which the owner private key corresponds to the owner public key;
sign, via at least one processor, by the HSM, the contract address for the smart contract using the owner private key to generate a contract deployment signature;
and
provide, via at least one processor, by the HSM, a contract deployment data datastructure to the TSS, in which the contract deployment data datastructure is structured to specify the salt value, and the contract deployment signature.

7 more elements

Dependencies are inferred from the claim text.

Facts

Application: 17/719,344Filed 12 Apr 2022 · continuation in part
Priority: 14 Jul 2015
Published: US 2022/0321340 A16 Oct 2022
Granted: 11 Feb 2025
Term ends: Not estimatedThe source records don’t support an estimate.

Classification14 codes

G06F 21/64
Protecting data: protecting data integrity, e.g. using checksums, certificates or signatures
H04L 9/0894
Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords: escrow, recovery or storing of secret…
G06F 21/602
Protecting data: providing cryptographic facilities or services
G06F 21/6218
Protecting access to data via a platform, e.g. using keys or access control rules: to a system of files or objects, e.g. local or distributed file…

Family

Application14/799,229Parent of this continuation-in-part · filed 14 Jul 2015
Application14/799,242Parent of this continuation-in-part · filed 14 Jul 2015
Application14/799,282Parent of this continuation-in-part · filed 14 Jul 2015
Application14/963,165Parent of this continuation-in-part · filed 8 Dec 2015
Application62/273,450Us provisional application · filed 31 Dec 2015
Application62/273,452Us provisional application · filed 31 Dec 2015
Application62/273,449Us provisional application · filed 31 Dec 2015
Application62/273,447Us provisional application · filed 31 Dec 2015
Application62/273,453Us provisional application · filed 31 Dec 2015
Application15/019,926Parent of this continuation-in-part · filed 9 Feb 2016
Application15/209,709Parent of this continuation-in-part · filed 13 Jul 2016
Application15/209,714Parent of this continuation-in-part · filed 13 Jul 2016
Application15/209,701Parent of this continuation-in-part · filed 13 Jul 2016
PCT/US2016/042169Parent of this continuation-in-part · filed 13 Jul 2016
Application15/210,813Parent of this continuation-in-part · filed 14 Jul 2016
Application15/210,781Parent of this continuation-in-part · filed 14 Jul 2016
Application15/210,807Parent of this continuation-in-part · filed 14 Jul 2016
Application15/210,817Parent of this continuation-in-part · filed 14 Jul 2016
Application15/210,795Parent of this continuation-in-part · filed 14 Jul 2016
Application15/210,821Parent of this continuation-in-part · filed 14 Jul 2016
Application15/456,461Parent of this continuation-in-part · filed 10 Mar 2017
Application15/486,243Parent of this continuation-in-part · filed 12 Apr 2017
Application62/509,011Us provisional application · filed 19 May 2017
Application15/898,224Parent of this continuation-in-part · filed 15 Feb 2018
Application15/984,280Parent of this continuation-in-part · filed 18 May 2018
Application16/421,442Parent of this continuation-in-part · filed 23 May 2019
US 2022/0321340 A1Pre-grant publication · published 6 Oct 2022
US 10,992,469 B2Parent of this continuation-in-part
US 10,778,439 B2Parent of this continuation-in-part
US 10,644,885 B2Parent of this continuation-in-part
US 11,488,147 B2Parent of this continuation-in-part
US 10,461,940 B2Parent of this continuation-in-part
US 10,339,523 B2Parent of this continuation-in-part
US 10,504,179 B1Parent of this continuation-in-part
US 2017/0017936 A1Published application
US 2017/0017954 A1Published application
US 2017/0017955 A1Published application
US 2017/0046689 A1Published application
US 2017/0048209 A1Published application
US 2017/0048234 A1Published application
US 2017/0048235 A1Published application
US 2017/0083907 A1Published application
US 2017/0085545 A1Published application
US 2017/0085555 A1Published application
US 2017/0091756 A1Published application
US 2017/0109735 A1Published application
US 2017/0221052 A1Published application
US 2017/0228731 A1Published application
US 2018/0176013 A1Published application
US 2018/0262341 A1Published application
US 2018/0367316 A1Published application
US 2019/0280864 A1Published application
US 12,225,127 B2This patent

From the US filing history. Foreign family members aren’t listed.

Timeline

Citations

Open elsewhere

Building an agent or pulling many patents? Use the API or MCP server instead of scraping pages. Get an API key