Secret Sharing via Blockchains

[0001] This application relates to U.S. application Ser. No. 15/419,033 filed Jan. 30, 2017 and to U.S. application Ser. No. 15/419,042 also filed Jan. 30, 2017, with both applications incorporated herein by reference in their entireties.

[0002] Security is important in today's online environment. One reads nearly every day of another hacking. People's data is even being held ransom.

[0010] The exemplary embodiments will now be described more fully hereinafter with reference to the accompanying drawings. The exemplary embodiments may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. These embodiments are provided so that this disclosure will be thorough and complete and will fully convey the exemplary embodiments to those of ordinary skill in the art. Moreover, all statements herein reciting embodiments, as well as specific examples thereof, are intended to encompass both structural and functional equivalents thereof. Additionally, it is intended that such equivalents include both currently known equivalents as well as equivalents developed in the future (i.e., any elements developed that perform the same function, regardless of structure).

[0011] Thus, for example, it will be appreciated by those of ordinary skill in the art that the diagrams, schematics, illustrations, and the like represent conceptual views or processes illustrating the exemplary embodiments. The functions of the various elements shown in the figures may be provided through the use of dedicated hardware as well as hardware capable of executing associated software. Those of ordinary skill in the art further understand that the exemplary hardware, software, processes, methods, and/or operating systems described herein are for illustrative purposes and, thus, are not intended to be limited to any particular named manufacturer.

[0012] As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless expressly stated otherwise. It will be further understood that the terms “includes,” “comprises,” “including,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. It will be understood that when an element is referred to as being “connected” or “coupled” to another element, it can be directly connected or coupled to the other element or intervening elements may be present. Furthermore, “connected” or “coupled” as used herein may include wirelessly connected or coupled. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items.

[0013] It will also be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first device could be termed a second device, and, similarly, a second device could be termed a first device without departing from the teachings of the disclosure.

[0014] FIGS. 1-3 are simplified illustrations for secretly sharing an electronic document 20, according to exemplary embodiments. The electronic document 20 contains sensitive information, such as a user's social security number, income, banking, and other personal information. The electronic document 20, in plain words, contains secret data 22. While the electronic document 20 may have any content, most readers are thought familiar with a mortgage application 24. That is, the electronic document 20 may be a web-based, portable document format (PDF) associated with an applicant's personal and financial records for obtaining a mortgage. As the reader understands, the mortgage application 24 includes the secret data 22, such as an applicant's social security number, income, and banking records. If the mortgage application 24 were to fall into the wrong hands, the secret data 22 may be nefariously used by a rogue entity.

[0015] Exemplary embodiments thus protect the secret data 22. A server 26 retrieves a representation 28 of the electronic document 20 and splits the representation 28 into multiple pieces termed shares 30. The server 26 may then distribute one or more of the shares 30 via a blockchain 32. As the reader may understand, the blockchain 32 is generally a digital ledger in which transactions are chronologically and/or publically recorded. The blockchain 32 is most commonly used in decentralized cryptocurrencies (such as Bitcoin). The blockchain 32, however, may be adapted to any chain or custody (such as in medical records and in chains of title in real estate transactions). Indeed, there are many different mechanisms and configurations of the blockchain 32, and exemplary embodiments may be adapted to any version. Regardless, the shares 30 may be integrated into the blockchain 32 as a distribution or publication mechanism. The blockchain 32 may then route via a communications network 34 to any destination.

[0016] FIG. 2 illustrates secret sharing. Once the representation 28 of the electronic document 20 is split into the multiple shares 30, the server 26 may integrate any one or more of the shares 30 into the blockchain 32, perhaps with a timestamp 40. While the blockchain 32 may be sent or routed to any destination (such as an Internet Protocol address associated with another server or device), FIG. 2 illustrates peer distribution. That is, the server 26 may broadcast the blockchain 32 to the IP addresses associated with a group 42 of peer devices or nodes. The blockchain 32, in other words, is distributed to trusted peers for further processing and/or verification.

[0017] FIG. 3 further illustrates secret sharing. Here the server 26 may integrate any one or more of the shares 30 into multiple blockchains 32. While exemplary embodiments may utilize any number of different blockchains 32, FIG. 3 illustrates a simple example of three (3) blockchains 32a-c distributed to three (3) different groups 42a-c of peer devices. That is, some of the shares 30 (such as a first subset 50) are integrated into a first blockchain 32a and distributed (via the communications network 34 illustrated in FIGS. 1-2) to a first group 42a of peer devices. A second subset 52 of the shares 30 are integrated into a second blockchain 32b and distributed to a second group 42b of peer devices. Still more shares 30 (such as the remaining portion or pieces in a third subset 54) are integrated into a third blockchain 32c and distributed to a third group 42c of peer devices. Different collections of the shares 30, in other words, may be distributed via different blockchains 32 to different peer devices.

[0018] Exemplary embodiments may thus stash the secret data 22 in the multiple blockchains 32a-c. Because the electronic document 20 (containing the secret data 22) is split into the multiple shares 30, any one or more of the peer devices must possess a sufficient minimum number M_Min (illustrated as reference numeral 60) of the shares 30 before the secret data 22 may be recovered. That is, possession of an insufficient number of the shares 30 guarantees that the secret data 22 remains unknown and confidential. So, if the first blockchain 32a contains less than the M_Min 60 of the total shares 30, then the first group 42a of peer devices cannot reconstruct the secret data 22. Likewise, if the second blockchain 32b and/or the third blockchain 32c also contains less than the M_Min 30, the second group 42b of peer devices and the third group 42c of peer devices are also unable to reveal or decipher the secret data 22. In other words, no single one of the multiple blockchains 32a-c stores the requisite minimum number M_Min 60 of the shares 30 to launch a brute-force attack on the secret data 22. Even multiple ones of the blockchains 32a-c may be purposefully designed to never exceed the requisite minimum number M_Min 60 of the shares 30, perhaps thus forcing a hacker to compromise several or all of the blockchains 32a-c. A rogue attack, in simple words, would have to access and compromise multiple blockchains 32 before jeopardizing the secret data 22 contained within the electronic document 20.

[0019] Exemplary embodiments thus present an elegant solution. Sensitive, secret documents (containing the secret data 22) may be secretly shared via the one or more blockchains 32a-c. Even if the blockchains 32a-c are dispersed to trusted peer devices, the peer devices still cannot discern the secret data 22 until the threshold minimum number M_Min 60 of the shares 30 is obtained. Exemplary embodiments thus purposefully add a second-layer of protection, beyond merely trusted receipt of the blockchain 32. The trusted peers simply do not have access to the secret data 22 until the minimum number M_Min 60 of the shares 30 is obtained.

[0020] Any secret sharing scheme may be utilized. The reader is perhaps familiar with Shamir's Secret Sharing Algorithm, which is a well-known cryptographic algorithm. Exemplary embodiments divide the secret data 22 into unique parts (e.g., the shares 30), with each individual share 30 being different from other shares 30. However, there are many secret sharing or splitting schemes and algorithms for distributing a secret, and exemplary embodiments may be applied regardless of any particular scheme or algorithm.

[0021] FIG. 4 is a detailed illustration of an operating environment, according to exemplary embodiments. Here the server 26 secretly shares the electronic document 20 via the one or more blockchains 32. The server 26 may have a processor 70 (e.g., “μP”), application specific integrated circuit (ASIC), or other component that executes an electronic representation of a sharing algorithm 72 stored in a local memory device 74. The sharing algorithm 72 includes instructions, code, and/or programs that cause the server 26 to perform operations, such as splitting or segmenting the representation 28 of the electronic document 20 into the multiple shares 30. The sharing algorithm 72 may then select one or more of the shares 30 (such as the first subset 50) for integration into the first blockchain 32a. The sharing algorithm 72 may then select other ones of the shares 30 (such as the second subset 52) for integration into the second blockchain 32b. The sharing algorithm 72 may then integrate any remaining, unselected ones of the shares 30 (such as the third subset 54) for integration into the third blockchain 32c. The sharing algorithm 72 may also add the timestamp 40 to each blockchain 32a-c. After different collections of the shares 30 are integrated into the different blockchains 32a-c, the blockchains 32a-c are distributed to their respective destinations (such as Internet Protocol addresses associated with the first group 42a of peer devices, the second group 42b of peer devices, and the third group 42c of peer devices).

[0022] Exemplary embodiments may be applied regardless of networking environment. Exemplary embodiments may be easily adapted to stationary or mobile devices having cellular, wireless fidelity (WI-FI®), near field, and/or BLUETOOTH® capability. Exemplary embodiments may be applied to mobile devices utilizing any portion of the electromagnetic spectrum and any signaling standard (such as the IEEE 802 family of standards, GSM/CDMA/TDMA or any cellular standard, and/or the ISM band). Exemplary embodiments, however, may be applied to any processor-controlled device operating in the radio-frequency domain and/or the Internet Protocol (IP) domain. Exemplary embodiments may be applied to any processor-controlled device utilizing a distributed computing network, such as the Internet (sometimes alternatively known as the “World Wide Web”), an intranet, a local-area network (LAN), and/or a wide-area network (WAN). Exemplary embodiments may be applied to any processor-controlled device utilizing power line technologies, in which signals are communicated via electrical wiring. Indeed, exemplary embodiments may be applied regardless of physical componentry, physical configuration, or communications standard(s).

[0023] Exemplary embodiments may utilize any processing component, configuration, or system. Any processor could be multiple processors, which could include distributed processors or parallel processors in a single machine or multiple machines. The processor can be used in supporting a virtual processing environment. The processor could include a state machine, application specific integrated circuit (ASIC), programmable gate array (PGA) including a Field PGA, or state machine. When any of the processors execute instructions to perform “operations”, this could include the processor performing the operations directly and/or facilitating, directing, or cooperating with another device or component to perform the operations.

[0024] Exemplary embodiments may packetize. The server 26 and the recipient peer devices may have network interfaces to the communications network 34, thus allowing collection and retrieval of information. The information may be received as packets of data according to a packet protocol (such as the Internet Protocol). The packets of data contain bits or bytes of data describing the contents, or payload, of a message. A header of each packet of data may contain routing information identifying an origination address and/or a destination address.

[0025] FIGS. 5-6 illustrate hashing, according to exemplary embodiments. When the server 26 retrieves the representation 28 of the electronic document 20, here the representation 28 may be one or more hash values 80. That is, the server 26 may call or invoke an electronic representation of a hashing algorithm 82 that hashes electronic data 84 representing or associated with the electronic document 20 to generate the hash values 80. The hash values 80 may be associated with a hash tree 86 and/or root 88. The sharing algorithm 72 may then retrieve and split the hash values 80 into the multiple shares 30. The sharing algorithm 72 may then group or collect different ones of the shares 30 for integration into the one or more blockchains 32 (as this disclosure earlier explained). The blockchains 32 are then distributed to their respective destinations (again as this disclosure earlier explained). Exemplary embodiments may thus first hash the electronic document 20, create the shares 30 from the hash values 80, and then integrate the shares 30 into the blockchain(s) 32.

[0026] Hashing adds another layer of security. Exemplary embodiments may call or execute the hashing algorithm 82 that generates the hash values 80 (e.g., the hash tree 86 and the root 88) associated with the electronic document 20. There are many hashing algorithms, and exemplary embodiments may utilize any of the hashing algorithms. For example, many readers may be familiar with the SHA family of cryptographic hashing algorithms. Moreover, the hash tree 86 may be described as the Merkle tree, which many readers are also thought familiar. Regardless, once the hash values 80 are determined, exemplary embodiments may split the hash values 80 into the shares 30 for integration into the one or more blockchains 32. That is, the shares 30 may be added to, or incorporated in, any record, transaction, or block and distributed via the blockchain(s) 32.

[0027] FIG. 6 illustrates an alternative hashing strategy. Here the server 26 may call or invoke the sharing algorithm 72 to split the electronic data 84 associated with the electronic document 20 into the multiple shares 30. The server 26 may then apply the hashing algorithm 82 to the shares 30 to generate the hash values 80. The hash values 80 may then be integrated into the one or more blockchains 32 for distribution. Exemplary embodiments may thus first create the shares 30 from the electronic data 84, hash the shares 30, and then integrate the hash values 80 into the blockchain(s) 32.

[0028] FIGS. 7-8 illustrate a sharing strategy 90, according to exemplary embodiments. Here the sharing algorithm 72 may retrieve and implement the sharing strategy 90 that defines distribution via the multiple blockchains 32a-c to protect the secret data 22. Suppose, for example, that the total number N_S (illustrated as reference numeral 92) of the shares 30 defines a number N_B (illustrated as reference numeral 94) of the different blockchains 32. The total number N_S 92 of the shares 30, in other words, may relate by a ratio to the number N_B 94 of blockchains 32 that must be used. As a simple example, the ratio may be

$\frac{N_S}{N_B}=10,000,$

[0029] where the total number N_S 92 of the shares 30 is ten thousand (10,000) times the number N_B 94 of blockchains 32 that must be used. Again, as a simple example, if the electronic document 20 is associated with one million (1,000,000) shares 30, then one hundred (100) different blockchains 32 must be generated and distributed. The sharing strategy 90, in other words, may set a maximum number N_S. (illustrated as reference numeral 96) of shares 30 integrated into any single blockchain 32. The sharing strategy 90, in other words, may thus limit the number of the shares 30 exposed by any individual blockchain 32.

[0030] FIG. 8 further illustrates the sharing strategy 90. Here, though, the number N_B 94 of blockchains may be based on the number of recipients. That is, the total number N_R (illustrated as reference numeral 98) of the recipients may define the number N_B 94 of the different blockchains 32. The greater the recipients, in other words, then the greater the N_B 94 of blockchains 32 that must be used. Again, suppose that the sharing strategy 90 may again be defined as the ratio

$\frac{N_R}{N_B}=100,$

where the total number N_R 98 of the recipients is one hundred (100) times the number N_B 94 of blockchains 32 that must be used. Again, as a simple example, if there are ten thousand recipients, then one hundred (100) different blockchains 32 must be generated and distributed. The sharing strategy 90, in other words, may set a maximum number N_Rmax (illustrated as reference numeral 100) of recipients per blockchain 32. The sharing strategy 90, in other words, may thus limit the number of the shares 30 exposed by any individual blockchain 32.

[0031] The sharing strategy 90 may be implemented as logical rules. If the sharing strategy 90 is mathematically defined (such as the ratio above discussed), the sharing strategy 90 may be expressed as logical statements involving mathematical expressions. Exemplary embodiments may code or program the sharing strategy 90 to achieve policy goals and/or security objectives.

[0032] FIG. 9 is a flowchart illustrating a method or algorithm for secret sharing via the blockchain(s) 32, according to exemplary embodiments. The electronic data 84 representing the electronic document 20 is received (Block 200). The electronic data 84 is hashed using the hashing algorithm 82 (Block 202) to generate the hash values 80 (Block 204). The shares are created from the hash values 80 (Block 206). The shares 30 are integrated into the one or more blockchains 32 (Block 208).

[0033] FIG. 10 is another flowchart illustrating a method or algorithm for secret sharing via the blockchain(s) 32, according to exemplary embodiments. The electronic data 84 representing the electronic document 20 is received (Block 200). The electronic data 84 is split to create the shares 30 (Block 202). The shares 30 are hashed using the hashing algorithm 82 (Block 204) to generate the hash values 80 (Block 206). The hash values 80 are integrated into the one or more blockchains 32 (Block 208).

[0034] FIG. 11 is a schematic illustrating still more exemplary embodiments. FIG. 11 is a more detailed diagram illustrating a processor-controlled device 250. As earlier paragraphs explained, the sharing algorithm 72 and the hashing algorithm 82 may partially or entirely operate in any mobile or stationary processor-controlled device. FIG. 11, then, illustrates the sharing algorithm 72 and the hashing algorithm 82 stored in a memory subsystem of the processor-controlled device 250. One or more processors communicate with the memory subsystem and execute either, some, or all applications. Because the processor-controlled device 250 is well known to those of ordinary skill in the art, no further explanation is needed.

[0035] FIG. 12 depicts other possible operating environments for additional aspects of the exemplary embodiments. FIG. 12 illustrates the sharing algorithm 72 and the hashing algorithm 82 operating within various other processor-controlled devices 250. FIG. 12, for example, illustrates that the sharing algorithm 72 and the hashing algorithm 82 may entirely or partially operate within a set-top box (“STB”) (252), a personal/digital video recorder (PVR/DVR) 254, a Global Positioning System (GPS) device 256, an interactive television 258, a tablet computer 260, or any computer system, communications device, or processor-controlled device utilizing any of the processors above described and/or a digital signal processor (DP/DSP) 262. Moreover, the processor-controlled device 250 may also include wearable devices (such as watches), radios, vehicle electronics, clocks, printers, gateways, mobile/implantable medical devices, and other apparatuses and systems. Because the architecture and operating principles of the various devices 250 are well known, the hardware and software componentry of the various devices 250 are not further shown and described.

[0036] Exemplary embodiments may be applied to any signaling standard. Most readers are thought familiar with the Global System for Mobile (GSM) communications signaling standard. Those of ordinary skill in the art, however, also recognize that exemplary embodiments are equally applicable to any communications device utilizing the Time Division Multiple Access signaling standard, the Code Division Multiple Access signaling standard, the “dual-mode” GSM-ANSI Interoperability Team (GAIT) signaling standard, or any variant of the GSM/CDMA/TDMA signaling standard. Exemplary embodiments may also be applied to other standards, such as the I.E.E.E. 802 family of standards, the Industrial, Scientific, and Medical band of the electromagnetic spectrum, BLUETOOTH®, and any other.

[0037] Exemplary embodiments may be physically embodied on or in a computer-readable storage medium. This computer-readable medium, for example, may include CD-ROM, DVD, tape, cassette, floppy disk, optical disk, memory card, memory drive, and large-capacity disks. This computer-readable medium, or media, could be distributed to end-subscribers, licensees, and assignees. A computer program product comprises processor-executable instructions for sharing secrets via blockchains, as the above paragraphs explained.

[0038] While the exemplary embodiments have been described with respect to various features, aspects, and embodiments, those skilled and unskilled in the art will recognize the exemplary embodiments are not so limited. Other variations, modifications, and alternative embodiments may be made without departing from the spirit and scope of the exemplary embodiments.