IP Library Granted Patent US 10,984,116
Granted Patent B2
US 10,984,116 · App. 16/261,720 · Granted Apr 20, 2021

Systems and methods for digital currency or crypto currency storage in a multi-vendor cloud environment

Inventor: Paul Lewis (Asbury, NJ)
Assignee: CALAMU TECHNOLOGIES CORPORATION
G06F21/602G06F3/067G06F21/6218H04L9/085H04L9/0819H04L9/0861H04L9/0894H04L9/14H04L9/3226H04L63/0428H04L63/0435H04L63/08H04L63/083G06F2221/2107H04L67/1097H04L2209/56H04L2463/081
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,984,116
App. No.
16/261,720
Granted
Apr 20, 2021
Kind
B2
Abstract

A cloud-based system for providing data security, the system having a processor which creates a source data file; wherein the source data file is split into one or more fragments; an encryption key associated with the one or more fragments; and wherein the one or more fragments are encrypted by the encryption key; a plurality of cloud storage providers; wherein the one or more fragments are distributed among the plurality of cloud storage providers whereby no single cloud storage provider possesses all of the one or more fragments; a pointer file which is created on a local computer; wherein the pointer file stores the location of the one or more fragments; and wherein the pointer file is accessed; the encryption key authenticates the plurality of cloud storage providers; the one or more fragments are transferred from the plurality of cloud storage providers to the local computer; and wherein the one or more fragments are reassembled; and the source data file is deleted.

Claims (39)

1. A cloud-based system for secure storage of digital currency or crypto currency (hereinafter, collectively, “digital currency”), comprising:

a processor configured to:

obtain source digital currency;

split the source digital currency into a plurality of data blocks;

encrypt the data blocks using an encryption key associated with the data blocks; and

write the encrypted data blocks across at least three cloud storage providers, each cloud storage provider located in a different legal jurisdiction, each data block written to at least two but less than all of the cloud storage providers, whereby there is no single cloud storage provider to which all of the data blocks are written; such that if any one cloud storage provider is unavailable, the encrypted data blocks stored thereon may be retrieved from at least one other cloud storage provider; and in the case any one of the cloud storage providers is compromised, the digital currency cannot be recovered from the encrypted data blocks stored in that cloud storage provider alone;

create a pointer file;

store in the pointer file the locations in every cloud storage provider to which each of the encrypted data blocks was written; and

the processor is further configured to thereafter:

access the pointer file and the encryption key;

authenticate, using the encryption key, the cloud storage providers in which the encrypted blocks were written;

transfer the encrypted blocks from the cloud storage providers to a secondary computer;

decrypt the transferred encrypted blocks;

reassemble the decrypted blocks as digital currency; and

delete the source digital currency.

2. The system as recited in claim 1 , wherein the encryption key is generated by a user.

3. The system as recited in claim 1 , wherein the processor is further configured to autogenerate the encryption key.

4. The system as recited in claim 1 , wherein the pointer file is stored locally on a user's computer.

5. The system as recited in claim 1 , wherein the pointer file further includes a lookup table.

6. A computer implemented method for secure storage of digital currency or crypto currency (hereinafter, collectively, “digital currency”), comprising causing by a processor completion of steps including:

obtaining source digital currency;

splitting the source digital currency into a plurality of data blocks;

encrypting the data blocks using an encryption key associated with the data blocks;

writing the encrypted data blocks across at least three cloud storage providers, each cloud storage provider located in a different legal jurisdiction, each data block written to at least two but less than all of the cloud storage providers, whereby there is no single cloud storage provider to which all of the data blocks are written; such that if any one cloud storage provider is unavailable, the encrypted data blocks stored thereon may be retrieved from at least one other cloud storage provider; and in the case any one of the cloud storage providers is compromised, the digital currency cannot be recovered from the encrypted data blocks stored in that cloud storage provider alone;

creating a pointer file;

storing in the pointer file the locations in every cloud storage provider to which each of the encrypted data blocks was written; and thereafter:

accessing the pointer file and the encryption key;

authenticating, using the encryption key, the cloud storage providers in which the encrypted blocks were written;

transferring the encrypted blocks from the cloud storage providers to a secondary the local computer;

decrypting the transferred encrypted blocks;

reassembling the decrypted blocks as digital currency; and

deleting the source digital currency.

7. The method as recited in claim 6 , further comprising:

generating, via the processor, a copy of the pointer file.

8. The method as recited in claim 7 , further comprising:

encrypting the copy of the pointer file.

9. The method as recited in claim 8 , further comprising:

accessing the encrypted pointer file on one or more secondary computers; and

decrypting the encrypted pointer file.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 14, 2020
From: LEWIS, PAUL
To: CALAMU TECHNOLOGIES CORPORATION
Reel/Frame 054631/0377 →
Continuity (5)
Continuation In Part 16055587 · Aug 6, 2018
Continuation 15226237 · Aug 2, 2016
Continuation In Part 14251612 · Jun 30, 2014
Provisional Application 61812115 · Apr 15, 2013
Related Publication 20190156045A1 · May 23, 2019