Method for user management for blockchain-based operations

Patent metadata

Field	Value
Publication number	US-11410168-B2
Application number	US-201916374084-A
Country	US
Kind code	B2
Filing date	Apr 3, 2019
Priority date	Apr 3, 2019
Publication date	Aug 9, 2022
Grant date	Aug 9, 2022

Abstract

Systems and methods are provided for generating a blockchain smart contract for managing user accounts and electronic wallets storing cryptocurrency. The described system includes determining a public encryption key associated with a third-party organization configured to manage blockchain transactions on behalf of a first user account, generating a first transaction data structure having a destination address field that specifies a user-account smart contract module published to a distributed ledger, wherein the first transaction data structure is configured to invoke change ownership functionality of the user-account smart contract module using the determined public encryption key associated with the third-party organization, and publishing the first transaction data structure to the distributed ledger maintained by the blockchain network of nodes.

First claim

What is claimed is:

1. A method for executing a blockchain-based transaction for transferring ownership of a user account from a first third-party organization to a second third-party organization, the method comprising:
determining a public encryption key of the second third-party organization that is comprised of a server system with a blockchain client configured to manage blockchain transactions on behalf of a plurality of user accounts;
generating a first transaction data structure having a destination address field that specifies a user-account smart contract module published to a distributed ledger,
wherein the first transaction data structure is configured to invoke change ownership functionality of the user-account smart contract module, and wherein the change ownership functionality transfers, using the determined public encryption key of the second third-party organization, the ownership of the user account to the second third-party organization without transferring a copy of a private encryption key of the user account to the second third-party organization; and
publishing the first transaction data structure to the distributed ledger maintained by a blockchain network of nodes.

2. The method of claim 1 , wherein the user-account smart contract module comprises computer-executable instructions configured to execute, at a server-side node of the blockchain network, the change ownership functionality that modifies an internal data store associated with the user-account smart contract module to store an account identifier derived from the public encryption key associated with the second third-party organization.

3. The method of claim 1 , wherein the user-account smart contract module is assigned a contract address within the distributed ledger, and wherein the destination address field of the first transaction data structure is set to the contract address.

4. The method of claim 1 , further comprising:
generating a second transaction data structure for transferring cryptographic assets from the user account to second target account using a token smart contract module published to the distributed ledger, wherein the second transaction data structure comprises a second destination address field that specifies the user-account smart contract module.

5. The method of claim 4 , wherein the second transaction data structure further comprises a source address field that contains an account identifier derived from the public encryption key of the second third-party organization, and a data field that comprises invocation of execute functionality of the user-account smart contract module using a first parameter and a second parameter,
wherein the first parameter comprises a contract address of the token smart contract module, and the second parameter comprises an invocation of transfer functionality of the token smart contract module.

6. The method of claim 5 , wherein the execute functionality of the user-account smart contract module is further configured to verify that an account invoking the execute functionality matches an owner identifier stored by the user-account smart contract module.

7. The method of claim 5 , wherein the transfer functionality of the token smart contract module is configured to check that an account invoking the transfer functionality is authorized based on a public key recovery of a plurality of digital signature values associated with the account.

8. The method of claim 4 , wherein the second transaction data structure causes the token smart contract module to generate a third transaction data structure to transfer the cryptographic assets from the user account to the second target account such that the user account is represented by the user-account smart contract module in a source portion of the third transaction data structure and not a user account address.

9. A system for executing a blockchain-based transaction for transferring ownership of a user account from a first third-party organization to a second third-party organization, the system comprising:
a memory; and
a hardware processor coupled to the memory and configured to:
determine a public encryption key of the second third-party organization that is comprised of a server system with a blockchain client configured to manage blockchain transactions on behalf of a plurality of user accounts;
generate a first transaction data structure having a destination address field that specifies a user-account smart contract module published to a distributed ledger,
wherein the first transaction data structure is configured to invoke change ownership functionality of the user-account smart contract module, and wherein the change ownership functionality transfers, using the determined public encryption key of the second third-party organization, the ownership of the user account to the second third-party organization without transferring a copy of a private encryption key of the user account to the second third-party organization; and
publish the first transaction data structure to the distributed ledger maintained by a blockchain network of nodes.

10. The system of claim 9 , wherein the user-account smart contract module comprises computer-executable instructions configured to execute, at a server-side node of the blockchain network, the change ownership functionality that modifies an internal data store associated with the user-account smart contract module to store an account identifier derived from the public encryption key associated with the second third-party organization.

11. The system of claim 9 , wherein the user-account smart contract module is assigned a contract address within the distributed ledger, and wherein the destination address field of the first transaction data structure is set to the contract address.

12. The system of claim 9 , wherein the processor is further configured to generate a second transaction data structure for transferring cryptographic assets from the user account to second target account using a token smart contract module published to the distributed ledger, wherein the second transaction data structure comprises a second destination address field that specifies the user-account smart contract module.

13. The system of claim 12 , wherein the second transaction data structure further comprises a source address field that contains an account identifier derived from the public encryption key of the second third-party organization, and a data field that comprises invocation of execute functionality of the user-account smart contract module using a first parameter and a second parameter,
wherein the first parameter comprises a contract address of the token smart contract module, and the second parameter comprises an invocation of transfer functionality of the token smart contract module.

14. The system of claim 13 , wherein the execute functionality of the user-account smart contract module is further configured to verify that an account invoking the execute functionality matches an owner identifier stored by the user-account smart contract module.

15. The system of claim 13 , wherein the transfer functionality of the token smart contract module is configured to check that an account invoking the transfer functionality is authorized based on a public key recovery of a plurality of digital signature values associated with the account.

16. The system of claim 12 , wherein the second transaction data structure causes the token smart contract module to generate a third transaction data structure to transfer the cryptographic assets from the first user account to the second target accou

Assignees

• Acronis Int Gmbh

Inventors

• Lyadvinsky Max
• Raevsky Alexey
• Petrushkin Anton

Classifications

• G06Q2220/00

  Business processing using cryptography · CPC title

• G06Q20/389

  Keeping log of transactions for guaranteeing non-repudiation of a transaction · CPC title

• H04L9/50

  using hash chains, e.g. blockchains or hash trees · CPC title

• G06Q20/223

  based on the use of peer-to-peer networks · CPC title

• G06Q20/3829 Primary

  involving key management · CPC title