Cryptocurrency aggregation system

Patent metadata

Field	Value
Publication number	US-10127552-B2
Application number	US-201414305981-A
Country	US
Kind code	B2
Filing date	Jun 16, 2014
Priority date	Jun 16, 2014
Publication date	Nov 13, 2018
Grant date	Nov 13, 2018

Abstract

A system includes a memory and a processor. The memory may store a customer account associated with a customer and an enterprise account associated with an enterprise. The processor may be communicatively coupled to the memory and may cause the system to receive a request to deposit a first amount of a cryptocurrency in the customer account from the customer. The processor may also cause the system to determine a public key associated with the customer account and receive the first amount of the cryptocurrency. The processor may further cause the system to determine a first value approximately equivalent to the first amount of cryptocurrency and associate the first value with the customer account. The processor is further able to aggregate the first amount of cryptocurrency with an aggregated amount of the cryptocurrency in the enterprise account and facilitate securing the public key in the enterprise account.

First claim

What is claimed is:

1. A system comprising:
a memory operable to:
store a customer account associated with a customer;
store an enterprise account associated with an enterprise; and

a processor communicatively coupled to the memory, the memory including executable instructions that upon execution by the processor cause the system to:
receive a first request to deposit a first amount of a cryptocurrency in the customer account and store a private key associated with the customer account from the customer;
determine a public key associated with the customer account;
receive, based at least in part upon the first request and the public key, the first amount of the cryptocurrency;
determine a first value approximately equivalent to the first amount of cryptocurrency;
associate the first value with the customer account;
aggregate the first amount of the cryptocurrency with an aggregated amount of the cryptocurrency in the enterprise account;
secure the public key in the enterprise account; and
secure the private key, wherein securing the private key comprises:
selecting a first hash function based on a first location of a first data center;
selecting a second hash function based on a second location of a second data center;
applying the first hash function to at least a portion of the private key to generate a first vault key, wherein applying the first hash function obfuscates the private key to generate the first vault key;
storing information associated with recovering the private key based on the first vault key;
applying the second hash function to at least a portion of the private key to generate a second vault key, wherein applying the second hash function obfuscates the private key to generate the second vault key;
storing information associated with recovering the private key based the second vault key;
storing the first vault key at the first data center; and
storing the second vault key at the second data center.

2. The system of claim 1 , the memory further including executable instructions that upon execution cause the system to:
receive a second request to withdraw a second amount of the cryptocurrency from the customer account from the customer;
determine a second value approximately equivalent to the second amount of the cryptocurrency to the customer account;
withdraw the second amount of the cryptocurrency from the enterprise account; and
transfer the second amount of the cryptocurrency to the customer.

3. The system of claim 1 , the memory further including executable instructions that upon execution cause the system to:
communicate, in response to securing the public key and the private key, a confirmation confirming the public key and the private key are secure to the customer.

4. The system of claim 1 , the memory further including executable instructions that upon execution cause the system to determine that the customer authorized the first request.

5. The system of claim 1 , wherein the customer account is associated with a cryptocurrency account.

6. The system of claim 1 , wherein:
the public key is a first public key;
the memory further including executable instructions that upon execution cause the system to determine a second public key associated with the enterprise account; and
aggregating the first amount of cryptocurrency with the aggregated amount of the cryptocurrency in the enterprise account is based at least in part upon the second public key.

7. The system of claim 1 , wherein the first value is determined based at least in part upon a price associated with the cryptocurrency.

8. A method comprising:
storing, using a processor, a customer account associated with a customer;
storing, using the processor, an enterprise account associated with an enterprise; and
receiving, at a network interface, a first request to deposit a first amount of a cryptocurrency in the customer account and store a private key associated with the customer account from the customer;
determining, by an aggregation engine implemented by the processor, a public key associated with the customer account;
receiving, at the network interface, based at least in part upon the first request and the public key, the first amount of the cryptocurrency;
determining, by the aggregation engine, a first value approximately equivalent to the first amount of cryptocurrency;
associating, by the aggregation engine, the first value with the customer account;
aggregating, by the aggregation engine, the first amount of the cryptocurrency with an aggregated amount of the cryptocurrency in the enterprise account;
securing, by a vault engine implemented by the processor, the public key in the enterprise account; and
securing, by the vault engine, the private key, wherein securing the private key comprises:
selecting a first hash function based on a first location of a first data center;
selecting a second hash function based on a second location of a second data center;
applying the first hash function to at least a portion of the private key to generate a first vault key, wherein applying the first hash function obfuscates the private key to generate the first vault key;
storing information associated with recovering the private key based on the first vault key;
applying the second hash function to at least a portion of the private key to generate a second vault key, wherein applying the second hash function obfuscates the private key to generate the second vault key;
storing information associated with recovering the private key based on the second vault key;
storing, by the vault engine, the first vault key at the first data center; and
storing, by the vault engine, the second vault key at the second data center.

9. The method of claim 8 , further comprising:
receiving, at the network interface, a second request to withdraw a second amount of the cryptocurrency from the customer account from the customer;
determining a second value approximately equivalent to the second amount of the cryptocurrency to the customer account;
withdrawing the second amount of the cryptocurrency from the enterprise account; and
transferring the second amount of the cryptocurrency to the customer.

10. The method of claim 8 , further comprising:
communicating, in response to securing the public key and the private key, a confirmation confirming the public key and the private key are secure to the customer.

11. The method of claim 8 , further comprising determining that the customer authorized the first request.

12. The method of claim 8 , wherein the customer account is associated with a cryptocurrency account.

13. The method of claim 8 , wherein:
the public key is a first public key; and
and the enterprise account is associated with a second public key.

14. The method of claim 8 , wherein the first value is determined based at least in part upon a price associated with the cryptocurrency.

15. A server comprising:
a memory operable to:
store a customer account associated with a customer;
store an enterprise account associated with an enterprise; and

a processor communicatively coupled to the memory, the memory including executable instructions that upon execution by the processor cause the system to:
receive a first request to deposit a first amount of a cryptocurrency in the customer account and store a private key associated with the customer account from the customer;
determine a public key associated with the customer account;
receive, based at least in part upon the first request and the public key, the first amount of the cryptocurrency;
determine a f

Assignees

• Bank Of America

Inventors

• Ronca James G
• Blackhurst Jason P
• Castinado Joseph B
• Dolan Heather
• Durbin Thomas E
• Thomas Richard H

Classifications

• H04L9/0894

  Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage · CPC title

• G06Q20/3829 Primary

  involving key management · CPC title

• G06Q40/02

  Banking, e.g. interest calculation or account maintenance (credit or loans G06Q40/03) · CPC title

• G06Q20/065

  using e-cash · CPC title

• G06Q20/108

  Remote banking, e.g. home banking · CPC title