ABSTRACT
Abstract
The disclosed embodiments include computerized systems and methods for generating secured blockchain-based ledger data structures that track occurrences of events across fragmented and geographically dispersed lines-of-business of an enterprise. In one instance, an apparatus associated with a rules authority of the secured blockchain-based ledger may detect an occurrence of a triggering event, and may access and decrypt a set of rules hashed into the secured blockchain-based ledger using a confidentially-held master cryptographic key. The apparatus may identify a rule associated with the detected event, and perform one or more operations consistent with the rule, including a disbursement of various rewards to employees in response to customer-specific interactions with the enterprise. The disclosed embodiments provide a rules process for aggregating mutually incompatible enterprise data that specifies the events, and for tracking the events in uniform data structures accessible across the enterprise.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
This application is a continuation of, and claims the benefit of priority to, U.S. application Ser. No. 14/928,838, filed Oct. 30, 2015, which claims the benefit of U.S. Provisional Patent Application No. 62/204,768, filed Aug. 13, 2015. The disclosures of these applications are expressly incorporated by reference herein to-their entireties.
DESCRIPTION
Technical Field
The disclosed embodiments generally relate to computerized systems and methods for securing data, and more particularly, and without limitation, computerized systems and methods that generate secured blockchain-based ledger structures.
Background
Modern commercial enterprises, such as financial institutions, multinational corporations, and law firms, often link together multiple, fragmented, and geographically dispersed business units and lines-of-business. Although operating within a common enterprise, the fragmented nature of these distinct business units and lines-of-business renders complex any attempt to accurately identify and capture the various points of customer interaction across the enterprise. Further, devices operating within these fragmented and geographically dispersed business units and lines-of-business often execute various and often mutually-incompatible software applications (with corresponding mutually-incompatible data inputs and outputs), which often prevents the timely aggregation of data captured across the enterprise devices and the dissemination of the aggregated data within the enterprise. The lack of business-unit and line-of-business integration may lead to an environment characterized by incoherent customer management, which may prevent conventional database architectures from tracking and quantifying occurrences of enterprise-specific events, such as cross-line-of-business referrals and cross-line-of-business interactions.
SUMMARY
The disclosed embodiments relate to computerized systems and methods that generate secured blockchain-based ledger structures tracking occurrences of events across fragmented and geographically dispersed enterprises.
In one embodiment, an apparatus includes at least one processor and a memory storing executable instructions that, when executed by the at least one processor, causes the at least one processor to perform the steps of accessing data corresponding to at least one blockchain ledger and detecting an occurrence of an event within the blockchain ledger data. The executed instructions may further cause the at least one processor to perform the step of decrypting (i) a first encrypted portion of the blockchain ledger data using a first cryptographic key and (ii) a second encrypted portion of the blockchain ledger data using a second cryptographic key. In certain aspects, the decrypted first data portion may identify a plurality of triggering events, and the decrypted second data portion may identify a plurality of rules associated with a rules authority. The executed instructions may further cause the at least one processor to perform the step of determining, based on the decrypted first data portion, that the detected event corresponds to at least one of the triggering events. In response to the determination, the executed instructions may further cause the at least one processor to perform the steps of identifying, based on the detected second data portion, at least one of the one or more rules that exhibits a causal relationship with the detected event, and generating an electronic command to perform one or more operations consistent with the at least one identified rule.
In further embodiments, a computer-implemented method may include accessing, using at least one processor, data corresponding to at least one blockchain ledger, and detecting, using the at least one processor, an occurrence of an event within the blockchain ledger data. The method may also include, using the at least one processor, decrypting (i) a first encrypted portion of the blockchain ledger data using a first cryptographic key and (ii) a second encrypted portion of the blockchain ledger data using a second cryptographic key. In certain aspects, the decrypted first data portion may identify a plurality of triggering events, and the decrypted second data portion may identify a plurality of rules associated with a rules authority. The method may also include, based on the decrypted first data portion, determining, using the at least one processor, that the detected event corresponds to at least one of the triggering events. In response to the determination, the method may further include identifying, using the at least one processor, and based on the detected second data portion, at least one of the one or more rules that exhibits a causal relationship with the detected event, and generating, using the at least one processor, an electronic command to perform one or more operations consistent with the at least one identified rule.
In other embodiments, a tangible, non-transitory computer-readable medium may store instructions that, when executed by at least one processor, perform a method. The method may include accessing data corresponding to at least one blockchain ledger, and detecting an occurrence of an event within the blockchain ledger data. The method may also include decrypting (i) a first encrypted portion of the blockchain ledger data using a first cryptographic key and (ii) a second encrypted portion of the blockchain ledger data using a second cryptographic key. In certain aspects, the decrypted first data portion may identify a plurality of triggering events, and the decrypted second data portion may identify a plurality of rules associated with a rules authority. The method may also include, based on the decrypted first data portion, determining that the detected event corresponds to at least one of the triggering events. In response to the determination, the method may further include identifying, based on the detected second data portion, at least one of the one or more rules that exhibits a causal relationship with the detected event, and generating an electronic command to perform one or more operations consistent with the at least one identified rule.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only, and are not restrictive of the disclosed embodiments as claimed. Further, the accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate aspects of the present disclosure and together with the description, serve to explain principles of the disclosed embodiments as set forth in the accompanying claims
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a diagram of an exemplary computing environment, consistent with disclosed embodiments.
FIG. 2 is a schematic diagram illustrating a conventional blockchain ledger architecture.
FIG. 3 is a schematic diagram illustrating a hybrid, public-private blockchain ledger architecture, consistent with disclosed embodiments.
FIG. 4 is a flowchart of an exemplary process for performing operations in response to events tracked within a hybrid blockchain ledger, consistent with the disclosed embodiments.
FIG. 5 is a diagram of an exemplary customer-specific accounting ledger, consistent with disclosed embodiments.
FIG. 6 is a flowchart of an exemplary process for performing operations in response to events tracked within a hybrid blockchain ledger, consistent with the disclosed embodiments.
DETAILED DESCRIPTION
Reference will now be made in detail to the disclosed embodiments, examples of which are illustrated in the accompanying drawings. The same reference numbers in the drawings and this disclosure are intended to refer to the same or like elements, components, and/or parts.
In this application, the use of the singular includes the plural unless specifically stated otherwise. In this application, the use of âorâ means âand/orâ unless stated otherwise. Furthermore, the use of the term âincluding,â as well as other forms such as âincludesâ and âincluded,â is not limiting. In addition, terms such as âelementâ or âcomponentâ encompass both elements and components comprising one unit, and elements and components that comprise more than one subunit, unless specifically stated otherwise. Additionally, the section headings used herein are for organizational purposes only, and are not to be construed as limiting the subject matter described.
I. Exemplary Computing Environments, Networks, Systems, and Devices
FIG. 1 illustrates an exemplary computing environment 100 consistent with certain disclosed embodiments. In one aspect, computing environment 100 may include client devices 102 , 104 , and 106 , system 140 , peer systems 160 , and a communications network 120 connecting one or more of the components of environment 100 .
Consistent with the disclosed embodiments, one or more of the components of computing environment 100 may be configured to address problems inherent to conventional blockchain-based ledgers by embedding a private-master encryption key architecture into a conventional blockchain architecture (e.g., a blockchain-based architecture associated with the public Bitcoin⢠ledger). In some aspects, the resulting hybrid blockchain architecture may facilitate a selective encryption of information by client devices 102 , 104 , and 106 , system 140 , and/or peer systems 160 , thus providing a technical solution that protects sensitive and/or confidential instructions sets and event triggers and corresponding confidential instructions sets.
a. Exemplary Client Devices
In one embodiment, client devices 102 , 104 , and/or 106 may include a computing device, such as, but not limited to, a hashing computer, a personal computer, a laptop computer, a tablet computer, a notebook computer, a hand-held computer, a personal digital assistant, a portable navigation device, a mobile phone, a smart phone, a wearable computing device (e.g., a smart watch, a wearable activity monitor, wearable smart jewelry, and glasses and other optical devices that include optical head-mounted displays (OHMDs), an embedded computing device (e.g., in communication with a smart textile or electronic fabric), and any other type of computing device that may be configured to store data and software instructions, execute software instructions to perform operations, and/or display information on a display device(s), consistent with disclosed embodiments. In certain embodiments, at least one of client devices 102 , 104 , and/or 106 may be associated with one or more users, such as users 108 , 110 , and/or 112 . For instance, user 110 may operate client device 104 and may do so to cause client device 104 to perform one or more operations consistent with the disclosed embodiments.
Client devices 102 , 104 , and/or 106 may include one or more tangible, non-transitory memories that store data and/or software instructions, and one or more processors configured to execute software instructions. Client devices 102 , 104 , and/or 106 may include one or more display devices that display information to a user and one or more input device(s) to allow the user to input information to client device 102 , 104 , and/or 106 (e.g., keypad, keyboard, touchscreen, voice activated control technologies, or any other type of known input device).
In one aspect, client devices 102 , 104 , and/or 106 may store in memory one or more software applications that run on client device 104 and are executed by the one or more processors. In some instances, client device 104 may store software applications that, when executed by one or more processors, perform operations that establish communications with one or more of peer systems 160 (e.g., across network 120 ) and that obtain, from peer systems 160 , a current version of a hybrid blockchain ledger generated and maintained in accordance with the disclosed embodiments.
In other instances, and as described below, one or more of client devices 102 , 104 , and/or 106 may execute the one or more stored software application and to obtain data from the hybrid blockchain ledger that includes, but not limited to, data identifying one or more tracked assets, and/or a public key of one or more users. Further, and as described below, the one or more executed software applications may cause client devices 102 , 104 , and/or 106 to extract, from the one or more accessed blocks, a copy of an encrypted and/or hashed ownership/rules portion of the transaction block (e.g., including the identification a holder of a master key) and/or a copy of an encrypted and/or hashed master data block (e.g., encrypted using the master key and including rules permitting preconfigured and/or actions involving the tracked assets). In additional instances, and as further described below, client devices 102 , 104 , and/or 106 may provide information associated with one or more actions or transactions involving the tracked assets (e.g., information identifying the actions or transaction, information identifying the assets, a public key, a digital signature, etc.) to peer systems 160 , along with copies of the encrypted and/or hashed rules engines and lists of triggering events.
In some aspects, the one or more stored applications may include a wallet application provided by business entity 150 (e.g., a mobile wallet application or an application executable on a desktop computer) and capa
CROSS-REFERENCE TO RELATED APPLICATIONS
This application is a continuation of, and claims the benefit of priority to, U.S. application Ser. No. 14/928,838, filed Oct. 30, 2015, which claims the benefit of U.S. Provisional Patent Application No. 62/204,768, filed Aug. 13, 2015. The disclosures of these applications are expressly incorporated by reference herein to-their entireties.
DESCRIPTION
Technical Field
The disclosed embodiments generally relate to computerized systems and methods for securing data, and more particularly, and without limitation, computerized systems and methods that generate secured blockchain-based ledger structures.
Background
Modern commercial enterprises, such as financial institutions, multinational corporations, and law firms, often link together multiple, fragmented, and geographically dispersed business units and lines-of-business. Although operating within a common enterprise, the fragmented nature of these distinct business units and lines-of-business renders complex any attempt to accurately identify and capture the various points of customer interaction across the enterprise. Further, devices operating within these fragmented and geographically dispersed business units and lines-of-business often execute various and often mutually-incompatible software applications (with corresponding mutually-incompatible data inputs and outputs), which often prevents the timely aggregation of data captured across the enterprise devices and the dissemination of the aggregated data within the enterprise. The lack of business-unit and line-of-business integration may lead to an environment characterized by incoherent customer management, which may prevent conventional database architectures from tracking and quantifying occurrences of enterprise-specific events, such as cross-line-of-business referrals and cross-line-of-business interactions.
SUMMARY
The disclosed embodiments relate to computerized systems and methods that generate secured blockchain-based ledger structures tracking occurrences of events across fragmented and geographically dispersed enterprises.
In one embodiment, an apparatus includes at least one processor and a memory storing executable instructions that, when executed by the at least one processor, causes the at least one processor to perform the steps of accessing data corresponding to at least one blockchain ledger and detecting an occurrence of an event within the blockchain ledger data. The executed instructions may further cause the at least one processor to perform the step of decrypting (i) a first encrypted portion of the blockchain ledger data using a first cryptographic key and (ii) a second encrypted portion of the blockchain ledger data using a second cryptographic key. In certain aspects, the decrypted first data portion may identify a plurality of triggering events, and the decrypted second data portion may identify a plurality of rules associated with a rules authority. The executed instructions may further cause the at least one processor to perform the step of determining, based on the decrypted first data portion, that the detected event corresponds to at least one of the triggering events. In response to the determination, the executed instructions may further cause the at least one processor to perform the steps of identifying, based on the detected second data portion, at least one of the one or more rules that exhibits a causal relationship with the detected event, and generating an electronic command to perform one or more operations consistent with the at least one identified rule.
In further embodiments, a computer-implemented method may include accessing, using at least one processor, data corresponding to at least one blockchain ledger, and detecting, using the at least one processor, an occurrence of an event within the blockchain ledger data. The method may also include, using the at least one processor, decrypting (i) a first encrypted portion of the blockchain ledger data using a first cryptographic key and (ii) a second encrypted portion of the blockchain ledger data using a second cryptographic key. In certain aspects, the decrypted first data portion may identify a plurality of triggering events, and the decrypted second data portion may identify a plurality of rules associated with a rules authority. The method may also include, based on the decrypted first data portion, determining, using the at least one processor, that the detected event corresponds to at least one of the triggering events. In response to the determination, the method may further include identifying, using the at least one processor, and based on the detected second data portion, at least one of the one or more rules that exhibits a causal relationship with the detected event, and generating, using the at least one processor, an electronic command to perform one or more operations consistent with the at least one identified rule.
In other embodiments, a tangible, non-transitory computer-readable medium may store instructions that, when executed by at least one processor, perform a method. The method may include accessing data corresponding to at least one blockchain ledger, and detecting an occurrence of an event within the blockchain ledger data. The method may also include decrypting (i) a first encrypted portion of the blockchain ledger data using a first cryptographic key and (ii) a second encrypted portion of the blockchain ledger data using a second cryptographic key. In certain aspects, the decrypted first data portion may identify a plurality of triggering events, and the decrypted second data portion may identify a plurality of rules associated with a rules authority. The method may also include, based on the decrypted first data portion, determining that the detected event corresponds to at least one of the triggering events. In response to the determination, the method may further include identifying, based on the detected second data portion, at least one of the one or more rules that exhibits a causal relationship with the detected event, and generating an electronic command to perform one or more operations consistent with the at least one identified rule.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only, and are not restrictive of the disclosed embodiments as claimed. Further, the accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate aspects of the present disclosure and together with the description, serve to explain principles of the disclosed embodiments as set forth in the accompanying claims
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a diagram of an exemplary computing environment, consistent with disclosed embodiments.
FIG. 2 is a schematic diagram illustrating a conventional blockchain ledger architecture.
FIG. 3 is a schematic diagram illustrating a hybrid, public-private blockchain ledger architecture, consistent with disclosed embodiments.
FIG. 4 is a flowchart of an exemplary process for performing operations in response to events tracked within a hybrid blockchain ledger, consistent with the disclosed embodiments.
FIG. 5 is a diagram of an exemplary customer-specific accounting ledger, consistent with disclosed embodiments.
FIG. 6 is a flowchart of an exemplary process for performing operations in response to events tracked within a hybrid blockchain ledger, consistent with the disclosed embodiments.
DETAILED DESCRIPTION
Reference will now be made in detail to the disclosed embodiments, examples of which are illustrated in the accompanying drawings. The same reference numbers in the drawings and this disclosure are intended to refer to the same or like elements, components, and/or parts.
In this application, the use of the singular includes the plural unless specifically stated otherwise. In this application, the use of âorâ means âand/orâ unless stated otherwise. Furthermore, the use of the term âincluding,â as well as other forms such as âincludesâ and âincluded,â is not limiting. In addition, terms such as âelementâ or âcomponentâ encompass both elements and components comprising one unit, and elements and components that comprise more than one subunit, unless specifically stated otherwise. Additionally, the section headings used herein are for organizational purposes only, and are not to be construed as limiting the subject matter described.
I. Exemplary Computing Environments, Networks, Systems, and Devices
FIG. 1 illustrates an exemplary computing environment 100 consistent with certain disclosed embodiments. In one aspect, computing environment 100 may include client devices 102 , 104 , and 106 , system 140 , peer systems 160 , and a communications network 120 connecting one or more of the components of environment 100 .
Consistent with the disclosed embodiments, one or more of the components of computing environment 100 may be configured to address problems inherent to conventional blockchain-based ledgers by embedding a private-master encryption key architecture into a conventional blockchain architecture (e.g., a blockchain-based architecture associated with the public Bitcoin⢠ledger). In some aspects, the resulting hybrid blockchain architecture may facilitate a selective encryption of information by client devices 102 , 104 , and 106 , system 140 , and/or peer systems 160 , thus providing a technical solution that protects sensitive and/or confidential instructions sets and event triggers and corresponding confidential instructions sets.
a. Exemplary Client Devices
In one embodiment, client devices 102 , 104 , and/or 106 may include a computing device, such as, but not limited to, a hashing computer, a personal computer, a laptop computer, a tablet computer, a notebook computer, a hand-held computer, a personal digital assistant, a portable navigation device, a mobile phone, a smart phone, a wearable computing device (e.g., a smart watch, a wearable activity monitor, wearable smart jewelry, and glasses and other optical devices that include optical head-mounted displays (OHMDs), an embedded computing device (e.g., in communication with a smart textile or electronic fabric), and any other type of computing device that may be configured to store data and software instructions, execute software instructions to perform operations, and/or display information on a display device(s), consistent with disclosed embodiments. In certain embodiments, at least one of client devices 102 , 104 , and/or 106 may be associated with one or more users, such as users 108 , 110 , and/or 112 . For instance, user 110 may operate client device 104 and may do so to cause client device 104 to perform one or more operations consistent with the disclosed embodiments.
Client devices 102 , 104 , and/or 106 may include one or more tangible, non-transitory memories that store data and/or software instructions, and one or more processors configured to execute software instructions. Client devices 102 , 104 , and/or 106 may include one or more display devices that display information to a user and one or more input device(s) to allow the user to input information to client device 102 , 104 , and/or 106 (e.g., keypad, keyboard, touchscreen, voice activated control technologies, or any other type of known input device).
In one aspect, client devices 102 , 104 , and/or 106 may store in memory one or more software applications that run on client device 104 and are executed by the one or more processors. In some instances, client device 104 may store software applications that, when executed by one or more processors, perform operations that establish communications with one or more of peer systems 160 (e.g., across network 120 ) and that obtain, from peer systems 160 , a current version of a hybrid blockchain ledger generated and maintained in accordance with the disclosed embodiments.
In other instances, and as described below, one or more of client devices 102 , 104 , and/or 106 may execute the one or more stored software application and to obtain data from the hybrid blockchain ledger that includes, but not limited to, data identifying one or more tracked assets, and/or a public key of one or more users. Further, and as described below, the one or more executed software applications may cause client devices 102 , 104 , and/or 106 to extract, from the one or more accessed blocks, a copy of an encrypted and/or hashed ownership/rules portion of the transaction block (e.g., including the identification a holder of a master key) and/or a copy of an encrypted and/or hashed master data block (e.g., encrypted using the master key and including rules permitting preconfigured and/or actions involving the tracked assets). In additional instances, and as further described below, client devices 102 , 104 , and/or 106 may provide information associated with one or more actions or transactions involving the tracked assets (e.g., information identifying the actions or transaction, information identifying the assets, a public key, a digital signature, etc.) to peer systems 160 , along with copies of the encrypted and/or hashed rules engines and lists of triggering events.
In some aspects, the one or more stored applications may include a wallet application provided by business entity 150 (e.g., a mobile wallet application or an application executable on a desktop computer) and capable of initiating transactions denominated in one or more currencies, including virtual currencies such as Bitcoinâ¢.
b. Exemplary Computer Systems
System 140 may be a computing system configured to execute software instructions to perform one or more operations consistent with disclosed embodiments. In one aspect, system 140 may be associated with a business entity 150 (e.g., a financial institution) that provides financial accounts, financial services transactions, and investment services one or more users (e.g., customers of the business entity 150 ). In some aspects, system 140 may be a distributed system that may include computing components distributed across one or more networks, such as network 120 , or other networks.
In one aspect, system 140 may include computing components configured to store, maintain, and generate data and software instructions. For example, system 140 may include one or more servers (e.g., server 142 ) and tangible, non-transitory memory devices (e.g., data repository 144 ). Server 142 may include one or more computing devices that may be configured to execute software instructions to perform one or more processes consistent with the disclosed embodiments. In one example, server 142 may be a computing device that executes software instructions that perform operations that provides information to one or more other components of computing environment 100 .
In one embodiment, server 142 may include a computer (e.g., a personal computer, network computer, or mainframe computer) having one or more processors that may be selectively activated or reconfigured by a computer program. In one aspect, server 142 (or other computing components of system 140 ) may be configured to provide one or more websites, digital portals, etc., that provide services consistent with business entity 150 , such as a digital banking or investment portal, and services consistent with disclosed embodiments. For instance, server 142 may be configured to provide information associated with a requested web page over communications network 120 to client device 104 , which may render the received information and present content from the web page on a display device, e.g., a touchscreen display unit.
In other aspects, server 142 (or other computing components of system 140 ) may be configured to provide information to one or more application programs executed by client device 104 (e.g., through a corresponding application programming interface (API)). For example, client device 104 may execute an application program associated with and provided by business entity 150 , such a mobile banking application and/or a mobile wallet application, to provide services consistent with the disclosed embodiments. In some instances, server 142 may provide information to client devices 102 , 104 , and/or 106 (e.g., through the API associated with the executed application program), and client devices 102 , 104 , and/or 106 may be configured by the executed application program to present portions of the information to corresponding users through a corresponding graphical user interface (GUI).
In further aspects, server 142 (or other computing components of system 140 ) may be configured to provide to client devices 102 , 104 , and/or 106 (and/or receive from client device 104 ) information associated with services provided by business entity 150 . For example, client device 104 may receive the transmitted information, and store portions of the information in locally accessible storage device and/or network-accessible storage devices and data repositories (e.g., cloud-based storage). In one instance, client device 104 may execute stored instructions (e.g., an application program, a web browser, a mobile banking application, and/or a mobile wallet application) to process portions of the stored data and render portions of the stored data for presentation to user 110 . Additionally, server 142 may be incorporated as a corresponding node in a distributed network, and additionally or alternatively, as a corresponding networked server in a cloud-computing environment. Furthermore, server 142 may communicate via network 120 with one or more additional servers (not shown), which may facilitate the distribution of processes for parallel execution by the additional servers.
In further aspects, business entity 150 may represent a âcontrolling entityâ capable of regulating transactions assets (e.g., units of virtual currency, units of various financial instruments, physical assets, etc.) tracked within hybrid public-private ledgers consistent with the disclosed embodiments. By way of example, one or more computing components of system 140 (e.g., server 142 ) may be configured (e.g., by executed software instructions) to establish one or more rules that regulate a distributions of and/or transactions associated with the tracked assets, an initiation of transfers of the tracked assets (e.g., a sale, a use of the tracked assets as collateral in a secured transaction etc.), and further, any additional or alternate action involving the tracked assets and/or the hybrid public-private ledger (e.g., processes that generate additional cryptographic key sets for user 110 , processes that recover assets tracked in the hybrid public-private ledger, etc.).
Additionally, in some aspects, system 140 may establish causal relationships between one or more of the established rules and one or more events that trigger an initiation of one or more corresponding regulated distributions, transfers, and/or other actions involving assets tracked within the hybrid public-private ledger (e.g., âtriggering eventsâ). For example, a confirmed loss of a private cryptographic key issued to user 110 may represent a triggering event that causes system 140 to verify user 110 's identity, initiate a transaction of the orphaned assets, generate a new pair of public and private cryptographic keys for user 110 (i.e., public and private blockchain keys), and transmit at least the private blockchain key to user 110 through secure, non-accessible processes, in accordance with one or more of the established rules.
Further, by way of example, a theft of a portion of user 110 's tracked assets (e.g., units of virtual currency specified within one of more blocks of the hybrid public-private ledger) may represent a triggering event that causes system 140 to initiate a recovery protocol to generate a transaction request to recover the value of the stolen assets (e.g., to transfer the stolen assets back to user 110 ), and further, to generate a new pair of public and private blockchain keys for user 110 , as described above. In other instances, a death and/or incapacitation of user 110 may represent a triggering event that causes system 140 to initiate a series of transaction to distribute of at least a portion of the tracked assets (e.g., through corresponding transaction requests consistent with the disclosed embodiments) to one or more additional owners identified by user 110 and specified within corresponding ones of the identified rules.
In some aspects, system 140 may be configured to establish one or more of the rules, and further, one or more of the causal relationships and triggering events, based on internal regulations associated with business entity 150 . For example, the one or more internal regulations associated with business entity 150 may specify that system 140 verify an identity of user 110 (e.g., based on various forms of multi-factor authentication data) and/or obtain specific elements of documentation (e.g., a police report, etc.) prior to initiating the lost private key protocol and/or the recovery protocols outlined above. In other aspects, system 140 may one or more of the rules and/or triggering events based on information received from user 110 (e.g., as input provided to a web page or other graphical user interface (GUI) presented by client device 104 and provided to system 140 ). For example, user 110 may specify, as input to the web page or GUI presented by client device 104 , one or more individuals that would receive portions of the tracked assets upon completion of one or more tasks and/or in the event of user 110 's accidental death. The disclosed embodiments are, however, not limited to the exemplary triggering events and established rules described above, and in further aspects, the disclosed embodiments may be configured to generate any additional or alternate user- and system-specified rules and triggering events consistent with the hybrid public-private ledger and appropriate to the tracked assets, user 110 , and/or business entity 150 (i.e., acting as a rules authority for the hybrid public-private ledger).
Further, and as outlined below, system 140 may be configured to store the one or more established rules (e.g., as a rules engine) and one or more of the established trigger events (e.g., as an event trigger list) within a portion of a local data repository (e.g., data repository 144 ). Additionally or alternatively, system 140 may be configured to store portions of the rules engine and/or event trigger list within a secure data repository accessible to system 140 across network 140 (e.g., cloud-based storage).
As described above, one or more computing components of system 140 (e.g., server 142 ) may be configured to generate pairs of public and private blockchain keys for user 110 (e.g., user 110 's public/private blockchain key pair), and to provide the generated private blockchain key to user 110 through secure, non-accessible and/or out-of-band communications (e.g., by mail, etc.). In further embodiments, the one or more components of system 140 (e.g., server 142 ) may be configured to generate and maintain additional cryptographic keys that facilitate a generation and maintenance of portions of the hybrid public-private ledger. For instance, system 140 may be configured to generate a master key, which system 140 may leverage to encrypt the stored rules engine. In certain aspects, system 140 may store copies of the generated master key in a portion of data repository 144 that is not accessible to user 110 (and any other users), thus maintaining a confidence of the generated master key.
In additional aspects, system 140 may be configured to generate and maintain a private crypto key on behalf of user 110 (and additionally or alternatively, user 108 and 112 ), which system 140 may leverage to encrypt the stored event trigger list, and which may be provided to user 110 (and/or to user 108 and 112 ) through secure, non-accessible and/or out-of-band communications. Further, and as described above, system 140 may store copies of the private crypto keys in a portion of data repository 144 .
Further, in additional embodiments, one or more computing components of system 140 (e.g., server 140 ) may be configured to hash the generated (and encrypted) rules engine and event trigger list into a genesis block associated with the hybrid public-private ledger. In other aspects, system 140 may provide the encrypted rules engine and event triggers list to one or more of peer system 160 , which may be configured to hash the encrypted rules engine and event trigger list into the genesis block. By way of example, and by hashing the encrypted rules engine and event trigger list into the genesis block of the hybrid public-private ledger, the disclosed embodiments enable an in-band communication of the encrypted rules engine and event triggers from user to user within blocks (e.g., transactions) of the hybrid public-private ledger
c. Exemplary Data Repositories and Stored Data
Data repository 144 may include one or more memories that are configured to store and provide access to data and/or software instructions. Such memories may include tangible non-transitory computer-readable media that store software instructions that, when executed by one or more processors (e.g., of server 132 ), perform one or more operations consistent with disclosed embodiments. Data repository 144 may also be configured to store information relating to business entity 150 , e.g., a financial institution.
For instance, data repository 144 may store customer data that uniquely identifies customers of a financial institution associated with system 140 . By way of example, a customer of the financial institution (e.g., users 108 , 110 , and/or 112 ) may access a web page associated with system 140 (e.g., through a web server executed by a corresponding front end), and may register for digital banking services and provide data, which may be linked to corresponding ones of users 108 , 110 , and/or 112 , and stored as customer data within data repository 144 . The stored customer data may, for example, include personal information, government-issued identifiers, employment information, and contact information. The stored customer data may also include authentication credentials associated with registered users of the financial institution (e.g., a user name, a user-specified password, a system-generated password, an alphanumeric identification number (e.g., a PIN number) specified by the users or assigned by financial system 140 , biometric information, and information facilitating enhanced authentication techniques).
In additional aspects, and as described above, data repository 144 may store a rules engine identifying or more rules that regulate a distribution of the tracked assets, an initiation of one or more transactions involving the tracked assets (e.g., a sale, a transfer in ownership, a use of the tracked assets as collateral in a secured transaction etc.), and further, any additional or alternate action involving the tracked assets and/or the hybrid public-private ledger (e.g., processes that generate additional cryptographic key sets for users 108 , 110 , and/or 112 , processes that recover assets racked in the hybrid public-private ledger, etc.). Further, and as described above, data repository 144 may also store information identifying an event triggers list that identifies causal relationships established by system 140 between one or more of the established rules and one or more events that trigger an initiation of one or more corresponding regulated distributions, transactions, and/or assets tracked within the hybrid blockchain ledger (e.g., âtriggering eventsâ).
In some aspects, system 140 may be configured to establish one or more of the rules, and further, one or more of the causal relationships and triggering events, based on one or more internal regulations associated with business entity 150 .
In other aspects, system 140 may one or more of the rules and/or triggering events based on information received from one or more of users 108 , 110 , and/or 112 (e.g., as input provided to a web page or other graphical user interface (GUI) presented by client devices 102 , 104 , and/or 106 and provided to system 140 ).
In an embodiment, data repository 144 may also store a copy of a master key and private crypto keys associated with users 108 , 110 , and 112 (and additionally or alternatively, additional private crypto keys associated with other users). By way of example, system 140 may be configured to store the private crypto keys in a data structure that includes information that associates the private crypto keys with corresponding ones of user 108 , 110 , and 112 , and further, may be configured to store the master key in a data structure within data repository 144 that is inaccessible to users 108 , 110 , and/or 112 (and additionally or alternatively, to other users). Further, in some aspects, data repository 144 may be configured to store the rules engine and/or event triggers list in raw, unencrypted form. In other aspects, consistent with the disclosed embodiments, data repository 144 may be configured to store the rules engine and/or event triggers in encrypted form (e.g., using the stored master key), and/or store a hashed representation of the rules engine and/or the event triggers list.
d. Exemplary Communications Networks
Communications network 120 may include one or more communication networks or medium of digital data communication. Examples of communication network 120 include a local area network (âLANâ), a wireless LAN, a RF network, a Near Field Communication (NFC) network, (e.g., a âWiFiâ network), a wireless Metropolitan Area Network (MAN) connecting multiple wireless LANs, NFC communication link(s), and a wide area network (âWANâ), e.g., the Internet. Consistent with embodiments of the present disclosure, communications network 120 may include the Internet and any publicly accessible network or networks interconnected via one or more communication protocols, including, but not limited to, hypertext transfer protocol (HTTP) and transmission control protocol/internet protocol (TCP/IP). Communications protocols consistent with the disclosed embodiments also include protocols facilitating data transfer using radio frequency identification (RFID) communications and/or NFC. Moreover, communications network 120 may also include one or more mobile device networks, such as a GSM network or a PCS network, allowing client device 104 to send and receive data via applicable communications protocols, including those described herein.
e. Exemplary Peer Systems
Referring back to FIG. 1 , peer systems 160 may include one or more computing systems configured to execute software instructions to perform one or more operations consistent with disclosed embodiments. In some aspects, peer systems 160 may include computing components configured to store, maintain, and generate data and software instructions. For example, each of peer systems 160 may include one or more computing devices (e.g., a server, network computer, or mainframe computer) having one or more processors that may be selectively activated or reconfigured by executable instructions (e.g., computer programs) stored in one or more tangible, non-transitory computer-readable storage devices.
In an embodiment, one or more of peer system 160 may be configured to receive, from client device 104 across network 120 , information associated with a distribution of, transaction involving, or other action associated with one or more assets tracked within hybrid blockchain ledgers consistent with the disclosed embodiments. By way of example, the received information may include, but is not limited to, data identifying at least a portion of the tracked assets, data identifying a current owner of the portion of the tracked assets (e.g., user 110 ) (or a obfuscated owner identifier), and further, encrypted copies of and/or hash values representative of the rules engine and event triggers list.
In some aspects, the one or more of peer systems 160 may be configured (e.g., by the executed software programs) to validate the received information and to generate a new block of the hybrid blockchain ledger that includes the received information, either alone (e.g., using a âone transaction, one blockâ paradigm) or in combination with information identifying additional distributions, transactions, or other actions associated with one or more tracked assets (e.g., as a multiple-transaction block). The one or more of peer systems 160 may be further configured to generate one or more hashes representative of the new block, which may be appended to a prior version of the hybrid private-public ledger along with the newly generated block. In some aspects, the one or more of peer system 160 may maintain the updated versions of the hybrid private-public ledger (i.e., the latest, longest hybrid private-public ledger), and may provide the updated version of the hybrid private-public ledger to client devices 102 , 104 , and/or 106 (and additionally or alternatively, other client devices associated with other users) upon receipt of a request across network 120 and/or at regular or predetermined intervals. In some aspects, one or more of peer systems 140 .
In certain instances, and in addition to a connection with network 120 , peer systems 160 may be interconnected across a peer-to-peer network (not depicted in FIG. 1 ) using any of the wired or wireless communications protocols outlined above. Further, in some instances, one or more of peer systems 160 may function as a âminer,â where any miner may be compensated in units of a virtual currency (e.g., Bitcoinâ¢) for validating the received data and for generating updated versions of the hybrid blockchain ledger.
II. Exemplary Processes for Tracking Assets Using Hybrid Blockchain Ledgers
In some embodiments, client devices 102 , 104 , and/or 106 may execute one or more stored applications that enable corresponding users to track, in conjunction with peer systems 150 and other components of computing environment 100 , a disposition and distribution of one or more assets using conventional, publicly available and transparent blockchain ledgers. In some aspects, the use of public blockchain ledgers to track ownership, disposition, and distribution of actual and/or virtual assets (e.g., unit of virtual currencies, such as Bitcoinâ¢, unit of other financial instruments and securities, physical assets, etc.) may present advantages over existing centralized server systems, such as those provided by financial institutions that leverage private ledgers.
a. Asset Tracking Using Conventional Blockchain Ledgers
FIG. 2 is a schematic diagram of an exemplary structure 200 of a conventional blockchain ledger, which may be generated through the interaction of components of computing environment 100 . For example, as described in reference to FIG. 2 , a user (e.g., user 110 ) may be associated with a device (e.g., client device 104 ) that executes a stored software application (e.g., a wallet application) capable of obtaining a current version of a conventional blockchain ledger from one or more networked computer systems (e.g., one of peer systems 160 configured to âmineâ broadcasted transaction data and update ledgers). In some aspects, the current version of a conventional blockchain ledger may represent a âlongestâ blockchain ledger than includes a maximum number of discrete âblocks,â which may identify transactions that transfer, distribute, etc., portions of tracked assets among various owners, including user 110 .
For example, client device 104 may obtain the current blockchain ledger, and may process the block chain ledger to determine that a prior owner (e.g., user 108 ) transferred ownership of a portion of the tracked assets to user 110 in a corresponding transaction (e.g., transaction 202 , schematically illustrated in FIG. 2 ). As described above, one or more of peer systems 160 may have previously data verified, processed, and packed associated with transaction 202 may be into a corresponding block of the conventional blockchain using any of the exemplary techniques described above and/or apparent to one of ordinary skill in the art.
In some aspects, as illustrated in FIG. 2 , transaction 202 may include input data that references one or more prior transactions (e.g., transactions that transferred ownership of the tracked asset portion to user 108 ), and further, output data that includes instructions for transferring the tracked asset portion to one or more additional owners (e.g., user 110 ). For example, input data consistent with the disclosed embodiments may include, but is not limited to, a cryptographic hash of the one or more prior transactions (e.g., hash 202 A) and the set of rules and triggers associated with the assets while the output data consistent with the disclosed embodiments may include, but is not limited to, a quantity or number of units of the tracked asset portion that are subject to transfer in transaction 202 and a public key of the recipient (e.g., public key 202 B of user 110 ).
Further, in some aspects, the transaction data may include a digital signature 202 C of user 108 (e.g., the prior owner), which may be applied to hash 202 A and public key 202 B using a private key 202 D of user 108 through any of a number of techniques apparent to one of skill in the art and appropriate to the conventional blockchain ledger architecture. By way of example, the presence of user 108 's public key within transaction data included within the conventional blockchain ledger may enable client device 104 and/or peer systems 160 to verify user 108 's digital signature, as applied to data associated with transaction 202 .
In an embodiment, user 110 may elect to further transfer the tracked asset portion to an additional user (e.g., user 112 ). For example, as described above, client device 104 may execute one or more software applications (e.g., wallet applications) that generate input and output data specifying a transaction (e.g., transaction 204 of FIG. 2 ) that transfers ownership of the tracked asset portion from user 110 to user 112 , and further, that transmit the generated data to one or more of peer systems 160 for verification, processing (e.g., additional cryptographic hashing) and inclusion into a new block of the clock-chain ledger.
For example, data specifying transaction 204 may include, but is not limited to, a cryptographic hash 204 A of prior transaction 202 , a quantity or number of units of the tracked asset portion that are subject to transfer in transaction 204 , and a public key of the recipient (e.g., public key 204 B of user 112 ). Further, in some aspects, the data specifying transaction 204 may include a digital signature 204 C of the user 110 , which may be applied to hash 204 A and public key 204 B using a private key 204 D of user 110 using any of the exemplary techniques described above. Further, and by way of example, the presence of user 110 's public key 202 B within transaction data included within the conventional blockchain ledger may enable various devices and systems (e.g., client devices 106 , 106 , and/or 108 , peer systems 160 , etc.) to verify user 110 's digital signature 204 C, as applied to data specifying transaction 204 .
As described above, one or more of peer systems 160 may receive the data specifying transaction 204 from client device 104 . In certain instances, peer systems 160 may act as âminersâ for the blockchain ledger, and may competitively process the received transaction data (either alone or in conjunction with other data) to generate additional blocks of the ledger, which may be appended to the blockchain ledger and distributed across peer systems 160 (e.g., through a peer-to-peer network) and to other connected devices of environment 100 .
In some aspects, conventional blockchain ledger architectures described above may enable the public to review content of the ledgers and verify ownerships. Further, the decentralized
CLAIMS
Claims ( 19 )
What is claimed is:
1. An apparatus, comprising:
at least one processor; and
a non-transitory memory storing executable instructions that, when executed by the at least one processor, causes the at least one processor to perform the steps of:
accessing data maintained within a first block of a blockchain ledger, and determining an occurrence of an event based on the accessed data, the first block corresponding to a current owner of an asset, the current owner being associated with a first private cryptographic key;
based on determining the occurrence of the event:
decrypting an encrypted first portion of the accessed data using a master cryptographic key associated with a rules authority, the decrypted first portion identifying a plurality of rules associated with the rules authority;
decrypting an encrypted second portion of the accessed data using a second private cryptographic key associated with a previous owner of the asset, the decrypted second portion of the accessed data identifying a plurality of triggering events, and the blockchain ledger comprising a second block that corresponds to the previous owner;
determining that the event corresponds to at least one of the triggering events; and
when the event corresponds to the at least one of the triggering events, identifying at least one of the plurality of rules that exhibits a relationship with the event; and
performing operations consistent with the at least one of the plurality of rules, the operations comprising:
generating a third block of the blockchain ledger, the third block corresponding to a future owner associated with a third private cryptographic key, and the third block including: (i) the encrypted first portion of the accessed data that is modified for the future owner, (ii) the encrypted second portion of the accessed data that is modified for the future owner, and (iii) event data associated with the determined occurrence of the event, the encrypted second portion of the accessed data being encrypted with the first private cryptographic key of the current owner; and
transmitting the third block to one or more peer systems, the one or more peer systems being configured to record the third block onto the blockchain ledger.
2. The apparatus of claim 1 , wherein the first private cryptographic key is associated with the event.
3. The apparatus of claim 1 , wherein the executed instructions further cause the at least one processor to perform the steps of storing the third block within a secure data repository.
4. The apparatus of claim 3 , wherein the executed instructions further cause the at least one processor to perform the steps of:
generating the master cryptographic key;
storing the generated master cryptographic key in a portion of the secure data repository; and
establishing at least one access permission for the stored master cryptographic key.
5. The apparatus of claim 1 , wherein the executed instructions further cause the at least one processor to perform the steps of:
obtaining trigger-event data identifying one or more candidate triggering events;
encrypting the trigger-event data and transmitting the encrypted trigger-event data to one or more peer systems, the one or more peer systems being configured to record the encrypted trigger-event data onto the blockchain ledger.
6. The apparatus of claim 1 , wherein the executed instructions further cause the at least one processor to perform the steps of:
obtaining rules data specifying one or more candidate rules established by the rules authority;
encrypting the rules data using the master cryptographic key; and
transmitting the encrypted rules data to one or more peer systems, the one or more peer systems being configured to record the encrypted rules data onto the blockchain ledger.
7. The apparatus of claim 1 , wherein:
the event comprises at least one of a referral of a customer from a first line-of-business of an enterprise to a second line-of-business of the enterprise or an activity of the customer involving the second line-of-business;
the at least one rule specifies at least one of a referral reward or a sales reward corresponding to the detected event, the at least one of the referral reward or sales award being associated with a reward type or value;
the first private cryptographic key is associated with a device associated with the current owner, wherein the current owner is at least one of a customer, a first employee of the first line-of- business, or a second employee of the second line-of-business; and
the executed instructions further cause the at least one processor to perform additional operations that initiate a disbursement of at least one of the referral reward to the first employee or the sales reward to the second employee.
8. The apparatus of claim 7 , wherein the executed instructions further cause the at least one processor to perform the steps of:
based on the determined occurrence of the event, decrypting an encrypted third portion of the accessed data using the first private cryptographic key, the decrypted third portion of the accessed data comprising correlation data that maps one or more characteristics of the event to the reward type or value;
extracting information specifying the one or more event characteristics from the accessed data;
determining the reward type or value based on a comparison of at least a portion of the correlation data and the extracted information; and
initiating the disbursement of the at least one referral or sales reward in accordance with the determined at least one reward type or value.
9. A computer-implemented method, comprising:
accessing, using at least one processor, data maintained within a first block of a blockchain ledger, and determining an occurrence of an event based on the accessed data, the first block corresponding to a current owner of an asset, the current owner being associated with a first private cryptographic key;
based on determining the occurrence of the event:
decrypting, using the at least one processor, an encrypted first portion of the accessed data using a master cryptographic key associated with a rules authority, the decrypted first portion identifying a plurality of rules associated with the rules authority;
decrypting, using the at least one processor, an encrypted second portion of the accessed data using a second private cryptographic key associated with a previous owner of the asset, the decrypted second portion of the accessed data identifying a plurality of triggering events, and the blockchain ledger comprising a second block that corresponds to the previous owner;
determining, using the at least one processor, that the event corresponds to at least one of the triggering events; and
when the event corresponds to the at least one of the triggering events, identifying at least one of the plurality of rules that exhibits a relationship with the event and
using the at least one processor, performing operations consistent with the at least one of the plurality of rules, the operations comprising:
generating a third block of the blockchain ledger, the third block corresponding to a future owner associated with a third private cryptographic key, the third block including: (i) the encrypted first portion of the accessed data that is modified for the future owner, (ii) the encrypted second portion of the accessed data that is modified for the future owner, and (iii) event data associated with the determined occurrence of the event, the encrypted second portion of the accessed data being encrypted with the first cryptographic private key of the current owner; and
transmitting the third block to one or more peer systems, the one or more peer systems being configured to record the third block onto the blockchain ledger.
10. The computer-implemented method of claim 9 , further comprising storing the third block within a secure data repository.
11. The computer-implemented method of claim 10 , further comprising:
generating the master cryptographic key;
storing the generated master cryptographic key in a portion of the secure data repository; and
establishing at least one access permission for the stored master cryptographic key.
12. The computer-implemented method of claim 9 , further comprising:
obtaining trigger-event data identifying one or more candidate triggering events;
encrypting the trigger-event data and transmitting the encrypted trigger-event data to one or more peer systems, the one or more peer systems being configured to record the encrypted trigger-event data onto the blockchain ledger.
13. The computer-implemented method of claim 9 , further comprising:
obtaining rules data specifying one or more candidate rules established by the rules authority;
encrypting the rules data using the master cryptographic key; and
transmitting the encrypted rules data to one or more peer systems, the one or more peer systems being configured to record the encrypted rules data onto the blockchain ledger.
14. The computer-implemented method of claim 9 , wherein:
the event comprises at least one of a referral of a customer from a first line-of-business of an enterprise to a second line-of-business of the enterprise or an activity of the customer involving the second line- of-business;
the at least one rule specifies at least one of a referral reward or a sales reward corresponding to the detected event, the at least one of the referral reward or sales award being associated with a reward type or value;
the first private cryptographic key is associated with a device associated with the current owner, wherein the current owner is at least one of a customer, a first employee of the first line-of-business, or a second employee of the second line-of-business; and
the method further comprises performing additional operations that initiate a disbursement of at least one of the referral reward to the first employee or the sales reward to the second employee.
15. A tangible, non-transitory computer-readable medium storing instructions that, when executed by at least one processor, perform a method comprising:
accessing data maintained within a first block of a blockchain ledger, the first block corresponding to a current owner of an asset, the current owner associated with a first private cryptographic key, and determining an occurrence of an event based on the accessed data;
based on determining the occurrence of the event:
decrypting an encrypted first portion of the accessed data using a master cryptographic key associated with a rules authority, the decrypted first portion identifying a plurality of rules associated with the rules authority;
decrypting an encrypted second portion of the accessed data using a second private cryptographic key associated with a previous owner of the asset, the decrypted second portion of the accessed data identifying a plurality of triggering events and the blockchain ledger comprises a second block that corresponds to the previous owner;
determining that the event corresponds to at least one of the triggering events; and
when the event corresponds to the at least one of the triggering events, identifying at least one of the plurality of rules that exhibits a relationship with the event; and
performing operations consistent with the at least one of the plurality of rules, the operations comprising:
generating a third block of the blockchain ledger, the third block corresponding to a future owner associated with a third private cryptographic key, the third block including: (i) the encrypted first portion of the accessed data that is modified for the future owner, (ii) the encrypted second portion of the accessed data that is modified for the future owner, and (iii) event data associated with the determined occurrence of the event, the encrypted second portion of the accessed data being encrypted with the first private cryptographic key of the current owner; and
transmitting the third block to one or more peer systems, the one or more peer systems being configured to record the third block onto the blockchain ledger.
16. The apparatus of claim 1 , wherein the at least one of the triggering events comprises a loss of the first private cryptographic key, and wherein the executed instructions further cause the at least one processor to perform the steps of:
determining that the event corresponds to the loss of the first private cryptographic key; and
when the event corresponds to the loss of the first private cryptographic key, identifying the at least one of the plurality of rules that exhibits a relationship with the loss of the first private cryptographic key, the at least one of the plurality of rules being associated with a generation of a new private cryptographic key; and
performing additional operations consistent with the at least one of the plurality of rules, the additional operations comprising generating the new private cryptographic key.
17. The apparatus of claim 16 , wherein:
the at least one of the triggering events comprises the loss of the first private cryptographic key by the-current owner; and
the additional operations further comprise transmitting the new private cryptographic key to a device of the current owner.
18. The apparatus of claim 16 , wherein the additional operations further comprise:
generating a further element of the blockchain ledger that includes the new private cryptographic key; and
transmitting the further element to the one or more peer systems, the one or more peer systems being configured to record the further element onto the blockchain ledger.
19. The apparatus of claim 1 , wherein the executed instructions further cause the at least one processor to perform the steps of:
modifying the decrypted first portion of the accessed data, the modified first portion comprising a modification to at least one of the plurality of rules;
encrypting the modified first portion using the master cryptographic key;
generating a further element of the blockchain ledger that includes the encrypted modified first portion and the encrypted second portion of the accessed data; and
transmitting the further element to the one or more peer systems, the one or more peer systems being configured to record the further element onto the blockchain ledger.
US16/519,122
2015-08-13
2019-07-23
Systems and method for tracking enterprise events using hybrid public-private blockchain ledgers
Active
2037-06-24
US11810080B2
( en )
Priority Applications (1)
Application Number
Priority Date
Filing Date
Title
US16/519,122
US11810080B2
( en )
2015-08-13
2019-07-23
Systems and method for tracking enterprise events using hybrid public-private blockchain ledgers
Applications Claiming Priority (3)
Application Number
Priority Date
Filing Date
Title
US201562204768P
2015-08-13
2015-08-13
US14/928,838
US10402792B2
( en )
2015-08-13
2015-10-30
Systems and method for tracking enterprise events using hybrid public-private blockchain ledgers
US16/519,122
US11810080B2
( en )
2015-08-13
2019-07-23
Systems and method for tracking enterprise events using hybrid public-private blockchain ledgers
Related Parent Applications (1)
Application Number
Title
Priority Date
Filing Date
US14/928,838
Continuation
US10402792B2
( en )
2015-08-13
2015-10-30
Systems and method for tracking enterprise events using hybrid public-private blockchain ledgers
Publications (2)
Publication Number
Publication Date
US20190347627A1
US20190347627A1 ( en )
2019-11-14
US11810080B2
true
US11810080B2 ( en )
2023-11-07
Family
ID=57994253
Family Applications (18)
Application Number
Title
Priority Date
Filing Date
US14/928,838
Active
2038-01-04
US10402792B2
( en )
2015-08-13
2015-10-30
Systems and method for tracking enterprise events using hybrid public-private blockchain ledgers
US14/931,414
Active
2038-01-15
US10402793B2
( en )
2015-08-13
2015-11-03
Systems and method for tracking subdivided ownership of connected devices using block-chain ledgers
US14/935,829
Active
2039-09-29
US11126975B2
( en )
2015-08-13
2015-11-09
Systems and method for tracking behavior of networked devices using hybrid public-private blockchain ledgers
US14/935,799
Active
2039-04-19
US11151526B2
( en )
2015-08-13
2015-11-09
Systems and methods for establishing and enforcing transaction-based restrictions using hybrid public-private blockchain ledgers
US14/936,812
Abandoned
US20170046693A1
( en )
2015-08-13
2015-11-10
Systems and methods for detecting and resolving data inconsistencies among networked devices using hybrid private-public blockchain ledgers
US14/936,833
Active
2039-08-03
US11308461B2
( en )
2015-08-13
2015-11-10
Systems and methods for tracking and transferring ownership of connected devices using blockchain ledgers
US15/232,100
Active
2038-07-17
US10558955B2
( en )
2015-08-13
2016-08-09
Secure real-time product ownership tracking using distributed electronic ledgers
US15/233,475
Abandoned
US20170046709A1
( en )
2015-08-13
2016-08-10
Product tracking and control system
US15/235,076
Abandoned
US20170046694A1
( en )
2015-08-13
2016-08-11
Secure Tracking Beacons Using Distributed Ledgers
US15/235,090
Active
2038-05-12
US10540641B2
( en )
2015-08-13
2016-08-11
Systems and methods for monitoring construction projects
US15/234,947
Active
2036-11-05
US10282711B2
( en )
2015-08-13
2016-08-11
System and method for implementing hybrid public-private block-chain ledgers
US15/235,199
Active
2038-06-16
US10552805B2
( en )
2015-08-13
2016-08-12
Systems and methods for monitoring referrals
US15/235,528
Active
2037-01-20
US10163080B2
( en )
2015-08-13
2016-08-12
Document tracking on a distributed ledger
US16/196,653
Active
US10692054B2
( en )
2015-08-13
2018-11-20
Document tracking on distributed ledger
US16/353,509
Active
US10824999B2
( en )
2015-08-13
2019-03-14
Systems and methods for implementing hybrid public-private block-chain ledgers
US16/516,914
Active
2037-02-15
US11810079B2
( en )
2015-08-13
2019-07-19
Systems and methods for tracking subdivided ownership of connected devices using block-chain ledgers
US16/519,122
Active
2037-06-24
US11810080B2
( en )
2015-08-13
2019-07-23
Systems and method for tracking enterprise events using hybrid public-private blockchain ledgers
US16/715,471
Active
2038-07-23
US11775945B2
( en )
2015-08-13
2019-12-16
Secure real-time product ownership tracking using distributed electronic ledgers
Family Applications Before (16)
Application Number
Title
Priority Date
Filing Date
US14/928,838
Active
2038-01-04
US10402792B2
( en )
2015-08-13
2015-10-30
Systems and method for tracking enterprise events using hybrid public-private blockchain ledgers
US14/931,414
Active
2038-01-15
US10402793B2
( en )
2015-08-13
2015-11-03
Systems and method for tracking subdivided ownership of connected devices using block-chain ledgers
US14/935,829
Active
2039-09-29
US11126975B2
( en )
2015-08-13
2015-11-09
Systems and method for tracking behavior of networked devices using hybrid public-private blockchain ledgers
US14/935,799
Active
2039-04-19
US11151526B2
( en )
2015-08-13
2015-11-09
Systems and methods for establishing and enforcing transaction-based restrictions using hybrid public-private blockchain ledgers
US14/936,812
Abandoned
US20170046693A1
( en )
2015-08-13
2015-11-10
Systems and methods for detecting and resolving data inconsistencies among networked devices using hybrid private-public blockchain ledgers
US14/936,833
Active
2039-08-03
US11308461B2
( en )
2015-08-13
2015-11-10
Systems and methods for tracking and transferring ownership of connected devices using blockchain ledgers
US15/232,100
Active
2038-07-17
US10558955B2
( en )
2015-08-13
2016-08-09
Secure real-time product ownership tracking using distributed electronic ledgers
US15/233,475
Abandoned
US20170046709A1
( en )
2015-08-13
2016-08-10
Product tracking and control system
US15/235,076
Abandoned
US20170046694A1
( en )
2015-08-13
2016-08-11
Secure Tracking Beacons Using Distributed Ledgers
US15/235,090
Active
2038-05-12
US10540641B2
( en )
2015-08-13
2016-08-11
Systems and methods for monitoring construction projects
US15/234,947
Active
2036-11-05
US10282711B2
( en )
2015-08-13
2016-08-11
System and method for implementing hybrid public-private block-chain ledgers
US15/235,199
Active
2038-06-16
US10552805B2
( en )
2015-08-13
2016-08-12
Systems and methods for monitoring referrals
US15/235,528
Active
2037-01-20
US10163080B2
( en )
2015-08-13
2016-08-12
Document tracking on a distributed ledger
US16/196,653
Active
US10692054B2
( en )
2015-08-13
2018-11-20
Document tracking on distributed ledger
US16/353,509
Active
US10824999B2
( en )
2015-08-13
2019-03-14
Systems and methods for implementing hybrid public-private block-chain ledgers
US16/516,914
Active
2037-02-15
US11810079B2
( en )
2015-08-13
2019-07-19
Systems and methods for tracking subdivided ownership of connected devices using block-chain ledgers
Family Applications After (1)
Application Number
Title
Priority Date
Filing Date
US16/715,471
Active
2038-07-23
US11775945B2
( en )
2015-08-13
2019-12-16
Secure real-time product ownership tracking using distributed electronic ledgers
Country Status (2)
Country
Link
US
( 18 )
US10402792B2
( en )
CA
( 12 )
CA2938519C
( en )
Cited By (2)
* Cited by examiner, â Cited by third party
Publication number
Priority date
Publication date
Assignee
Title
US12452066B2
( en )
2024-01-17
2025-10-21
Bank Of America Corporation
System and method for allocating transfer of data from a data file
US12609917B2
( en )
2024-01-17
2026-04-21
Bank Of America Corporation
System and method for requesting data transfers in a blockchain network
Families Citing this family (1336)
* Cited by examiner, â Cited by third party
Publication number
Priority date
Publication date
Assignee
Title
US10547687B2
( en )
*
2007-01-17
2020-01-28
Eagency, Inc.
Mobile communication device monitoring systems and methods
US9256904B1
( en )
2008-08-14
2016-02-09
Experian Information Solutions, Inc.
Multi-bureau credit file freeze and unfreeze
US20190311447A1
( en )
*
2018-01-08
2019-10-10
Domos. LLC
Method and apparatus for real time, dynamic management of real estate finance, services, and reporting
US11785143B2
( en )
*
2009-01-28
2023-10-10
Virtual Hold Technology Solutions, Llc
System and method for secure storage and management of transitory data using a blockchain
US10565229B2
( en )
2018-05-24
2020-02-18
People.ai, Inc.
Systems and methods for matching electronic activities directly to record objects of systems of record
US12531934B2
( en )
2009-08-27
2026-01-20
People.ai, Inc.
Systems and methods for detecting events based on updates to node profiles from electronic activities
US9652802B1
( en )
2010-03-24
2017-05-16
Consumerinfo.Com, Inc.
Indirect monitoring and reporting of a user's credit data
US10852069B2
( en )
2010-05-04
2020-12-01
Fractal Heatsink Technologies, LLC
System and method for maintaining efficiency of a fractal heat sink
US8706530B2
( en )
2010-09-29
2014-04-22
Dacadoo Ag
Automated health data acquisition, processing and communication system
CA2884070A1
( en )
*
2013-04-10
2014-10-10
Iconic Worldwide Gaming Limited
Method, apparatus, and computer-readable media for enabling real-time competition based on commodities
US11521290B2
( en )
*
2013-05-22
2022-12-06
Patrick Damien O'Brien
Systems and methods for storing contract information on multiple blockchain ledgers
US10981680B2
( en )
2013-10-07
2021-04-20
Shay C. Colson
3-D printed package customization
US9248611B2
( en )
2013-10-07
2016-02-02
David A. Divine
3-D printed packaging
US12503259B2
( en )
*
2013-10-07
2025-12-23
Shay C. Colson
3-D printed packaging
US11716211B2
( en )
2016-10-01
2023-08-01
James L. Schmeling
3D-printed packaging with blockchain integration
US11292241B2
( en )
2016-05-25
2022-04-05
Shay C. Colson
3-D packaging and shipping based on aggregate data
US11292622B2
( en )
2013-10-07
2022-04-05
Shay C. Colson
3D printed vehicle packaging
US10676219B2
( en )
2016-10-01
2020-06-09
Shay C. Colson
Printing packaging in expanded material
US10424404B2
( en )
2013-11-13
2019-09-24
Dacadoo Ag
Automated health data acquisition, processing and communication system and method
US11481808B2
( en )
2014-05-16
2022-10-25
Cardlytics, Inc.
System and apparatus for identifier matching and management
US9858621B1
( en )
2014-05-20
2018-01-02
State Farm Mutual Automobile Insurance Company
Autonomous vehicle technology effectiveness determination for insurance pricing
US11669090B2
( en )
2014-05-20
2023-06-06
State Farm Mutual Automobile Insurance Company
Autonomous vehicle operation feature monitoring and evaluation of effectiveness
US10373259B1
( en )
*
2014-05-20
2019-08-06
State Farm Mutual Automobile Insurance Company
Fully autonomous vehicle insurance pricing
US11295380B2
( en )
2015-01-28
2022-04-05
Crediot, Inc.
Method and system for tracking personal property collateral
US10535063B2
( en )
*
2015-03-13
2020-01-14
First Data Corporation
Systems and methods for securing digital gift cards with a public ledger
US10979410B1
( en )
2015-05-04
2021-04-13
United Services Automobile Association (Usaa)
Systems and methods for utilizing cryptology with virtual ledgers in support of transactions and agreements
US11392944B2
( en )
*
2015-05-20
2022-07-19
Ripple Luxembourg S.A.
Transfer costs in a resource transfer system
US11481771B2
( en )
2015-05-20
2022-10-25
Ripple Luxembourg S.A.
One way functions in a resource transfer system
US10740732B2
( en )
2015-05-20
2020-08-11
Ripple Luxembourg S.A.
Resource transfer system
US11367072B2
( en )
2015-05-20
2022-06-21
Ripple Luxembourg S.A.
Private networks and content requests in a resource transfer system
US11386415B2
( en )
2015-05-20
2022-07-12
Ripple Luxembourg S.A.
Hold condition in a resource transfer system
US11069000B1
( en )
2015-06-16
2021-07-20
BitPagos, Inc.
Payment processing service utilizing a distributed ledger digital asset
US20170011460A1
( en )
*
2015-07-09
2017-01-12
Ouisa, LLC
Systems and methods for trading, clearing and settling securities transactions using blockchain technology
US10339523B2
( en )
*
2015-07-14
2019-07-02
Fmr Llc
Point-to-point transaction guidance apparatuses, methods and systems
US9300678B1
( en )
2015-08-03
2016-03-29
Truepic Llc
Systems and methods for authenticating photographic image data
US10509806B2
( en )
2015-08-17
2019-12-17
Accenture Global Solutions Limited
Recommendation engine for aggregated platform data
US11195177B1
( en )
*
2015-08-21
2021-12-07
United Services Automobile Association (Usaa)
Distributed ledger systems for tracking recurring transaction authorizations
US10311511B2
( en )
2015-09-14
2019-06-04
The Toronto-Dominion Bank
Connected device-based property evaluation
US10095549B1
( en )
*
2015-09-29
2018-10-09
Amazon Technologies, Inc.
Ownership transfer account service in a virtual computing environment
US11915332B2
( en )
*
2015-10-02
2024-02-27
Loyyal Holdings Incorporated
System and process for tokenization and management of liability
WO2017066002A1
( en )
*
2015-10-17
2017-04-20
Banqu, Inc.
Blockchain-based identity and transaction platform
US11494761B2
( en )
2015-11-06
2022-11-08
Cable Television Laboratories, Inc.
Systems and methods for digital asset security ecosystems
US11941588B2
( en )
*
2015-11-06
2024-03-26
Cable Television Laboratories, Inc.
Systems and methods for blockchain virtualization and scalability
JP2019502215A
( en )
*
2015-11-10
2019-01-24
ã¦ã©ã«ãã¼ã ã¢ããï¼ã¨ã«ã¨ã«ã·ã¼
Delivery of prescription drugs
US20170132615A1
( en )
*
2015-11-11
2017-05-11
Bank Of America Corporation
Block chain alias for person-to-person payments
CN109874340B
( en )
*
2015-11-18
2023-06-13
å ¨çæ ·æ¬è§£å³æ¹æ¡è¡ä»½æéå ¬å¸
A distributed system for secure storage and retrieval of encrypted biological specimen data
US10423938B1
( en )
*
2015-11-20
2019-09-24
United Services Automobile Association
Identifying negotiable instrument fraud using distributed ledger systems
US11361286B1
( en )
*
2015-11-20
2022-06-14
United Services Automobile Association (Usaa)
Identifying negotiable instrument fraud using distributed ledger systems
US10586062B1
( en )
*
2015-11-23
2020-03-10
United Services Automobile Association (Usaa)
Systems and methods to track, store, and manage events, rights and liabilities
US10757154B1
( en )
2015-11-24
2020-08-25
Experian Information Solutions, Inc.
Real-time event-based notification system
US9992028B2
( en )
2015-11-26
2018-06-05
International Business Machines Corporation
System, method, and computer program product for privacy-preserving transaction validation mechanisms for smart contracts that are included in a ledger
KR101678795B1
( en )
*
2015-11-30
2016-11-22
ì ì¼êµ¬
Iot-basesd things management system and method using block chain authentification
WO2017095833A1
( en )
*
2015-11-30
2017-06-08
Erik Voorhees
Systems and methods for improving security in blockchain-asset exchange
US20220358185A1
( en )
2015-12-02
2022-11-10
Wells Fargo Bank, N.A.
Traversing data structures for compliance
US11032286B1
( en )
*
2015-12-02
2021-06-08
United Services Automobile Association (Usaa)
Block chain authentication systems and methods
US10833843B1
( en )
2015-12-03
2020-11-10
United Services Automobile Association (USAA0
Managing blockchain access
US11055713B1
( en )
*
2015-12-08
2021-07-06
Wells Fargo Bank, N.A.
Identity services systems and methods
US10521780B1
( en )
2015-12-16
2019-12-31
United Services Automobile Association (Usaa)
Blockchain based transaction management
US10013573B2
( en )
*
2015-12-16
2018-07-03
International Business Machines Corporation
Personal ledger blockchain
US10521973B2
( en )
*
2015-12-17
2019-12-31
International Business Machines Corporation
System for monitoring and enforcement of an automated fee payment
CN108701325B
( en )
*
2015-12-21
2022-11-22
æè¶ç¦å ¬å¸
Self-adjusting transaction system and method therefor
CA3002235C
( en )
2015-12-22
2021-01-26
Thomson Reuters Global Resources Unlimited Company
Methods and systems for identity creation, verification and management
US10692056B1
( en )
*
2015-12-28
2020-06-23
Wells Fargo Bank, N.A.
Systems and methods for dynamic savings based on actual use for network enabled properties
US10423993B2
( en )
*
2015-12-28
2019-09-24
Raise Marketplace, Llc
Authenticating an exchange item in an exchange item marketplace network
US9894485B2
( en )
*
2015-12-28
2018-02-13
Keir Finlow-Bates
Peer-to-peer geolocation system
US10645068B2
( en )
2015-12-28
2020-05-05
United States Postal Service
Methods and systems for secure digital credentials
US10817593B1
( en )
2015-12-29
2020-10-27
Wells Fargo Bank, N.A.
User information gathering and distribution system
US10318747B1
( en )
*
2015-12-30
2019-06-11
Amazon Technologies, Inc.
Block chain based authentication
US20170195336A1
( en )
*
2016-01-05
2017-07-06
Sensormatic Electronics, LLC
Method and System for Non-Authoritative Identity and Identity Permissions Broker and Use Thereof
US10901945B2
( en )
*
2016-01-05
2021-01-26
The grät Network, PBC
Systems and methods concerning tracking models for digital interactions
<span itemprop