# US 11,308,484 B2 · System and method for secure storage of digital currencies and making transactions in a blockchain network

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

- Number: US 11,308,484 B2
- Document ID: US11308484B2
- Status: Granted
- Kind: B2
- Application number: 16/975,796
- Filed: 2019-02-08
- Published: 2021-12-09
- Granted: 2022-04-19
- Earliest claimed: 2019-02-08
- Applicants: Aleksey Sergeevich Smirnov
- Inventors: Aleksey Sergeevich Smirnov
- Web page: https://patentgrep.com/patent/US11308484B2

## CPC

- G06Q 20/3674: {involving authentication}
- H04L 9/0897: {involving additional devices, e.g. trusted platform module [TPM], smartcard or USB}
- G06F 21/74: operating in dual or compartmented mode, i.e. at least one secure mode
- G06Q 20/02: involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
- G06Q 20/065: {using e-cash}
- G06Q 20/367: {involving electronic purses or money safes}
- G06Q 20/3825: {Use of electronic signatures}
- G06Q 20/3829: {involving key management}
- G06Q 20/389: {Keeping log of transactions for guaranteeing non-repudiation of a transaction}
- G06Q 20/401: {Transaction verification}
- G06Q 20/4014: {Identity check for transactions}
- G06Q 20/405: {Establishing or using transaction specific rules}
- H04L 9/0894: {Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage}
- H04L 9/3234: {involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token (network architectures or network communication protocols for supporting authentication of entities using an additional device in a packet data network H04L63/0853)}
- H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- H04L 9/3247: {involving digital signatures}
- H04L 9/3255: {using group based signatures, e.g. ring or threshold signatures}
- H04L 63/0838: {using one-time-passwords}
- H04L 63/0861: {using biometrical features, e.g. fingerprint, retina-scan (cryptographic mechanisms or cryptographic arrangements for entity authentication using biological data H04L9/3231)}
- H04L 63/126: {the source of the received data}
- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- G06Q 20/3278: {RFID or NFC payments by means of M-devices}
- G06Q 20/385: {using an alias or single-use codes}
- G06Q 20/40145: {Biometric identity checks}
- G06Q 2220/00: Business processing using cryptography
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L 2209/56: Financial cryptography, e.g. electronic payment or e-cash
- H04L 2209/805: Lightweight hardware, e.g. radio-frequency identification [RFID] or sensor
- H04L 2463/082: applying multi-factor authentication
- 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
- 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)

## Abstract

The claimed solution relates to a method of making transactions in the blockchain framework using a protected hardware and software complex to ensure secure storage of digital currencies (cryptocurrencies) and control the entire lifecycle of multiple wallets simultaneously to make transactions in the blockchain network. Basic features of the hardware and software complex include the effective control over the entire life cycle of cold wallets, generation of digital wallets and secure storage of their private keys in an isolated environment using the hardware security modules (HSM), as well as maintaining the multiple level authentication of blockchain transactions. It is possible to use all the features of the complex due to compatibility with the application programming interface (API), which enables to integrate the complex into the existing software solutions, for example, banking systems.

## Claims

### Claim 1

A system for secure storage of digital currencies, processing and executing transactions in at least one blockchain network, wherein system contains
a server connected to at least one blockchain network and the server providing a life-cycle management of a digital wallets of users, tracking and validation of an incoming transactions, generation and primary validation of the transactions in the at least one blockchain network, wherein the server contains
an administrator module, which is configured to create an accounts for administrators and users, manage an administrator rights which allow to set limits for withdrawal of the digital currencies from digital wallets and approve an incoming transactions, and users rights, which allow to set a transaction multisignature rules and a transaction confirmation rules, view statistics on the digital wallets of users;
a user module, which is configured to
create the digital wallets of users, assign the multisignature rules for transactions and the transaction confirmation rules by users for each created digital wallet, wherein
the transaction multisignature rules include one of the following: M of N signatures, a signature from multiple groups, or a signature from multiple groups with a quorum within a group, or transaction confirmation time period after which the transaction is rejected;
the confirmation rules include at least of the following: a hyperlink, a code, a one-time password, a biometric identification, a confirmation step using a hardware token or a cryptographic signature;
process a user requests depending on the confirmation rules assigned to the digital wallet;
assign a multi-factor authentication methods by users;
a database, that stores an information about addresses of digital wallets, transactions, an administrators and users accounts, rights of administrators and users, an authentication data, the transaction multisignature rules and transaction confirmation rules for created digital wallets;
at least one hardware security module (HSM), which is connected to the server, wherein HSM provides
an isolated environment to create and maintain the full life-cycle management of the digital wallets;
a secure storage of private keys of the digital wallets;
a storage of the authentication data of administrators and users;
supporting a process of sending addresses of digital wallets to the server;
validation of transactions, signing of a confirmed transactions;
transfer confirmed transactions to the server.

### Claim 2 (depends on 1)

The system according to claim 1, wherein the multisignature rules are set at creating process of the digital wallet of user.

### Claim 3 (depends on 1)

The system according to claim 1, wherein the hardware token is a smart card, USB, or NFC token.

### Claim 4 (depends on 1)

The system according to claim 1, wherein when processing the transaction for the digital wallet the server performs an initial verification for compliance with the multisignature and confirmation rules for the digital wallet to approve the transaction.

### Claim 5 (depends on 4)

The system according to claim 4, wherein upon receipt of a request for the transaction via the digital wallet, the server, using the authentication data, performs the initial verification of signatures of all users assigned in the multisignature rules for the digital wallet.

### Claim 6 (depends on 5)

The system according to claim 5, wherein after validation of the request for transaction the server collects a primary information about the digital wallet in the blockchain network and generates a raw transaction on its basis, which is saved in the database.

### Claim 7 (depends on 1)

The system according to claim 1, wherein for each signature a weight coefficients and a threshold values are set for each of the groups, and the threshold value must be exceeded by the sum of the weights of all signers in the group to confirm the transaction.

### Claim 8 (depends on 6)

The system according to claim 6, wherein after validation of the transaction and initial verification of all signatures, the control server transmits the transaction data and signatures to the HSM.

### Claim 9 (depends on 8)

The system according to claim 8, wherein by the authentication data the HSM checks the incoming raw transactions from the server for the validity of the signatures that were used to confirm the transaction, and in case of successful verification, signs the raw transactions using the private key of the digital wallet corresponding to this transaction.

### Claim 10 (depends on 9)

The system according to claim 9, wherein after signing of the raw transaction the HSM transfers the signed transaction to the server for its subsequent transfer to the blockchain network.

### Claim 11

A transaction execution method using a digital currency in a blockchain network, comprising the following steps:
receiving a request on a server to create a digital wallet to make a transactions using digital currency, wherein server comprises an administrator module, which is configured to create an accounts for administrators and users, manage an administrator rights which allow to set limits for withdrawal of the digital currencies from digital wallets and approve an incoming transactions, and users rights, which allow to set a transaction multisignature rules and a transaction confirmation rules, view statistics on the digital wallets of users; the request comprises the transaction multisignature rules and the transaction confirmation rules, which is created by users for the digital wallet, wherein
the multisignature rules include an authentication data of users assigned to sign the transactions and at least one of the following: M of N signatures, a signature from multiple groups, or a signature from multiple groups with a quorum within a group, or transaction confirmation time period after which the transaction is rejected;
the transaction confirmation rules include at least of the following: a hyperlink, a code, an one-time password, a biometric identification, a confirmation step using a hardware token or a cryptographic signature;
verifying users rights and the multisignature rules of the request for creation of the digital wallet using the authentication data of users;
signing the request for creation of the digital wallet;
transferring the request for creation of the digital wallet to a hardware security module (HSM), wherein user's digital wallet is created by generating a private and public keys of the digital wallet at the HSM and the private and public keys of the digital wallet and the authentication data of users assigned to sign transactions on the created digital wallet are saved in the HSM;
transmitting and save the public key of the created digital wallet and the authentication data of users assigned to sign transactions on the created digital wallet in a database of the server;
receiving a request on the server to execute a transaction by one of the created digital wallets;
collecting on the server a primary data of the digital wallet in the blockchain network;
generating and saving on the server a raw transaction based on the primary data;
confirming the raw transaction by all users using the transaction multisignature rules and transaction confirmation rules for the digital wallet;
checking a confirmation of the transaction by the server, the raw transaction and signatures of the users confirming the transaction;
transmitting confirmed transaction to the HSM;
verifying the transaction confirmation rules by each user signed the confirmed transaction, wherein the multisignature rules of the raw transaction are verified on the HSM by the authentication data, and whether verification is successful the raw transaction is signed using the private key of the digital wallet whereby the transaction was initiated;
transferring the signed transaction to the server for its further transfer to the blockchain network.

### Claim 12 (depends on 11)

The method according to claim 11, wherein the user account enables at least one of the following: initiate transactions, approve and reject transactions, veto transactions for a specified period of time after the transaction has been proposed, create digital wallets.

### Claim 13 (depends on 11)

The method according to claim 11, wherein for each signature a weight coefficients and threshold values are set for each of the groups, and the threshold value must be exceeded by the sum of the weights of all signers in the group to confirm the transaction.

### Claim 14 (depends on 11)

The method according to claim 11, wherein for each initiated transaction a time period is set within which the transaction can be vetoed.

### Claim 15 (depends on 11)

The method according to claim 11, wherein the HSM is implemented with a real-time data replication function, which is performed using one or more redundant HSMs.