US20170046693A1 - Systems and methods for detecting and resolving data inconsistencies among networked devices using hybrid private-public blockchain ledgers - Google Patents

Systems and methods for detecting and resolving data inconsistencies among networked devices using hybrid private-public blockchain ledgers Download PDF

Info

Publication number
US20170046693A1
US20170046693A1 US14/936,812 US201514936812A US2017046693A1 US 20170046693 A1 US20170046693 A1 US 20170046693A1 US 201514936812 A US201514936812 A US 201514936812A US 2017046693 A1 US2017046693 A1 US 2017046693A1
Authority
US
United States
Prior art keywords
data
user
rules
identifying
cryptographic key
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
US14/936,812
Inventor
Perry Haldenby
Rajan MAHADEVAN
John Jong Suk LEE
Paul Mon-Wah CHAN
Orin Del Vecchio
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Toronto-Dominion Bank
Original Assignee
Toronto-Dominion Bank
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US201562204768P priority Critical
Application filed by Toronto-Dominion Bank filed Critical Toronto-Dominion Bank
Priority to US14/936,812 priority patent/US20170046693A1/en
Publication of US20170046693A1 publication Critical patent/US20170046693A1/en
Assigned to THE TORONTO-DOMINION BANK reassignment THE TORONTO-DOMINION BANK ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: HALDENBY, PERRY AARON JONES, CHAN, PAUL MOH-WAH, DEL VECCHIO, ORIN, MAHADEVAN, RAJAN, LEE, JOHN JONG SUK
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/04Payment circuits
    • G06Q20/06Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • G06Q20/065Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
    • G06Q20/0655Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash e-cash managed centrally
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60Protecting data
    • G06F21/62Protecting access to data via a platform, e.g. using keys or access control rules
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60Protecting data
    • G06F21/64Protecting data integrity, e.g. using checksums, certificates or signatures
    • G06F21/645Protecting data integrity, e.g. using checksums, certificates or signatures using a third party
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/06Resources, workflows, human or project management, e.g. organising, planning, scheduling or allocating time, human or machine resources; Enterprise planning; Organisational models
    • G06Q10/063Operations research or analysis
    • G06Q10/0631Resource planning, allocation or scheduling for a business operation
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/06Resources, workflows, human or project management, e.g. organising, planning, scheduling or allocating time, human or machine resources; Enterprise planning; Organisational models
    • G06Q10/063Operations research or analysis
    • G06Q10/0631Resource planning, allocation or scheduling for a business operation
    • G06Q10/06311Scheduling, planning or task assignment for a person or group
    • G06Q10/063114Status monitoring or status determination for a person or group
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/08Logistics, e.g. warehousing, loading, distribution or shipping; Inventory or stock management, e.g. order filling, procurement or balancing against orders
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/10Office automation, e.g. computer aided management of electronic mail or groupware; Time management, e.g. calendars, reminders, meetings or time accounting
    • G06Q10/103Workflow collaboration or project management
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/10Office automation, e.g. computer aided management of electronic mail or groupware; Time management, e.g. calendars, reminders, meetings or time accounting
    • G06Q10/109Time management, e.g. calendars, reminders, meetings, time accounting
    • G06Q10/1093Calendar-based scheduling for a person or group
    • G06Q10/1097Task assignment
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/04Payment circuits
    • G06Q20/06Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • G06Q20/065Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/10Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G06Q20/102Bill distribution or payments
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/36Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
    • G06Q20/367Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes involving electronic purses or money safes
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/382Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3829Payment protocols; Details thereof insuring higher security of transaction involving key management
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/40Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401Transaction verification
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/40Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401Transaction verification
    • G06Q20/4016Transaction verification involving fraud or risk level assessment in transaction processing
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/40Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/405Establishing or using transaction specific rules
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce, e.g. shopping or e-commerce
    • G06Q30/02Marketing, e.g. market research and analysis, surveying, promotions, advertising, buyer profiling, customer management or rewards; Price estimation or determination
    • G06Q30/0207Discounts or incentives, e.g. coupons, rebates, offers or upsales
    • G06Q30/0214Referral award systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/08Insurance, e.g. risk analysis or pensions
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/12Accounting
    • G06Q40/128Check-book balancing, updating or printing arrangements
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
    • G06Q50/08Construction
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
    • G06Q50/10Services
    • G06Q50/18Legal services; Handling legal documents
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/06Network architectures or network communication protocols for network security for supporting key management in a packet data network
    • H04L63/061Network architectures or network communication protocols for network security for supporting key management in a packet data network for key exchange, e.g. in peer-to-peer networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/06Network architectures or network communication protocols for network security for supporting key management in a packet data network
    • H04L63/062Network architectures or network communication protocols for network security for supporting key management in a packet data network for key distribution, e.g. centrally by trusted party
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for supporting authentication of entities communicating through a packet data network
    • H04L63/0876Network architectures or network communication protocols for network security for supporting authentication of entities communicating through a packet data network based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communication
    • H04L9/08Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0816Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communication
    • H04L9/08Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0861Generation of secret information including derivation or calculation of cryptographic keys or passwords
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communication
    • H04L9/08Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0891Revocation or update of secret information, e.g. encryption key update or rekeying
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communication
    • H04L9/08Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0894Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communication
    • H04L9/32Cryptographic mechanisms or cryptographic arrangements for secret or secure communication including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3247Cryptographic mechanisms or cryptographic arrangements for secret or secure communication including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N5/00Details of television systems
    • H04N5/76Television signal recording
    • H04N5/91Television signal processing therefor
    • H04N5/913Television signal processing therefor for scrambling ; for copy protection
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q2220/00Business processing using cryptography
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q2220/00Business processing using cryptography
    • G06Q2220/10Usage protection of distributed data files
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q2230/00Voting or election arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2209/00Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
    • H04L2209/24Key scheduling, i.e. generating round keys or sub-keys for block encryption
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2209/00Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
    • H04L2209/38Chaining, e.g. hash chain or certificate chain
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2209/00Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
    • H04L2209/56Financial cryptography, e.g. electronic payment or e-cash
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/04Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H04L63/0435Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload wherein the sending and receiving network entities apply symmetric encryption, i.e. same key used for encryption and decryption
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/04Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H04L63/0442Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for supporting authentication of entities communicating through a packet data network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/12Applying verification of the received information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N5/00Details of television systems
    • H04N5/76Television signal recording
    • H04N5/91Television signal processing therefor
    • H04N5/913Television signal processing therefor for scrambling ; for copy protection
    • H04N2005/91307Television signal processing therefor for scrambling ; for copy protection by adding a copy protection signal to the video signal
    • H04N2005/91342Television signal processing therefor for scrambling ; for copy protection by adding a copy protection signal to the video signal the copy protection signal being an authentication signal
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02PCLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/80Management or planning
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y04INFORMATION OR COMMUNICATION TECHNOLOGIES HAVING AN IMPACT ON OTHER TECHNOLOGY AREAS
    • Y04SSYSTEMS INTEGRATING TECHNOLOGIES RELATED TO POWER NETWORK OPERATION, COMMUNICATION OR INFORMATION TECHNOLOGIES FOR IMPROVING THE ELECTRICAL POWER GENERATION, TRANSMISSION, DISTRIBUTION, MANAGEMENT OR USAGE, i.e. SMART GRIDS
    • Y04S10/00Systems supporting electrical power generation, transmission or distribution
    • Y04S10/50Systems or methods supporting the power network operation or management, involving a certain degree of interaction with the load-side end user applications

Abstract

The disclosed embodiments include computerized systems and methods that generate secured blockchain-based ledger structures that facilitate event-based control of tracked assets. In one embodiment, an apparatus associated with a centralized 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. In some aspects, the detected event may correspond to a dispute involving one or more terms or conditions of a contractual agreement between a first party and one or more second parties, and the performed operations may resolve the dispute.

Description

    CROSS-REFERENCE TO RELATED APPLICATIONS
  • This application claims the benefit of U.S. Provisional Patent Application No. 62/204,768, filed Aug. 13, 2015, which is expressly incorporated by reference herein to its entirety.
  • 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 that facilitate event-based control of tracked assets.
  • Background
  • Today, virtual and crypto-currencies, such as Bitcoin™, are gaining acceptance as viable mechanisms for performing purchase transactions and other financial services transactions. The transfer of units of these virtual and crypto-currencies between owners, which is essential to the ultimate success of these virtual and crypto-currencies, relies on a robust blockchain ledger structure that, due to its public nature, redundant verification, and resistance to fraudulent activity, offers advantages over existing centralized server systems. Despite its many advantages, conventional systems exhibit significant flaws, especially when used to track assets in secure, high-risk, and/or sensitive applications and when used to resolve inconsistencies within data associated with the tracked assets.
  • SUMMARY
  • The disclosed embodiments relate to computerized systems and methods that generate secured blockchain-based ledger structures that facilitate event-based control of tracked assets.
  • In an 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, obtaining notification data identifying a dispute involving a contractual agreement between a first party and one or more second parties, and 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 some aspects, the decrypted first data portion may identify a plurality of triggering events controlled by a rules authority, and the decrypted second data portion may identify a plurality of rules associated with the triggering events. The executed instructions may further cause the at least one processor to perform the steps of establishing that the identified dispute corresponds to at least one of the triggering events, identifying, based on the detected second data portion, at least one of the rules that exhibits a causal relationship with the detected first event, and generating an electronic command to perform one or more operations to resolve the identified dispute consistent with the at least one identified rule.
  • The disclosed embodiments also include a computer-implemented method that accesses, using at least one processor, data corresponding to at least one blockchain ledger, that obtains, using the at least one processor, notification data identifying a dispute involving a contractual agreement between a first party and one or more second parties, and using the at least one processor, decrypts (0 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 some aspects, the decrypted first data portion may identify a plurality of triggering events controlled by a rules authority, and the decrypted second data portion may identify a plurality of rules associated with the triggering events. The method may also include establishing, using the at least one processor, that the identified dispute corresponds to at least one of the triggering events, identifying, using the at least one processor, and based on the detected second data portion, at least one of the rules that exhibits a causal relationship with the detected first event, and generating, using the at least one processor, an electronic command to perform one or more operations to resolve the identified dispute consistent with the at least one identified rule.
  • In further embodiments, a tangible, non-transitory computer-readable medium storing instructions that, when executed by at least one processor, cause the at least one processor to perform a method that includes accessing data corresponding to at least one blockchain ledger, obtaining notification data identifying a dispute involving a contractual agreement between a first party and one or more second parties, and 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 some aspects, the decrypted first data portion may identify a plurality of triggering events controlled by a rules authority, and the decrypted second data portion may identify a plurality of rules associated with the triggering events. The method may also include the steps of establishing that the identified dispute corresponds to at least one of the triggering events, identifying, based on the detected second data portion, at least one of the rules that exhibits a causal relationship with the detected first event, and generating an electronic command to perform one or more operations to resolve the identified dispute 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.
  • FIGS. 4 and 5 are flowcharts of exemplary processes for performing event-based operations on assets 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
  • Systems 140, 141, and 146 may be computing systems configured to execute software instructions to perform one or more operations consistent with disclosed embodiments. In one aspect, systems 140 and 141 may be associated with business entities 150 and 151 (e.g., a financial institution) that provide financial accounts, financial services transactions, and investment services one or more users (e.g., customers of the business entities 150 and 151). In further aspects, system 146 may be associated with a neutral third party (e.g., clearinghouse entity 152) that, among other things, may resolve disputes regarding contractual terms, conditions, and performance between financial institutions 150 and 151 and between users 108, 110, and 112. In some aspects, systems 140, 141, and/or 146 may be distributed systems that may include computing components distributed across one or more networks, such as network 120, or other networks.
  • In one aspect, systems 140, 141, and 146 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). Similarly, system 141 may include one or more servers (e.g., server 143) and tangible, non-transitory memory devices (e.g., data repository 145), and system 146 may include one or more servers (e.g., server 147) and tangible, non-transitory memory devices (e.g., data repository 149).
  • Server 142 (and additionally or alternatively, servers 143 and 147) 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 (and additionally or alternatively, servers 143 and 147) 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, servers 142, 143, and/or 147 (or other computing components of systems 140, 141, and/or 146) 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 interlace (GUI).
  • In further aspects, servers 142, 143, and/or 147 (or other computing components of systems 140, 141, and/or 146) 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 entities 150 and 151 and clearinghouse entity 152. 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, servers 142, 143, and/or 147 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, servers 142, 143, and/or 147 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 “rules entity” capable of regulating transactions involving assets (e.g., units of virtual currency, units of various financial instruments, physical assets, connected devices, real estate, etc.) tracked within hybrid public-private ledgers consistent with the disclosed embodiments. Further, business entity 150, acting as the rules authority, may be capable of regulating transfers of ownership of these assets, either singly or jointly through subdivided interests, 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
  • In additional embodiments, one or more computing components of system 141 (e.g., server 143) and/or system 146 (e.g., server 147) may perform one or more of the exemplary operations described above in reference to system 140, which facilitate a capability of business entities 150 and 151 (and any additional or alternate financial institutions within environment 100) and/or clearinghouse entity 152 to function as a “rules authority” within computing environment 100.
  • 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 one 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 establish 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 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 Private-Public 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. Tracking Assets 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 that 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 verified, processed, and packed data associated with transaction 202 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 202A) 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 202B of user 110).
  • Further, in some aspects, the transaction data may include a digital signature 202C of user 108 (e.g., the prior owner), which may be applied to hash 202A and public key 202B using a private key 202D 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 204A 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 204B of user 112). Further, in some aspects, the data specifying transaction 204 may include a digital signature 204C of the user 110, which may be applied to hash 204A and public key 204B using a private key 204D 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 202B within transaction data included within the conventional blockchain ledger may enable various devices and systems (e.g., client devices 102, 104, and/or 106, peer systems 160, etc.) to verify user 110's digital signature 204C, 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 nature of conventional blockchain ledgers may also enable multiple distributed networks to verify the contents of a single ledger. The resulting redundancy may render conventional blockchain ledger architecture more robust than centralized server systems, and effectively eliminate the falsification of ledger data by malicious parties.
  • Despite these advantages, conventional blockchain ledger architectures may exhibit significant flaws when implemented by secured, high-risk systems. By way of example, unencrypted conventional ledger blocks may represent a security concern for transactions of sensitive nature, and further, may represent a privacy concern for members of the general public. For instance, information indicative of an interaction of a prior asset owner and a corresponding device, as present within conventional blockchain ledgers, may represent private information that should not be available to future owners, let alone members of the public.
  • Further, if an owner were to lose or misplace a corresponding private key, the distributed nature of conventional blockchain ledger architectures, such as those described above, provide little recourse to recover possession of the one or more tracked assets. In certain aspects, the rigidity and inflexibility of these conventional blockchain ledger architectures, and their inability to adapt to changing circumstances (e.g., loss of private keys, theft of tracked assets due to fraudulent or malicious activity), often results in volatility in the usage of the tracked assets and an erosion in a public trust of conventional blockchain ledgers.
  • Thus, there is a need for improved systems and methods that not only enhance the security of blockchain ledger architectures for use high-risk, sensitive applications, but that also provide a framework that provides owners or holders of assets tracked by blockchain ledger architectures with recourse in an event of fraud or malicious activity, while maintaining the public availability and verification characteristic of blockchain ledgers.
  • b. Exemplary Hybrid Public-Private Blockchain Ledger Architectures
  • The disclosed embodiments address these and other problems associated with conventional block-ledger architectures in a technical manner, by providing computer-implemented systems and methods that augment a conventional blockchain ledger with a private-master encryption key architecture that, in conjunction with an owner's pair of public and private blockchain keys, selectively encrypt ledger data to protect both a privacy of owners of tracked assets and a confidentiality of existing instruction sets maintained within the blockchain ledger.
  • Further, by incorporating an encrypted rules engine and corresponding list of triggering events (e.g., an event triggers list) into each block of the conventional blockchain ledger architecture (and thus generating a hybrid, public-private blockchain architecture), computer-implemented systems and methods consistent with the disclosed embodiments may perform operations that provide owners or holders tracked assets with recovery options in an event of fraud or malicious activity, while maintaining the public availability and verification characteristic of conventional blockchain ledgers.
  • In certain aspects, discrete data blocks of the conventional blockchain ledgers (e.g., as outlined above in reference to FIG. 2) and of the hybrid blockchain ledgers (e.g., as described in reference to FIG. 3) may include common elements of data that may specify transactions that distribute, transfer, and/or otherwise act upon portions of tracked assets. For example, these common data elements may include, but are not limited to, input data that references one or more prior transactions (e.g., a cryptographic hash of the one or more prior transactions), output data that includes instructions for transferring the tracked asset portion to one or more additional owners (e.g., a quantity or number of units of the tracked asset portion that are subject to the transaction and a public key of the recipient) and further, a digital signature applied to the input and/or output data using a corresponding public key of a current owner of the tracked asset portion. The disclosed embodiments are, however, not limited to exemplary transactions that include a transfer of tracked assets and to the exemplary data elements described above, and in further embodiments, discrete blocks of the hybrid blockchain ledgers may represent any additional or alternate transaction appropriate to the tracked assets, and further, any additional or alternate data appropriate to the tracked assets and to the transaction.
  • In contrast to the conventional blockchain ledgers described above, the disclosed embodiments may establish a “centralized authority” capable of vetting real-time transactions (e.g., distributions, transfers, and/or other actions) involving portions of assets tracked within the exemplary hybrid blockchain ledger architectures described herein, and further, of establishing and maintaining rules (e.g., through a rules engine and corresponding list of triggering events) that facilitate regulatory-based, policy-based, and customer-specified controls of transactions involving the tracked assets (e.g., units of virtual currency, etc.).
  • For example, and as described above, business entity 150 may represent the centralized authority, and one or more computing components of system 150 may perform operations that establish the rules engine and the list of triggering events, which may be stored within a secure data repository (e.g., data repository 144). In some aspects, the generated and stored rules engine may identify one 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 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 racked in the hybrid public-private ledger, etc.). Further, and as described above, the generated and stored list of triggering events may include information that specifies 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, transactions, and/or actions associated with assets tracked within the hybrid public-private ledger (e.g., the triggering events).
  • In some aspects, system 140 may establish one or more of the rules and/or triggering events to reflect regulations and/or policies promulgated by governmental entity, a financial regulator, and/or the centralized authority. For example, system 140 may establish a loss of a private key by user 110 as a “triggering event” that would cause system 140 to perform operations that create a new transaction and generate a new pair of public and private blockchain keys for user 110 in response to a verification of particular authentication credentials. In other aspects, system 140 may establish 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 a particular distribution of tracked assets (e.g., recurring bill payments, distributions to other owners, etc.) in response to an accident involving user 110 and/or user 110's death (e.g., triggering events).
  • In further contrast to the conventional blockchain ledgers described above, one or more computing components of system 140 (e.g., server 142 upon execution of stored instructions) may generate additional cryptographic keys that facilitate the exemplary regulation of transactions (e.g., distributions, transfers, and/or actions) involving assets tracked within the hybrid public-private ledger. By way of example, system 140 may generate a master cryptographic key with which system 140 may encrypt the generated and stored rules engine. In some 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.
  • System 140 may also perform operations that encrypt the generated list of triggering events, either alone or in conjunction with metadata identifying the centralized authority and/or information facilitating a processing of the transaction blocks throughout the hybrid blockchain ledger. In certain aspects, system 140 may also perform operations that generate and maintain additional private cryptographic keys (e.g., a private “crypto” key) associated with each owner associated with the assets tracked within the hybrid blockchain ledger (e.g., users 108, 110, and/or 112) and further, that would enable the owners to decrypt and access the list of triggering events and additionally or alternatively, the metadata identifying the centralized authority. System 140 may store copies of the generated private crypto keys in a portion of data repository 144. Furthermore, system 140 may also perform operations that provide corresponding ones of the private crypto keys to users 108, 110, and/or 112 through secure, non-accessible and/or out-of-band communications.
  • The disclosed embodiments may also be configured to communicate the encrypted and/or hashed rules engine and list of triggering events to owners of and/or user associated with the tracked assets through “in-band” communication processes, such as through an incorporation of the encrypted rules engine and list of triggering events into the transaction blocks of the hybrid blockchain ledger. For example, system 140 may perform operations that hash the encrypted rules engine and list of triggering events into a genesis block of the hybrid blockchain ledger, the contents of which may be incorporated (e.g., by client devices 102, 104, and/or 106, peer systems 160, etc.) into each of the subsequent transaction blocks generated and appended to the hybrid blockchain ledger. In some aspects, by incorporating the hashed and encrypted rules engine and list of triggering events into blocks of the hybrid blockchain ledger, the disclosed embodiments may ensure that the established rules are followed even in an event of actions by malicious parties to disrupt the tracked assets (e.g., instances of Bitcoin™ peeling, etc.)
  • Further, in some instances, the additional private crypto keys held by the owners and/or users (e.g., stored in corresponding ones of client devices 102, 104, and/or 106 and accessible to executable application programs) may enable the owners and/or users to access the encrypted list of triggering events maintained within the hybrid blockchain ledger. The owners and/or user may, through corresponding client devices, view the individual events that, when detected by system 140, could cause system 140 to perform operations that recover, authorize, audit, and/or verify the transaction and/or ownership data included within the hybrid blockchain ledger (e.g., associated with corresponding portions of the tracked assets).
  • In certain aspects, one or more computing components of system 140 may perform operations that modify portions of the stored rules and/or list of triggering events, e.g., in response to changes in regulations and/or policies, in response to additional owner input, etc. In order to access and modify the generated rules engine (and/or the list of triggering events) maintained within the hybrid blockchain ledger, system 140 may leverage the stored master cryptographic key to access and modify the hashed and encrypted rules engine. System 140 may, in certain instances, encrypt and re-hash the modified rules engine and submit the encrypted and hashed modified rules engine to one or more of peer systems 160 for inclusion in a block of the hybrid blockchain ledger. For example, the one or more of peer systems 160 may incorporate the hashed and encrypted modified rules engine into the hybrid blockchain ledger as a special transaction (e.g., a “0” value transaction), such that the hybrid blockchain ledger tracks each change within the modified rules engine.
  • FIG. 3 is a schematic diagram of illustrating an exemplary structure 300 of a hybrid, public-private blockchain ledger, which may be generated through the interaction of components of computing environment 100, in accordance with the disclosed embodiments. For example, as described in reference to FIG. 3, users 108, 110, and 112 may be associated with corresponding devices (e.g., client devices 102, 104, and 106), which may be configured to execute one or more stored software applications (e.g., a wallet application) capable of obtaining a current version of a hybrid blockchain ledger from one or more networked computer systems (e.g., one of peer systems 160 configured to “mine” broadcast transactions and update ledgers).
  • Further, in some aspects, and as described above, a system associated with a centralized authority (e.g., system 140 associated with business entity 150) may generate a rules engine that regulate transactions involving the assets tracked by the hybrid blockchain ledger (e.g., distributions, transfers of ownership, other actions, etc.), and further, a list of triggering events that, upon detection by system 140, trigger an initiation of one or more of the distributions, transfers, and/or other actions regulated by the generated rules engine. In additional aspects, and as described above, system 140 may generate a master encryption key (e.g., master key 301 of FIG. 3), and may generate additional private “crypto” keys 302A and 302B, which may be associated with corresponding ones of users 108 and 110. In some aspects, system 140 may maintain master key 301 and/or private crypto keys 302A, 302B, and 302C in a portion of data repository 144 and provide private crypto keys 302A, 302B, and 302C to users 108, 110, and 112 through secure, out-of-band communications. System 140 may, in additional aspects, encrypt the generated rules engine and the generated list of triggering events, and further, perform operations that hash the encrypted rules engine and list of triggering events into a genesis block of the hybrid blockchain ledger (e.g., genesis block 304).
  • In an embodiment, one of the users (e.g., user 108) may own and/or control a portion of the tracked assets. For example, a device associated with user 108 (e.g., client device 102) may execute a stored software application (e.g., a wallet application) capable of obtaining a current version of a hybrid blockchain ledger, including genesis block 304, from one or more networked computer systems (e.g., one of peer systems 160 configured to “mine” broadcast transactions and update ledgers). In some aspects, the current version of a hybrid blockchain ledger may represent a “longest” blockchain ledger that includes a maximum number of discrete “blocks,” which may identify transactions that transfer, distribute, etc., portions of tracked assets among various owners, including user 108.
  • For example, client device 102 may obtain the current hybrid blockchain ledger, and may process the hybrid blockchain ledger to determine that a prior owner transferred ownership of a portion of the tracked assets to user 108 in a corresponding transaction (e.g., transaction 306, schematically illustrated in FIG. 3). As described above, one or more of peer systems 160 may have previously verified, processed, and packed data associated with transaction 306 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. 3, data specifying transaction 306 may include input data that references one or more prior transactions (e.g., transactions that transferred ownership of the tracked asset portion to the prior owner), and further, output data that includes instructions for transferring the tracked asset portion to user 108. For example, and as described above, 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 306A), and 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 306 and a public key 306B of user 108 (Le., the recipient of the tracked asset portion transferred in transaction 306). Further, in some aspects, the transaction data may include a digital signature 306C of the prior owner, which may be applied to hash 306A and public key 306B using a private key of the prior owner through any of a number of techniques apparent to one of skill in the art and appropriate to the conventional blockchain ledger architecture.
  • Further, and in contrast to the conventional blockchain ledger architectures described above, transaction 306 may also include encrypted and/or hashed copies of rules engine 324 and event trigger list 322. In certain aspects, a device of the prior owner (e.g., which may execute one or more software applications) may access genesis block 304 (e.g., from the current version of the hybrid blockchain ledger obtained from one or more of peer systems 160), may parse genesis block 306, and may extract copies of the encrypted and/or hashed rules engine 324 and event trigger list 322. The prior owner's device may transmit to one or more of peer systems 160 along with the hash 306A, public key 306B, and digital signature 306C for verification, processing (e.g., additional cryptographic hashing) and inclusion into a new block of the hybrid blockchain ledger.
  • In an embodiment, user 108 may elect to further transfer that tracked asset portion to an additional user (e.g., user 110). For example, as described above, the one or more software applications executed by client device 102 may cause client device 102 to perform operations that generate input and output data specifying a new transaction (e.g., transaction 308 of FIG. 3) that transfers ownership of the tracked asset portion from user 108 to user 110, 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 hybrid blockchain ledger.
  • For example, data specifying transaction 308 may include, but is not limited to, a cryptographic hash 308A of prior transaction 306, a quantity or number of units of the tracked asset portion that are subject to transfer in transaction 308, and a public key of the recipient (e.g., public key 308B of user 110). Further, in some aspects, the data specifying transaction 308 may include a digital signature 308C of the user 108, which may be applied to hash 308A and public key 308B using a private key 308D of user 108 using any of the exemplary techniques described above. Further, and by way of example, the presence of user 108's public key within transaction data included within the conventional blockchain ledger may enable various devices and systems (e.g., client devices 102, 104, and/or 106, peer systems 160, etc.) to verify the user 108's digital signature 308C, as applied to data specifying transaction 308.
  • Additionally, and as described above, client device 102 may also parse data specifying prior transaction 306 (e.g., as obtained from the current version of the hybrid blockchain ledger) and extract encrypted and/or hashed copies of rules engine 324 and event trigger list 322. In certain aspects, client device 102 may append the encrypted and/or hashed copies of rules engine 324 and event trigger list 322 to the data specifying transaction 308 (e.g., cryptographic hash 308A, public key 308B, and digital signature 308C), and transmit the data specifying transaction 308 to one or more of peer systems 160 for verification, processing (e.g., additional cryptographic hashing) and inclusion into a new block of the hybrid blockchain ledger.
  • Further, and as described above, private crypto key 302A may enable client device 102 (e.g., associated with user 108) to access encrypted event trigger list 322 upon extracted from the hybrid blockchain ledger, as described above. In some embodiments, private crypto key 302A may provide client device 102 with read-only access to the encrypted event trigger list 322. In some aspects, client device 102 may obtain private crypto key 302A from system 140 using secured out-of-band communications, and additionally or alternatively, as input provided by user 108 through a web page or other graphical user interface (GUI) presented by client device 104.
  • In an embodiment, ownership of the tracked asset portion may be transferred from user 108 to user 110 upon verification and publication of the data specifying transaction 308 within a corresponding block of the hybrid blockchain ledger by peer systems 160. In further embodiments, and as described above, user 110 may elect to further transfer that tracked asset portion to yet another user (e.g., user 112). For example, as described above, the one or more software applications executed by client device 104 may cause client device 104 to perform operations that generate input and output data specifying a new transaction (e.g., transaction 310 of FIG. 3) 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 hybrid blockchain ledger.
  • For example, data specifying transaction 310 may include, but is not limited to, a cryptographic hash 310A of prior transaction 308, a quantity or number of units of the tracked asset portion that are subject to transfer in transaction 310, and a public key 310B of user 112. Further, in some aspects, the data specifying transaction 310 may include a digital signature 310C of the user 110, which may be applied to hash 310A and public key 310B using a private key 310D of user 110, as described above. Additionally, and by way of example, the presence of user 110's public key 308B within transaction data included within the hybrid blockchain ledger may enable various devices and systems (e.g., client devices 102, 104, and/or 106, peer systems 160, etc.) to verify the user 110's digital signature 310C, as applied to data specifying transaction 310.
  • Additionally, and as described above, client device 104 may also parse data specifying prior transaction 308 (e.g., as obtained from the current version of the hybrid blockchain ledger) and extract encrypted and/or hashed copies of rules engine 324 and event trigger list 322. In certain aspects, client device 104 may append the encrypted and/or hashed copies of rules engine 324 and event trigger list 322 to the data specifying transaction 310 (e.g., cryptographic hash 310A, public key 310B, and digital signature 310C), and transmit the data specifying transaction 310 to one or more of peer systems 160 for verification, processing (e.g., additional cryptographic hashing) and inclusion into a new block of the hybrid blockchain ledger. In an embodiment, ownership of the tracked asset portion may be transferred from user 110 to user 112 upon verification and publication of the data specifying transaction 310 within a corresponding block of the hybrid blockchain ledger by peer systems 160.
  • Further, and as described above, private crypto key 302B may enable client device 104 (e.g., associated with user 110) to decrypt event trigger list 322 upon extraction from the hybrid blockchain ledger, as described above. In some aspects, client device 104 may obtain private crypto key 302B from system 140 using secured out-of-band communications, and additionally or alternatively, as input provided by user 110 through a web page or other graphical user interface (GUI) presented by client device 104. In other aspects, client device 104 may identify and extract private crypto key 302B from a portion of the hybrid blockchain ledger obtained from peer systems 160 (e.g., as a secure in-band communication).
  • In the embodiments described above, system 140 may establish and maintain rules (e.g., through a rules engine and corresponding list of triggering events) that facilitate regulatory-based, policy-based, and customer-specified controls of transactions involving assets tracked within a hybrid blockchain ledger. For example, client devices 102, 104, and/or 106 may generate transaction data that includes rules engine and list of triggering events, and one or more of peer systems 160 may embed the generated transaction data into blocks of the hybrid blockchain ledger for reference in subsequent transactions. Further, in certain aspects, system 140 may be configured to detect an occurrence of an event (e.g., based on data received from client devices 102, 104, and/or 106, etc.), may determine whether the list of triggering events includes the detected event, and when triggering event list includes the detected event, perform one or more operations consistent with an established rule that references the detected event, as described below in reference to FIG. 4.
  • FIG. 4 is a flowchart of an exemplary process 400 for automatically performing event-based operations on assets tracked within a hybrid blockchain ledger in accordance with disclosed embodiments. In an embodiment, a centralized authority may be assigned to establish regulatory-based, policy-based, and customer-specified control over assets tracked within the hybrid blockchain ledger. In some aspects, tracked assets consistent with the disclosed embodiments may include, but are not limited to, units of a virtual currency or a crypto-currency, units of financial instruments held by one or more owners, and physical assets utilized by one or more individuals and/or entities. In some aspects, a computer system associated with the centralized authority (e.g., system 140 associated with business entity 150) may execute one more stored application programs to cause system 140 to recover, authorize, audit, and/or verify an ownership of at least a portion of the tracked assets and/or transactions involving the tracked assets based on established and maintained rules.
  • In one aspect, one or more computing components of system 140 may generate a rules engine and a list of triggering events, which may be stored within a portion of data repository 144 (e.g., in step 402). For example, the generated and stored rules engine may identify one 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 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.). Further, and as described above, the generated and stored list of triggering events may include information that specifies 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 actions involving assets tracked within the hybrid public-private ledger (e.g., the triggering events).
  • In certain instances, system 140 may establish, in step 402, one or more of the rules and/or triggering events to reflect regulations and/or policies promulgated by governmental entity, a financial regulator, and/or the centralized authority. For example, system 140 may establish a loss of a private key by user 110 as a “triggering event” that would cause system 140 to perform operations that generate a new pair of public and private blockchain keys for user 110 in response to a verification of particular authentication credentials. Further, and by way of example, system 140 may deem a documented theft of a portion of the tracked assets a “triggering event” that would cause system 140 to perform operations recover the stolen portion of the tracked assets and generate a new pair of public and private blockchain keys for user 110.
  • In other instances, system 140 may establish, in step 402, 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 a particular distribution of tracked assets (e.g., recurring bill payments, etc.) in response to an accident involving user 110 and/or user 110's death (e.g., triggering events). The disclosed embodiments are, however, not limited to these exemplary triggering events and corresponding rules, and in further embodiments, system 140 may establish any additional or alternate rules and/or triggering events appropriate to the tracked assets, to business entity 150, and further, to users 108, 110, and 112.
  • Further, one or more computing components of system 140 may generate additional cryptographic keys that facilitate the exemplary regulation of transactions (e.g., distributions, transfers, and/or actions) involving assets tracked within the hybrid public-private ledger (e.g., in step 404). By way of example, in step 404, system 140 may generate a master cryptographic key with which system 140 may encrypt the generated and stored rules engine, as described above. In some 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.
  • Further, in step 404, system 140 may also perform operations that generate and maintain additional private cryptographic keys (e.g., private “crypto” keys) associated with each owner of the assets tracked within the hybrid blockchain ledger. As described above, the generated private crypto keys may enable a device of each owner to decrypt and access the list of triggering events and additionally or alternatively, metadata identifying the centralized authority. System 140 may store copies of the generated private crypto keys in a portion of data repository 144. Furthermore, system 140 may also perform operations that provide corresponding ones of the private crypto keys to users 108, 110, and/or 112 through secure, non-accessible and/or out-of-band communications.
  • In step 406, system 140 may perform operations that encrypt the generated and stored rules engine (e.g., using the master encryption key) and further, that encrypt the generated and stored list of triggering events (e.g., using any of the exemplary techniques described above that facilitate decryption using the private crypto keys). For example, system 140 may perform operations in step 406 that hash the encrypted rules engine and list of triggering events into a genesis block of the hybrid blockchain ledger, the contents of which may be incorporated (e.g., by client devices 102, 104, and/or 106, peer systems 160, etc.) into each of the subsequent transaction blocks generated and appended to the hybrid blockchain ledger. In some aspects, by incorporating the hashed and encrypted rules engine and list of triggering events into the blocks of the hybrid blockchain ledger, the disclosed embodiments may ensure that the established rules are followed even in an event of actions by malicious parties that disrupt the tracked assets (e.g., instances of Bitcoin™ peeling, etc.).
  • Further, in some embodiments, one or more computing components of system 140 may detect an occurrence of an event involving a portion of the tracked assets, an owner of a portion of the tracked assets, and/or a transaction involving a portion of the detected assets (e.g., in step 408). For example, system 140 may receive data from client device 104 that indicates user 110 lost a corresponding private blockchain key associated with a portion of the tracked assets. In other instances, system 140 may detect an event in step 408 based on data received across network 120 from one or more systems associated with local, state, and/or federal governmental entities (e.g., data from a law enforcement system notifying business entity 150 of a theft of a portion of the tracked assets, data from a local government confirming a death of an owner of a portion of the tracked assets, etc.). Further, in additional instances, system 140 may detect an occurrence of an event based on one or more sensors and devices communicatively connected to network 120 and capable of transmitting data to system 140. The disclosed embodiments are, however, not limited to these exemplary events, and in further embodiments, system 140 may be configured to detect any additional or alternate event appropriate to the tracked assets and to the components of computing environment 100.
  • System 140 may also be configured to access the stored list of triggering events (e.g., within database 144), and may determine whether the list of triggering events includes the detected event (e.g., in step 410). If system 140 were to identify the detected event within the list of triggering events (e.g., step 410; YES), system 140 may establish the detected event as a triggering event, and may access the encrypted rules engine using the master encryption key (e.g., in step 412). System 140 may further identify, within the accessed rules engine, one or more of the established rules that are causally related to the detected triggering event (e.g., in step 414). Further, in some aspects, system 140 may be configured to perform one or more operations, either individually or in sequence, that are consistent with the identified rules (e.g., in step 416). For example, the accessed rules engine may include information identifying the one or more operations associated with the identified rules. In other instances, at least one of the performed operations may represent a default operation associated with the identified rules (e.g., a specific type of authentication required before performing the one or more operations on behalf of user 110).
  • In one embodiment, one or more computing components of system 140 may also determine whether to update portions of the generated rules engine and/or list of triggering events (e.g., in step 418). For example, system 140 may identify an update or modification to one or more regulations and/or policies promulgated by governmental entity, a financial regulator, and/or the centralized authority. In other instances, system 140 may obtain, from client device 104, information updating a rule and/or triggering event previously established by system 140 based on input received from user 110 (e.g., through a web page and/or GUI presented by client device 104).
  • If system 140 determines to update portions of the generated rules engine and/or list of triggering events (e.g., step 418; YES), system 140 may access appropriate portions of the rules engine and/or list or triggering events in step 420 (e.g., using the master encryption key and/or any of the exemplary techniques described above), and may modify the appropriate portions of the rules engine and/or list of triggering events to reflect the updated regulations, policies, user-specified rules, and/or user-specified events (e.g., in step 422). In some instances, system 140 may modify the accessed rules engine by adding a new rule, deleting an existing rule, modifying one or more parameters of an existing rule, and/or modifying one or more operations associated with an existing rule. In other instances, system 140 may modify the accessed list of event triggers to add a new triggering event, delete an existing triggering event, and/or add or modify parameters associated with an existing triggering event.
  • In some aspects, system 140 may encrypt and re-hash the modified rules engine and/or list of triggering events, and may submit the encrypted and hashed modified rules engine and/or list of triggering events to one or more of peer systems 160 for inclusion in a block of the hybrid blockchain ledger (e.g., in step 424). For example, one or more of peer systems 160 may incorporate the hashed and encrypted modified rules engine and/or list of triggering events into the hybrid blockchain ledger as a special transaction (e.g., a “0” value transaction), such that the hybrid blockchain ledger tracks each change within the modified rules engine and/or list of triggering event Exemplary process 400 is then complete in step 426.
  • Referring back to step 418, if system 140 were to determine that no modification to the rules engine and/or the list of triggering events is warranted (e.g., step 418; NO), exemplary process 400 may pass forward to step 426, and exemplary process 400 is complete. Further, and in reference to step 410, if system 140 were to determine that the list of triggering events fails to include the detected event (e.g., step 410; NO), exemplary process 400 may pass forward to step 418, and system 140 may determine whether to update portions of the rules engine and/or list of triggering events using any of the exemplary processes described above.
  • In the embodiments described above, and through the generation of the master cryptographic key and management of the generated rules engine and corresponding list of triggering events, system 140 may perform operations that recover, authorize, audit, and/or verify an ownership of at least a portion of the tracked assets and/or transactions involving the tracked assets. In certain aspects, the operations performed by system 140, which utilize hybrid blockchain ledgers consistent with the disclosed embodiments, would not be possible using the conventional blockchain ledgers described above.
  • For example, user 110 may be an avid user of a virtual or crypto-currency (e.g., Bitcoin™), user 110 may store a private key (e.g., private key 310D) on a laptop computer (e.g., client device 104) to generate and confirm Bitcoin™ transactions. In one instance, user 110 may unfortunately drop the laptop into a swimming pool while confirming a Bitcoin™ with private key 310D, and upon retrieved from the swimming pool, user 110 may establish that the laptop no longer functions and that data on the laptop is not recoverable.
  • Through a device in communication with network 120 (e.g., user 110's smartphone), user 110 may access a conventional blockchain ledger, such as those conventional architectures outlined above, and determine that the Bitcoin™ transfer was incomplete when user 110 dropped the laptop into the swimming pool. Further, user 110 may determine that the Bitcoin™ transaction represents an orphaned block within the conventional blockchain ledger, and the Bitcoins™ associated with the orphaned block are unrecoverable and permanently lost.
  • In other aspects, user 110 may access a hybrid blockchain ledger (e.g., as described above in reference to FIG. 3), and may determine that the Bitcoin™ transfer was incomplete when user 110 dropped the laptop into the swimming pool. In an embodiment, however, user 110 may provide input to the smartphone identifying the unrecoverable private key, which the smartphone may transmit to system 140 across network 120. In some aspects, system 140 may receive the transmitted message (e.g., in step 408), may determine that user 110's loss of private key 310D represents a triggering event (e.g., step 410; YES), and may perform operations that authenticate user 110's identity and that regenerate a pair of private and public blockchain keys for user 110, which system 140 may transmit to user 110 through any of the secure non-accessible processes outlined above (e.g., in steps 412, 414, and 416). Upon receipt of the newly generated private key, user 110 may access the hybrid blockchain ledger (e.g., through the smartphone) and confirm the Bitcoin transfer to recover the crypto-currency.
  • Further, and by way of example, user 110 may access a wallet application executed by client device 104, and further, may determine that the mobile wallet is missing a number Bitcoins™. User 110 may suspect that the loss of the Bitcoins™ represents a theft by a malicious entity, and through a complex search of a corresponding blockchain ledger (e.g., conventional blockchain ledgers described above, and/or hybrid blockchain ledgers consistent with the disclosed embodiments), user 110 may trace the theft of the Bitcoins™ to a single transaction within a corresponding block. User 110 may contact the police e-crime unit and report the theft, and the police may confirm the accuracy of user 110's allegations regarding the theft.
  • User 110 may, in some instances, be capable of processing the conventional blockchain ledgers described above to determine an address of the malicious entity responsible for the theft. The decentralized and anonymous nature of conventional blockchain ledgers may, however, prevent user 110 from identifying the malicious entity, and the stolen Bitcoins™ may remain permanently unrecoverable.
  • The disclosed embodiments may, however, address the deficiencies of conventional blockchain ledgers and provide user 110 with recourse to recover the stolen Bitcoins™. For example, the police e-crime unit may notify the centralized authority of the theft of user 110's Bitcoins™ and destination address associated with the malicious entity (e.g., through a message transmitted to system 140 and received, e.g., in step 408). System 140 may determine that the theft of the Bitcoins™ represents a triggering event included within the generated list (e.g., step 410; YES), and may perform operations that automatically create a request for a new transaction that returns the stolen Bitcoins™ to user 110 using any of the exemplary techniques described above (e.g., in steps 412, 414, and 416). System 140 may also perform operations that regenerate a pair of private and public blockchain keys for user 110, which system 140 may transmit to user 110 through any of the secure non-accessible processes outlined above (e.g., in steps 412, 414, and 416).
  • The hybrid blockchain ledger architectures described above may add a level of sophistication to conventional mechanisms for trustless communication by allowing transactions involving tracked assets to occur according to common transaction rules. Further, the hybrid blockchain ledger architectures consistent with the disclosed embodiments may allow owners of the tracked assets to project authority over the tracked assets by establishing customized rules for transaction authorization. Furthermore, and in contrast to the conventional techniques described above, the hybrid blockchain ledger architecture may enable a centralized authority (e.g., business entity 150 associated with system 140) to recover, authorize, audit, and/or verify an ownership of at least a portion of the tracked assets and/or transactions involving the tracked assets based on established and maintained rules.
  • In the embodiments described above, and through the generation of a master cryptographic key and management of a generated rules engine and corresponding list of triggering events, system 140, acting as a centralized authority, may perform operations that recover, authorize, audit, and/or verify an ownership of at least a portion of the tracked assets and/or transactions involving the tracked assets. In some aspects, and as outlined above, tracked assets consistent with the disclosed embodiments may include, but are not limited to, units of a virtual currency or a crypto-currency, units of financial instruments held by one or more owners, and physical assets utilized by one or more individuals and/or entities
  • In additional aspects, the exemplary hybrid blockchain algorithms described above may track a location, performance, usage, and/or status one or more additional client devices (e.g., “connected devices) disposed within computing environment 100 (not shown in FIG. 1), which may be configured to establish communications with client devices 102, 104, and 106, and further, with system 140, using any of the communications protocols outlined above. For example, client device 102, 104, and 106, system 140, and the connected devices may be uniquely identifiable and addressable within communications network 120, and may be capable of transmitting and/or receiving data across the established communications sessions. Further, in some aspects, system 140 may be configured to establish the communications sessions with one or more of the connected devices, and to exchange data with the connected devices autonomously and without input or intervention from a user of client device 104 (e.g., user 110).
  • In some aspects, the connected devices may be implemented as a processor-based and/or computer-based device that includes one or more processors and tangible, computer-readable memories, as described above in reference to client devices 102, 104, and 106. By way of example, connected devices consistent with the disclosed embodiments may include, but are not limited to mobile communications devices (e.g., mobile telephones, smart phones, tablet computers, etc.) and other devices capable of communicating with client device 104 (e.g., internet-ready televisions, internet-ready appliances and lighting fixtures, computing devices disposed within motor vehicles, etc.).
  • Further, in additional aspects, the connected devices may include sensor devices in communication with the one or more processors and the memories. The sensor devices may, in some aspects, be configured to monitor the usage, location, status, etc., of corresponding ones of the connected devices, and may be configured to provide sensor data to corresponding ones of the processors. In some aspects, the sensor data may include, but is not limited to, data identifying a current state, data specifying intended and/or unintended interaction with one or more of users 108, 110, and/or 112 (e.g., through client devices 102, 104, and/or 106), inadvertent interactions (e.g., drops, other accidental interactions, etc.), and data describing any additional or alternate characteristics of the connected devices capable of being monitored and quantified by the sensor devices.
  • In other aspects, computing environment 100 may include one or more additional computing systems in communication with the connected devices using any of the communications protocols outlined above. The additional computing system may, in an embodiments, include one or more sensor devices capable of monitoring a location, performance, usage, and/or status of the connected devices, which may establish a “sensor network” capable of monitoring the connected devices. These additional computing systems may provide the additional sensor data to the connected devices using any of the communications protocols outlined above, either at regular intervals or in response to requests from the connected devices. In some instances, the additional computing systems may be implemented as processor-based and/or computer-based systems consistent with the exemplary systems described above.
  • In further aspects, the connected devices may be configured to transmit portions of the sensor data (e.g., as detected by on-board sensor devices and/or received from the sensor network) to client devices 102, 104, and/or 106 and additionally or alternatively, to system 140, using any of the communications protocols outlined above. By way of example, the sensor data may characterize an interaction between the connected devices and users 108, 110, and 112 (e.g., the monitored data may represent usage data indicative of a consumption of one or more services provided by the connected devices), and the connected devices may transmit the usage data for users 108, 110, and/or 112 to corresponding ones of client devices 102, 104, and/or 106, which may store the received usage data in a corresponding data repository. In further aspects, the connected devices may also transmit the usage data to system 140, along with information linking specific elements of the usage data to corresponding users and/or client devices (e.g., user 110's usage data may be linked to an identifier of user 110 and/or of client device 104). In certain aspects, client devices 102, 104, and/or 106 may also incorporate corresponding portions of the monitored data, e.g., as received from the connected devices, into hybrid blockchain ledgers consistent with the disclosed embodiments in order to record, track, and publicly monitor the location, performance, usage, and/or status of the connected devices.
  • III. Systems and Methods for Detecting and Resolving Data Inconsistencies among Networked Devices Using Hybrid Private-Public Ledgers
  • In various embodiments described above, computer systems of centralized authority (e.g., a financial institution, etc.) augment conventional, decentralized blockchain ledger architectures by selectively encrypt ledger data to protect both a privacy of owners of tracked assets and a confidentiality of existing instruction sets maintained within the blockchain ledger. Further, by incorporating an encrypted rules engine and corresponding list of triggering events (e.g., an event trigger list) into each block of the conventional blockchain ledger architectures (and thus generating a hybrid, public-private blockchain ledger architecture), computer implemented systems and methods consistent with the disclosed embodiments may perform operations that, for example, provide owners or holders of tracked assets with recovery options in an event of fraud or malicious activity, while maintaining the public availability and verification characteristic of conventional blockchain ledgers.
  • Further, and consistent with the disclosed embodiments, client devices 102, 104, and/or 106 may execute stored software applications (e.g., mobile applications provided by the centralized authority), which may cause client devices 102, 104, and/or 106 to transmit data identifying transactions involving held assets to one or more computer systems across network 120 (e.g., one or more of peer systems 160). As described above, peer systems 160 may act as “miners” for hybrid blockchain ledgers consistent with the disclosed embodiments, and may competitively process the received transaction data (either alone or in conjunction with other data) to generate additional ledger blocks, which may be appended to the hybrid blockchain ledgers and distributed across peer systems 160 (e.g., through a peer-to-peer network) and to other connected devices of environment 100 (e.g., across network 120).
  • a. Exemplary Processes for Establishing and Enforcing Contractual Terms and Obligations Using Hybrid, Blockchain Ledger Data Structures
  • In some embodiments, one or more of the exemplary hybrid blockchain ledger data structures described above may provide a centralized and transparent mechanism that records obligations enforceable on various parties to a contractual agreement, and further, that tracks data indicative of one or more transactions initiated by the contracting parties in partial or total satisfaction of the recorded obligations. Additionally, given the transparent and centralized nature of these exemplary hybrid blockchain ledger data structures, the disclosed embodiments may enable a system of a clearinghouse entity to access the portions of the hybrid blockchain ledger data, reconcile assets, funds, and other tracked data against the recorded obligations and further, identify and media conflicts between the various parties.
  • For example, a first party (e.g., user 108) may engage with a second party (e.g., user 110) to renovate a portion of user 108's home in exchange for an agreed-upon sum (e.g., $15,000). In certain aspects, users 108 and 110 may establish terms that require payment of the agreed-upon sum not on once, but in a first installment prior to initiation of the renovation (e.g., an initial payment of $5,000 for supplies), and in two subsequent installments contingent upon user 108's approval of user 110's progress in the renovations. For example, user 108 may agree to pay $5,000 on or before November 15th, may agree to pay a first $5,000 installment on December 1st in response to user 110's satisfactory completion of 50% of the renovation, and further, may agree to pay a second $5,000 installment on December 15th in response to user 110's satisfactory completion of the remainder of the renovation.
  • In some instances, devices associated with users 108 and 110 (e.g., client devices 102 and 104) may execute software applications (e.g., one or more “smart contract” applications) that establish, facilitate, verify, and/or enforce the negotiation or performance of a contractual agreement (e.g., that establish and implement a “smart contract” between the parties). In certain aspects, user 108 may provide, to client device 102 as input to a graphical user interface (GUI) generated by the executed start contract applications, data that, among other things, identifies the contracting parties (e.g., users 108 and 110), the contracted activity (e.g., the renovation of user 108's home), user 108's obligations under the contractual agreement (e.g., the initial $5,000 payment on November 15th and the $5,000 installment payments due on December 1st and December 15th in exchange for satisfactory completion of portions of the renovation), and user 110's scheduled performance under the contractual agreement (e.g., to initiate work on by November 15th, to complete 50% of the renovation by December 1st, and to complete renovations by December 15th). Additionally or alternatively, user 108 may provide input that identifies one or more financial services accounts held by user 108 at a first financial institution (e.g., a checking, savings, and/or investment account, a home equity line-of-credit, etc.), upon which user 108 may draw to service the financial terms of the financial agreement,
  • Client device 108 may, for example, package the inputted data into one or more data structures for storage in a locally accessible data repository or within secure, remote data repository accessible across network 120 (e.g., a cloud-based data repository). In further instances, client device 108 may transmit portions of the inputted data, including, but not limited to, data that identifies the contracting parties, the contracted activity, user 108's obligations under the contractual agreement, and user 110's scheduled performance, to a system maintained by the first financial institution (e.g., system 140). As described below, system 140, acting as a rules authority, may execute software applications that decrypt, access, and update portions of an encrypted list of triggering events (e.g., event triggers list 322) and an encrypted rules engine (e.g., rules engine 324) to include portions of the transmitted data, and may establish and maintain a new ledger block of a hybrid, blockchain ledger data structure to record and track the terms of the contractual agreement, as input into client device 102 by user 108.
  • For example, as described above, system 140 may access copies of the encrypted list of triggering events and the encrypted rules engine (e.g., as stored locally in data repository 144 and/or as obtained from a latest, longest version of the hybrid, blockchain ledger data structure), and may decrypt the encrypted list of triggering events and the encrypted rules engine using any of the exemplary techniques described above. In some aspects, system 140 may execute software applications that modify and/or augment the decrypted list of triggering events to include data identifying user 108's scheduled payments (e.g., November 15th, December 1st, and December 15th) and the conditions facilitating on one or more of these scheduled payments (e.g., 50% completion on December 1st and 10% completion on December 15th).
  • Additionally, and in certain aspects, system 140 may modify and/or augment the decrypted rules list to include one or more operations associated with the scheduled payments and/or facilitating conditions. For example, system 140 may generate and include, within the decrypted rules data, additional rules data identifying operations that initiate an electronic funds transfer of $5,000 from an account of user 108 to an account of user 110 on November 15th. Further, and by way of example, system 140 may include, within the decrypted rules data, operations that confirm a completion of 50% the renovation on or before December 1st (e.g., based on an electronic confirmation digitally signed by user 108's private key), and that initiate an electronic funds transfer of the $5,000 installment on December 1st in response to the confirmation. Similarly, in some instances, system 140 may include, within the decrypted rules data, operations that confirm a completion of the renovation on or before December 15th (e.g., based on an electronic confirmation digitally signed by user 108's private key), and that initiate an electronic funds transfer of the final $5,000 installment on December 15th in response to the confirmation.
  • System 140 may encrypt the modified list of triggering events and the modified rules engine using any of the exemplary techniques described above, and may store the encrypted list of triggering events and the encrypted rules engine in a locally accessible data repository (e.g., data repository 144) and/or in a remote data repository accessible across network 120 (e.g., a cloud-based data repository). Further, and in certain aspects, system 140 may execute software applications to establish and maintain a new ledger block of the exemplary hybrid blockchain ledger that records data indicative of the terms of and parties to the contractual agreement (e.g., data identifying the contracting parties, the contracted activity, user 108's obligations under the contractual agreement, user 110's scheduled performance, etc.), the encrypted list of triggering events, and the encrypted rules engine using any of the exemplary techniques described above,
  • For example, and as described above, system 140 may append the new ledger block to the latest, longest version of the hybrid blockchain ledger, which may be distributed to one or more additional devices and systems operating within environment 100. Additionally, in some aspects, system 140 may append the new ledger block to one or more sidechains or other blockchain-ledger-based data structures that track terms and conditions of the contractual agreement.
  • In additional aspects, similar to those described above, user 110 may provide, to client device 104 as input to a GUI generated by the executed start contract applications, data that among other things, identifies the contracting parties (e.g., users 108 and 110), the contracted activity (e.g., the renovation of user 108's home), user 110's obligations under the contractual agreement (e.g., initiate renovations on or before November 15th, complete 50% of the renovations to user 108's satisfaction on or before December 1st, and complete the renovations to user 108's satisfaction on or before December 15th), and user 108's required performance under the terms of the contractual agreement (e.g., the initial $5,000 payment on November 15th and the $5,000 installment payments due on December 1st and December 15th in exchange for satisfactory completion of portions of the renovation). Additionally or alternatively, user 110 may provide input that identifies one or more financial services accounts held by user 110 at a second financial institution (e.g., a checking, savings, and/or investment account, a business account, etc.) into which the proceeds of the contractual agreement may be deposited,
  • Client device 104 may, in some instances, package the inputted data into one or more data structures for storage in a locally accessible data repository or within secure, remote data repository accessible across network 120 (e.g., a cloud-based data repository). In further instances, client device 104 may transmit portions of the inputted data, including, but not limited to, data that identifies the contracting parties, the contracted activity, user 110's obligations under the contractual agreement, and user 108's scheduled performance, to a system maintained by the second financial institution (e.g., system 141). As described below, system 141, acting as a rules authority, may execute software applications that decrypt, access, and update portions of an encrypted list of triggering events(e.g., event triggers list 322) and an encrypted rules engine (e.g., rules engine 324) to include portions of the transmitted data, and may establish and maintain a new ledger block of a hybrid, blockchain ledger data structure to record and track the terms of the contractual agreement, as input into client device 104 by user 110.
  • For example, as described above, system 141 may access a copies of the encrypted list of triggering events and the encrypted rules engine (e.g., as stored locally in data repository 145 and/or as obtained from a latest, longest version of the hybrid, blockchain ledger data structure), and may decrypt the encrypted list of triggering events and the encrypted rules engine using any of the exemplary techniques described above. In some aspects, system 141 may execute software applications that modify and/or augment the decrypted list of triggering events to include data identifying performance milestones that would result in receipt of payment (e.g., initiation of renovations on or by November 15th, satisfactory completion of 50% of the renovations on December 1st, and satisfactory completion of all renovations on December 15th),
  • Additionally, and in certain aspects, system 140 may modify and/or augment the decrypted rules list to include one or more operations associated with the scheduled payments and/or facilitating conditions. For example, system 140 may generate and include within the decrypted rules data identifying operations that confirm receipt of an electronic funds transfer of $5,000 from an account of user 103 on November 15th (e.g., prior to initiating renovations). Further, and by way of example, system 141 may include, within the decrypted rules data, rules data confirming a satisfactory completion of 50% the renovation on or before December 1st (e.g., based on an electronic confirmation digitally signed by user 108's private key), and confirming receipt of an electronic funds transfer of the $5,000 installment on December 1st. Similarly, in some instances, system 141 may include, within the decrypted rules data, rules data confirming a satisfactory completion of the renovation on or before December 15th (e.g., based on an electronic confirmation digitally signed by user 105's private key), and confirming receipt of an electronic funds transfer of the final $5,000 installment on December 15th.
  • Using any of the exemplary techniques described above, system 141 may encrypt the modified list of triggering events and the modified rules engine, and may store the encrypted list of triggering events and the encrypted rules engine in a locally accessible data repository (e.g., data repository 145) and/or in a remote data repository accessible across network 120 (e.g., a cloud-based data repository). Further, and in certain aspects, system 141 may execute software applications to establish and maintain a new ledger block of the exemplary hybrid blockchain ledger that records data indicative of the terms of and parties to the contractual agreement (e.g., data identifying the contracting parties, the contracted activity, user 110's obligations under the contractual agreement, user 108's scheduled performance, etc.), the encrypted list of triggering events, and the encrypted rules engine using any of the exemplary techniques described above.
  • For example, and as described above, system 141 may append the new ledger block to the latest, longest version of the hybrid blockchain ledger, which may be distributed to one or more additional devices and systems operating within environment 100. Additionally or alternatively, system 140 may append the new ledger block to one or more sidechains or other blockchain-ledger-based data structures that track terms and conditions of the contractual agreement.
  • Further, and by way of example,the new ledger blocks may be structured to include, among other things: a block header (which identifies an address of a prior block); an identifier of the corresponding one of system 140, system 141, and/or peer systems 160 that created the additional ledger block; a rules header that includes a rules associate key (e.g., that associates a rule to the Internet-connected device); an encrypted list of event triggers and an encrypted rules engine; a header for received transaction data; and the received transaction data written into the hybrid, blockchain data structure, as described above.
  • In certain aspects, the disclosed embodiments may enable system 140 (e.g., maintained by the first financial institution of user 108) and system 141 (e.g., maintained by the second financial institution of user 110) to establish and maintain distinct ledger blocks within the hybrid blockchain ledger data structure (and/or one or more sidechain data structures) that record terms of the contractual agreement provided by user 108 and by user 110. By memorializing these contractual terms in corresponding ledger blocks, which include encrypted lists of event triggers accessible by corresponding ones of the contracting parties (e.g., crypto keys 302A and 302B, as described above), the disclosed embodiments may enable each of the contracting parties to access the hybrid blockchain ledger data structures and confirm their understanding and interpretation of the mutually agreed-upon terms.
  • Further, one or more of the exemplary hybrid blockchain ledger data structures described above may enable client devices 102 and 104, and additionally or alternatively, systems 140 and 141, to monitor and publicly record data indicative of activities by users 108 and 110 that partially satisfy one or more of the obligations set forth in the contractual agreement between users 108 and 110. In other aspects, as described below, computer systems maintained by a neutral third party (e.g., system 146 of clearinghouse entity 150) may access one or more data blocks of the exemplary hybrid blockchain ledger data structures described above, and may reconcile portions of the recorded contractual terms and conditions (e.g., as provided by users 108 and 110) and further, mediate disputes between users 108 and 110 in an open and transparent manner.
  • For example, as described above, client device 102 may execute one or more software applications (e.g., one or more of the smart contract applications described above) that access one or more portions of stored contractual data (e.g., as input by user 108, above) and determine that the contractual agreement requires an initial transfer of $5,000 to an account held by user 110 on November 1st to initiate the agreed-upon renovations. The executed software applications may, for example, cause client device 102 to perform operations that transfer $5,000 in virtual currency from a mobile wallet maintained by client device 102 to a corresponding mobile wallet of user 110 (e.g., as maintained by a mobile wallet application executed by client device 104) using any of the exemplary techniques described above.
  • In some aspects, client device 102 may initiate the transfer (e.g., from user 108's account to user 110's account) by establishing a peer-to-peer communications (P2P) session with client device 104 (e.g., using near-field communications (NFC) protocols, Bluetooth™ communications protocols, etc.), and one or more applications programs executed by client devices 102 and 104 (e.g., mobile wallet applications, etc.) may exchange data effecting the transfer of the $5,000 installment without recourse to the first or second financial institutions. In other aspects, and consistent with the disclosed embodiments, client device 102 may perform operations that initiate an electronic transfer of funds from an account held by user 108 at the first financial institution to an account held by user 110 at the second financial institution (e.g., through appropriate API calls) and additionally or alternatively, receive input from user 108 indicative of a payment of the $5,000 installment in cash or by check. The disclosed embodiments are, however, not limited to these exemplary transfer protocols, and in additional aspects, user 108 and/or client device 102 may initiate a transfer of the $5,000 installment using any additional or alternate techniques apparent and appropriate to users 108 and 110.
  • Additionally, client devices 102 and/or 104 may generate data indicative of the initiated transfer of the $5,000 installment payment, and additionally or alternatively, the completion of the initiated transfer (e.g., which signals the available of the funds for use by user 110). In some aspects, client devices 102 and/or 104 may transfer portions of the generated data for inclusion in one or more additional ledger blocks of the hybrid blockchain ledger data structure, which may memorialize user 108's partial satisfaction of the obligations set forth on the contractual agreement.
  • For example, client device 102 may transmit portions of the generated data that identify the initiated transfer (e.g., an amount of the transfer, a timestamp, a confirmation number or other identifier of the initiated transfer, etc.) to system 140. In certain aspects, system 140 may access and decrypt an encrypted list of event triggers (e.g., event trigger list 322) and an encrypted rules engine using any of the exemplary techniques described above. Additionally, in further aspects, system 140 may parse the decrypted list of triggering events to determine that the $5,000 transfer initiated on November 1st represents a first installment payment mandated by the contractual agreement (e.g., to enable user 110 to being renovations), and based on the decrypted rules engine, may identify one or more rules that are associated with the first installment payment and specify a generation of an additional ledger block that records the first installment payment in partial satisfaction of user 108's contractual obligations. In accordance with the one or more identified rules, system 140 may execute software applications that establish a new ledger block that includes portion of the data identifying the initiated transfer, as well as the encrypted list of triggering events and encrypted rules engine maintained by system 140, using any of the exemplary techniques described above.
  • Additionally or alternatively, client device 102 may transmit portions of the generated data that identify the initiated and/or completed transfer (e.g., the transferred amount of the transfer, a timestamp of the initiated and/or completed transfer, the confirmation number, etc.) to system 141. As described above, and based on an accessed and decrypted list of triggering events and corresponding rules engine, system 140 may execute software applications that establish a new ledger block that includes portion of the data identifying the initiated transfer and/or completed transfer, as well as the encrypted list of triggering events and encrypted rules engine maintained by system 141, using any of the exemplary techniques described above.
  • In response to the initiated and completed transfer of the initial $5,000 installment, user 110 may purchase necessary supplies and begin renovations on user 108's home in accordance with the contractual agreement. With the November 15th deadline looming for completing 50% of the renovations to user 108's home, which would trigger a transfer of the second $5,000 installment from user 108 to user 110, users 108 and 110 may agree to meet and review the progress of the renovations. For example, after reviewing the progress and status of the renovations, user 108 and 110 may tentatively agree that user 110 completed at least 50% of the agreed-upon renovations, which would trigger the transfer of the agreed-upon $5,000 transfer.
  • In response to the tentative agreement regarding the pace of renovations, user 110 may provide input data to client device 104 specifying the portion of the agreed-upon renovations completed prior to the December 1st deadline and further, specifying the completed portions represents at least 50% of the agreed-upon work. For example, user 104 may input the data into a GUI or other interface presented to user 110 by client device 104, and client device 104 may package the inputted data into a corresponding data structure (e.g., an electronic construction report). Client device 104 may, in some instances, execute one or more software applications (e.g., one or more of the smart contract applications described above) that parse the electronic construction report and determine that user 110 satisfied the obligations for transfer of the second $5,000 installment of funds. The executed smart contract applications may cause client device 104 to generate data requesting a transfer of the second $5,000 installment from user 108 to user 110, which may be transmitted with the electronic construction report to system 141 using any of the communications protocols outlined above. Additionally or alternatively, client device 104 may also transmit the electronic construction report to client device 102 for review and approval by user 108.
  • In some aspects, and in response to the received request, system 140 may access and decrypt an encrypted list of event triggers (e.g., event trigger list 322) and an encrypted rules engine (e.g., rules engine 324) using any of the exemplary techniques described above. For example, system 140 may access copies of the encrypted list of event triggers and an encrypted rules engine from a locally accessible data repository (e.g., data repository 144) and/or may extract the encrypted list of event triggers and an encrypted rules engine from a latest, longest version of the hybrid, blockchain ledger data structure described above. System 140 may parse the decrypted list of triggering events, in conjunction with the electronic construction report, to establish that the portion of the renovations performed by user 110 (e.g., as set forth in the electronic construction report) represent an event triggering disbursement of the second $5,000 installment. Based on one or more of the decrypted rules, system 140 may perform operations to initiate the disbursement and record the initiated disbursement in a new ledger block of the hybrid, blockchain ledger data structure (and/or one or more sidechain data structures) using any of the exemplary techniques described above.
  • In other aspects, client device 102 may receive the electronic construction report from client device 102, and may execute one or more application programs (e.g., the smart contract applications described above) to process and render portions of the electronic construction report for presentation to user 108 through a corresponding GUI. In some aspects, client device 102 may also receive data (e.g., from system 140 maintained by the first financial institution of user 108) indicative of the transfer of the second $5,000 installment from user 108 to user 110 (e.g., from accounts of user 108 to accounts of user 110, a transfer of units of virtual currency, etc.). Upon review of the presented portions of the electronic construction report, user 108 may determine that the portion of the renovations completed by user 110 falls short of the 50% required triggering the transfer of the second $5,000 installment,
  • For example, upon negotiation of the terms of the contractual agreement, users 108 and 110 may agree that the renovation process includes four specific construction projects (e.g., a removal of carpet from a portion of the home, an installation of a new hardwood floor, a removal of a partial wall, and an application of new paint within a portion of the home). In some instances, and upon review of the electronic construction report, user 108 may reconsider the prior agreement with user 110 and may determine that user 110 failed to complete at least two of the four specific construction requirements before December 1st, and thus failed to complete the 50% of the renovations necessary to trigger the transfer of the second $5,000 installment.
  • In some aspects, user 108 may provide input to client device 102 (e.g., through a corresponding GUI generated by the one or more executed smart contract applications) that disputes user 110's performance of 50% of the renovation prior to the December 1st deadline and further, disputed the propriety of the executed transfer of the second $5,000 installment. In response to user 108's input, client device 102 may generate data that, among other things, identifies the party initiating the dispute (e.g., an identifier of user 108), the other contracting party (e.g., user 110), a corresponding device that initiated the dispute (e.g., an IP address or MAC address associated with client device 102), the one or more disputed terms of the contractual agreement (e.g., the performance by user 110 of 50% of the renovation prior to the December 1st deadline), one or more disputed actions (e.g., the transfer of the second $5,000 installment from user 108 to user 110), and/or evidence supporting the disputed one or more terms and actions (e.g., the electronic construction report). Client device 102 may, in some instances, transmit the generated data to system 140 across network 120 using any of the communications protocols outlined above.
  • System 140 may, upon receipt of the transmitted data may store portions of the transmitted data in a corresponding portion of a local data repository (e.g., data repository 144). In additional aspects, system 140 may decrypt copies of an encrypted list of triggering events and an encrypted rules engine using any of the exemplary techniques described above. For example, and based on the decrypted event triggers, system 140 may determine that the receipt of the data indicative of the disputed term of the contractual agreement (e.g., the performance by user 110 of 50% of the renovation prior to the December 1st deadline) and the transfer of the second $5,000 from user 108 to user 110 represents a disagreement between the interpretation of the contractual terms and user 110's performance by the first financial institution (which deems user 110's performance insufficient to initiate transfer of the second $5,000 installment) and the second financial institution (which deemed user 110's performance sufficient to transfer the second $5,000 installment from user 108 to user 110).
  • In some aspects, system 140 may parse the decrypted rules engine to identify one or more dispute resolution procedures, which may include, but are not limited to, requesting that a neutral third party, such as clearinghouse entity 152, resolve the dispute between the first and second financial institutions regarding the transfer of the second $5,000 installment. In certain aspects, system 140 may execute software applications that generate a request for dispute resolution that includes, but is not limited to, data that identifies the party initiating the dispute (e.g., an identifier of user 108), the other contracting party (e.g., user 110), a corresponding device that initiated the dispute (e.g., an IP address or MAC address associated with system 140), the first and second financial institutions, the one or more disputed terms of the contractual agreement (e.g., the performance by user 110 of 50% of the renovation prior to the December 1st deadline), one or more disputed actions (e.g., the transfer of the second $5,000 installment from user 108 to user 110), and/or evidence supporting the disputed one or more terms and actions (e.g., the electronic construction report).
  • System 140 may, in certain aspects, execute software applications that generate one or more additional ledger blocks of the hybrid blockchain ledger data structure to memorialize the dispute between the dispute between the first and second financial institutions using any of the exemplary techniques described above. System 140 may, in further aspects, transmit the generated dispute-resolution request to a computer system maintained by clearinghouse entity 152 (e.g., system 146), which may perform operations that automatically and transparently resolve the dispute between the first and second financial institutions, as described below.
  • b. Exemplary Processes for Resolving Disputed Contractual Terms Using Hybrid, Blockchain Ledger Data Structures
  • In some aspects, and as described above, computing environment 100 may include a number of computer systems maintained by various financial institutions systems 140 and 141), which may act as rules authorities, and which may execute software applications to establish and maintain ledger blocks of the exemplary hybrid blockchain ledger data structures described above. For example, various parties may mutually agree on terms of a contractual agreement, which accords rights to the various parties and imposes corresponding obligations for performance. As described above, client devices operated by these various parties (e.g., client devices 102, 104, and 106) may execute mutually compatible “smart contract” applications that establish and enforce performance of the contractual agreement and further, transmit data indicative of the terms, rights, obligations, and/or performance by the parties to corresponding ones of the financial institution systems, which may process and incorporate portions of the transmitted data into ledger blocks of the exemplary hybrid blockchain ledger data structures using any of the exemplary techniques described above.
  • By way of example, the parties may agree on contractual terms that require a first party (e.g., user 108) to pay a predetermined sum to a second party (e.g., user 108) in exchange for specified actions performed by user 110 on behalf of user 108. In some instances, and as described above, the payment may represent a transfer of units of a virtual currency held by user 108 (e.g., within a mobile wallet maintained by client device 102) to user 110 (e.g., to a mobile wallet maintained by client device 104). Additionally or alternatively, the payment may represent a transfer of funds from an account of user 108 at a first financial institution to an account of user 110 at a second financial institution. Further, in additional instances, such as those described above, user 110 may provide (e.g., through client device 104) evidence of the performance of the specified actions to user 108 (e.g., through client device 102), and client devices 102 and/or 104 may transmit identifying the evidenced performance and the effected transfer to systems maintained by the first and second financial institutions (e.g., systems 140 and 141), which may process and incorporate portions of the transmitted data into ledger blocks of the exemplary hybrid blockchain ledger data structures using any of the exemplary techniques described above.
  • In some aspects, however, the first and second financial institutions may disagree on a sufficiency of user 110's performance, and first financial institution may dispute the propriety of the transfer of funds from user 108 to user 110. For example, and as described above, client device 104 may present an electronic construction report to system 141 as evidence that user 110 completed 50% of an agreed-upon renovation of user 108's home, and based on a decrypted list of triggering events and rules engine, perform operations that transfer funds (e.g., a second $5,000 installment) from user 108 to user 110 in exchange for user 110's performance, as described above. In certain aspects, system 140 may dispute the sufficiency of user 110's performance, as outlined in the electronic construction report (e.g., which client device 104 provided to client device 102, and which client device 102 provided to system 140), and may initiate processes to automatically and transparently resolve the dispute and perform corrective actions, as described below in reference to FIG. 5.
  • FIG. 5 is a flowchart of an exemplary process 500 for automatically resolving contracting disputes using data tracked within a hybrid blockchain ledger, in accordance with disclosed embodiments. The disclosed embodiments may, for example, enable a system maintained by a neutral third party (e.g., system 146 of clearinghouse entity 152) to receive notification of a dispute between two or more parties (e.g., between financial institutions, etc.) regarding an implementation of one or more contractual terms (e.g., as set forth in rules engines maintained by systems of the financial institution), and further, to arbitrate and resolve the dispute based on one or more rules and operations established and maintained by system 146 (e.g., within data repository 149).
  • In some aspects, system 146 may receive notification of a dispute between multiple parties to a contractual agreement (e.g., in step 502). By way of example, and as described above, system 141 (e.g., maintained by the second financial institution of user 110) may determine, based on decrypted copies of an encrypted list of triggering events and an encrypted rules engine, that an electronic construction report (e.g., generated by client device 104) indicates that user 110 completed at least 50% of the agreed-upon renovations to user 108's home prior to Dec. 1, 2015, which triggers a transfer of a second $5,000 installment from user 108 to user 110 in accordance with terms of a corresponding contractual agreement. In contrast, system 140 (e.g., maintained by the first financial institution of user 108) may dispute the sufficiency of user 110's performance, and may establish that the transfer of the second $5,000 installment is improper and inconsistent with the contractual agreement. As described above, and in response to the detected dispute, system 140 may generate corresponding notification data that identifies the dispute, the parties, and disputed evidence, and transmit the notification data to system 146 as a notification of a dispute (e.g., which system 146 may receive in step 502).
  • The notification data may, in certain instances, include, but is not limited to, data that identifies the party initiating the dispute (e.g., an identifier of user 108), the other contracting party (e.g., user 110), a corresponding device that initiated the dispute (e.g., an IP address or MAC address associated with system 140 and/or client device 102), the first and second financial institutions, the one or more disputed terms of the contractual agreement (e.g., the performance by user 110 of 50% of the renovation prior to the December 1st deadline), one or more disputed actions (e.g., the transfer of the second $5,000 installment from user 108 to user 110), and/or evidence supporting the disputed performance (e.g., the electronic construction report generated by client device 104). The disclosed embodiments are not limited to this exemplary notification data, and in further embodiments, system 146 may receive any additional or alternate data capable of characterizing the dispute and appropriate to system 146.
  • System 146 may, in some aspects, access a latest, longest version of a hybrid blockchain ledger data structure corresponding to the contractual agreement (and additionally or alternatively, a sidechain data structure), and may obtain, from the accessed hybrid blockchain ledger data structure, data identifying terms, provided rights, and imposed obligations of the contractual agreement and any recorded performance by the parties (e.g., in step 504). By way of example, and as described above, the accessed hybrid blockchain ledger data structure may include a first data block (e.g., established by system 140) that records the contractual terms provided to system 140 by client device 102 (e.g., including terms input by user 108 into GUI generated by an executed smart contract application), and a second data block (e.g., established by system 141) that records the contractual terms provided to system 141 by client device 104 (e.g., including terms input by user 110 into GUI generated by an executed smart contract application). Additionally, in some instances, the accessed hybrid blockchain ledger data structure may include one or more third data blocks that specify or identify portions of user 110's disputed performance (e.g., data blocks that incorporate portions of the electronic construction report included within the received notification data. In some aspects, system 146 may extract data corresponding to the first, second, and third data blocks, which may be stored in corresponding portions of a locally accessible data repository (e.g., data repository 149).
  • Further, in step 506, system 146 may also access and decrypt an encrypted list of triggering events (e.g., event trigger list 322) and an encrypted rules engine (e.g., rules engine 324). In some aspects, and as described above, system 146 may access and decrypt the encrypted list of triggering events and encrypted rules engine hashed into the latest, longest version of the hybrid blockchain ledger data structure corresponding to the contractual agreement (e.g., as obtained above in step 504). In other aspects, consistent with the disclosed embodiments, system 146 may access a locally stored copy of the encrypted list of triggering events and/or the encrypted rules engine (e.g., as stored within data repository 149).
  • In some aspects, the decrypted list of triggering events may specify that the received notification data represents an event triggering initiation and performance of a dispute-resolution process by system 146, which may be defined by one or more associated rules set forth in the decrypted rules engine. For instance, the decrypted rules engine may include one or more rules that define operations performed by system 146 to resolve a dispute involving terms of and/or performance related to the contractual agreement between users 108 and 112. By way of example, the specified dispute-resolution operations may include a first operation that determines whether users 108 and 110 specified mutually consistent terms and conditions (e.g., within the extracted first and second data blocks described above), and one or more second operations (e.g., specified by the first and second financial institutions, a governmental and/or regulatory entity, etc.) to determine a compliance of the evidenced performance (e.g., the electronic construction report) with the mutually consistent terms and conditions.
  • Further, in additional instances, the decrypted rules engine may also identify operations that enable system 146 to resolve the contractual dispute between users 108 and 110, and further, between the first and second financial institutions, based on a consensus of those financial institutions capable of acting as rules authorities for the hybrid blockchain ledger data structure. For example, one or more of the rules may cause system 146 to provide portions of the received notification data to systems maintained by the financial institution (e.g., that operate as rules authorities within environment 100). In some aspects, the transmitted notification data portions may cause software applications executed by the financial institution systems to prompt a competent representative of each financial institutions (e.g., an attorney in the office of the general counsel) to review the evidence and the contractual terms, and identify the prevailing party (e.g., user 108 or user 110) within an established time period. The financial institution systems may transmit data indicative of the prevailing party to system 146, which may aggregate the received data and establish, as the prevailing party, that contracting party identified by a plurality and/or a majority of the financial institutions.
  • In other instances, and consistent with the disclosed embodiments, the decrypted rules engine may include multiple groups of rules specifying operations that resolve corresponding types of disputes. For example, the decrypted rules engine may include groups of rules specifying operations for resolving disputes involving constructions contracts, employment contracts, licensing agreement, and any additional or alternate type of contract appropriate to the first and second financial institutions and users 108 and 110. The disclosed embodiments are not limited to these exemplary rules, and in additional embodiments, the decrypted rules engine may specify any additional or alternate dispute-resolution rule appropriate to the contractual agreement, the contracting parties, and the various financial institutions.
  • In further aspects, system 146 may select one or more of the decrypted rules associated with the resolution of the contractual dispute involving users 108 and 110 (e.g., in step 508), and may perform operations consistent with the one or more selected rules to resolve the contractual dispute (e.g., in step 510). For example, and in accordance with the selected rules, system 146 may execute software applications that access locally stored data (e.g., extracted from the first and second data blocks described above) identifying each set of terms and conditions specified by users 108 and 110. Based on the accessed data, system 146 may determine that users 108 and 110 specified mutually consistent terms and conditions specifying a disbursement of the second $5,000 installment upon completion of at least 50% of the renovation of user 108's home prior to December 1st. System 146 may parse the electronic construction report to determine, for example, that the renovation includes four specific construction projects (e.g., a removal of carpet from a portion of the home, an installation of a new hardwood floor, a removal of a partial wall, and an application of new paint within a portion of the home), which may be subdivided into twenty discrete tasks. Based on the electronic construction report, system 146 may also determine that, while user 110 did not complete any of the four tasks by December 1st, user 110 complete fourteen of the twenty discrete tasks. In certain aspects, system 146 may determine that user 110's performance complied with the terms of the contractual agreement in step 510.
  • In other instances, system 146 establish user 110's compliance with the contractual agreement in accordance with a consensus decision of all financial institutions capable of acting as rules authorities for the hybrid blockchain ledger data structure. For example, system 146 may identify nine such financial institutions, and may obtain IP addresses and other information identifying computer systems maintained by these nine financial institution (e.g., from a corresponding portion of data repository 149). System 146 may, in some instances, transmit portions of the received notification data to these nine systems, and software executed by these nine systems may request that representatives of the corresponding institutions review the disputed terms and evidence and provide input identifying whether the user 110 complied with the contractual agreement within a predetermined time period (e.g., one hour, twenty-four hours, etc.). The systems maintained by these none financial institutions may transmit the provided input back to system 146, and system 146 may process and aggregate the results to determine the consensus decision.
  • By way of example, system 146 may receive responses from seven of the nine computer systems within the predetermined time period, and system 146 may determine that six of the seven financial institutions agree that user 110's performance complied with the terms of the contractual agreement. System 146 may, in certain aspects, and based on the consensus decision, determine in step 510 that user 110's performance complied with the terms of the contractual agreement.
  • The disclosed embodiments are, however, not limited to these exemplary dispute resolution processes. In additional embodiments, system 146 may resolve the dispute in a multi-step process that initially reviews the provided evidence in light of the terms of the contractual agreement, and if the outcome were ambiguous, would establish a final decision regarding user 110's compliance with the contractual agreement on the basis of the consensus decision of the participating financial institutions, as described above. In further embodiments, system 146 may also implement any additional or alternate processes to resolve the identified dispute that would be appropriate to the disputed terms of the contractual agreement, the contracting parties, and/or the corresponding financial institutions.
  • Based on the resolved dispute, system 146 may determine the propriety of the transfer of the second $5,000 installment from user 108 to user 110 (e.g., in step 512). For example, if system 146 were to determine that user 110 completed at least 50% of the agreed-upon renovations by December 1st, user 110's performance may be compliant with the contractual agreement. System 146 may determine that the transfer of the second $5,000 installment from user 108 to user 110 is proper and consistent with the contractual agreement (e.g., step 512; YES), and system 146 may execute software applications that establish and maintain a new ledger block identifying the propriety of the transfer and the resolution of the dispute between users 108 and 110 and between the first and second financial institutions using any of the exemplary techniques described above (e.g., in step 514). Exemplary process 500 is then complete in step 516.
  • If, however, system 146 were to determine that user 110 failed to complete at least 50% of the agreed-upon renovations by December 1st, user 110's performance may be non-compliant with the contractual agreement. System 146 may determine that the transfer of the second $5,000 installment from user 108 to user 110 is inappropriate and inconsistent with the contractual agreement (e.g., step 512; NO), and system 146 may execute software instructions that initiate an additional transaction to reverse the transfer of the second $5,000 installment from user 108 to user 110 and to return the $5,000 in funds to user 108 using any of the exemplary techniques described above (e.g., in step 518). Exemplary process 500 may then pass back to step 514, and system 146 may establish and maintain a new ledger block identifying the impropriety of the transfer and the initiation of the new transaction returning the second $5,000 installment to user 108 using any of the exemplary techniques described above. Exemplary process 500 is then complete in step 516.
  • In the embodiments described above, system 146 of clearinghouse entity 152 may resolve disputes between financial institutions and between contracting parties that involve an interpretation of contractual terms and/or a performance of the contracting parties. In additional aspects, and consistent with the disclosed embodiments, system 146 may apply one or more of the rules and/or event triggers described above to determine a propriety of one or more new ledger blocks added to the hybrid blockchain ledger data structure (and/or one or more sidechain data structures)by systems of various rules authorities (e.g., systems 140 and 141), and further, to reconcile various assets and funds tracked within the hybrid blockchain ledger data structure and/or the one or more corresponding sidechain data structures.
  • Various embodiments have been described herein with reference to the accompanying drawings. It will, however, be evident that various modifications and changes may be made thereto, and additional embodiments may be implemented, without departing from the broader scope of the disclosed embodiments as set forth in the claims that follow.
  • Further, other embodiments will be apparent to those skilled in the art from consideration of the specification and practice of one or more embodiments of the present disclosure. It is intended, therefore, that this disclosure and the examples herein be considered as exemplary only, with a true scope and spirit of the disclosed embodiments being indicated by the following listing of exemplary claims.

Claims (22)

What is claimed is:
1. An apparatus, comprising:
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;
obtaining notification data identifying a dispute involving a contractual agreement between a first party and one or more second parties;
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, the decrypted first data portion identifying a plurality of triggering events controlled by a rules authority, and the decrypted second data portion identifying a plurality of rules associated with the triggering events;
establishing that the identified dispute corresponds to at least one of the triggering events;
identifying, based on the detected second data portion, at least one of the rules that exhibits a causal relationship with the detected first event; and
generating an electronic command to perform one or more operations to resolve the identified dispute consistent with the at least one identified rule.
2. The apparatus of claim 1, wherein the executed instructions further cause the at least one processor to perform the step of detecting, within at least a portion of the accessed blockchain ledger data, an occurrence of an electronic transfer of funds from an account of the first party to an account of at least one of the second parties, the electronic transfer being initiated in response to a performance of one or more activities by the at least one second party.
3. The apparatus of claim 2, wherein:
at least one of a device of the second party or a system of a financial institution associated with the first party executes instructions to initiate the electronic transfer of funds from the first party account to the at least one second party account; and
the executed instructions further cause the at least one processor to perform the step of receiving the notification data from at least one of a device of the first party or a system of a financial institution associated with the first party.
4. The apparatus of claim 2, wherein the identified dispute represents a dispute between the first and second parties regarding a conformity of the one or more performed activities to the contractual agreement.
5. The apparatus of claim 2, wherein the executed instructions further cause the at least one processor to perform the steps of:
extracting data that characterizes the contractual agreement from at least a portion of the accessed blockchain ledger data;
determining, based on the data characterizing the contractual agreement and a portion of the notification data, that the performance of the one of more activities by the second party fails to conform to the contractual agreement; and
in response to the determination, generate a first electronic command to initiate a reversal of the electronic transfer.
6. The apparatus of claim 5, wherein the portion of the notification data identified the one or more performed activities.
7. The apparatus of claim 5, wherein the executed instructions further cause the at least one processor to perform the step of generating a second electronic command to establish at least one additional data block, the at least one additional data block comprising at least one of (0 data identifying the dispute, (ii) data establishing the non-conformity of the one or more performed activities with the contractual agreement, or (Hi) data indicative of the initiated reversal of the electronic transfer.
8. The apparatus of claim 5, wherein the executed instructions further cause the at least one processor to perform the steps of:
obtaining rules authority data identifying a plurality of entities that function as rules authorities for the at least one blockchain ledger;
transmit at least a portion of the obtained notification data and the extracted contractual agreement data to systems associated with corresponding ones of the entities, the transmitted portion of the notification data identifying the one or more performed activities;
receiving, from the entity systems, data indicative of the conformity of the one or more performed activities to the contractual agreement; and
determining, based on the received data, whether the one of more performs activities by the second party conforms to the contractual agreement.
9. The apparatus of claim 1, wherein the executed instructions further cause the at least one processor to perform the steps of:
identifying an establishment of at least one additional data block;
determining that the establishment of the at least one additional data block corresponds to at least one of the triggering events;
identifying, based on the detected second data portion, at least one of the rules that exhibits a causal relationship with the detected first event; and
generating an electronic command to append the at least one additional data block to the at least one blockchain ledger in accordance with the at least one rule.
10. The apparatus of claim 1, wherein the executed instructions further cause the at least one processor to perform the steps of:
receiving data identifying at least one additional rule, the additional rule being associated with at least one of the triggering events, and the data being received from a device associated with at least one of the first or second parties;
modifying the decrypted second data portion to incorporate at least a portion of the received data; and
encrypting the modified second data portion using the second cryptographic key.
11. The apparatus of claim 1, wherein the executed instructions further cause the at least one processor to perform the steps of:
receiving data identifying at least one additional triggering event controlled by the rules authority, the data being received from a device associated with at least one of the first or second parties;
modifying the decrypted first data portion to incorporate at least a portion of the received data; and
encrypting the modified first data portion using the first cryptographic key.
12. The apparatus of claim 1, wherein:
the first cryptographic key comprises a private cryptographic key associated with at least one of the parties; and
the second cryptographic key corresponds to a master cryptographic key; and
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 a secure data repository; and
establishing at least one access permission for the stored master cryptographic key, the at least one established access permission preventing at least one of parties from accessing the stored master cryptographic key.
13. A computer-implemented method, comprising:
accessing, using at least one processor, data corresponding to at least one blockchain ledger;
obtaining, using the at least one processor, notification data identifying a dispute involving a contractual agreement between a first party and one or more second parties;
using the at least one processor, decrypting (0 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, the decrypted first data portion identifying a plurality of triggering events controlled by a rules authority, and the decrypted second data portion identifying a plurality of rules associated with the triggering events;
establishing, using the at least one processor, that the identified dispute corresponds to at least one of the triggering events;
identifying, using the at least one processor, and based on the detected second data portion, at least one of the rules that exhibits a causal relationship with the detected first event; and
generating, using the at least one processor, an electronic command to perform one or more operations to resolve the identified dispute consistent with the at least one identified rule.
14. The method of claim 13, further comprising detecting, within at least a portion of the accessed blockchain ledger data, an occurrence of an electronic transfer of funds from an account of the first party to an account of at least one of the second parties, the electronic transfer being initiated in response to a performance of one or more activities by the at least one second party.
15. The method of claim 14, wherein:
at least one of a device of the second party or a system of a financial institution associated with the first party executes instructions to initiate the electronic transfer of funds from the first party account to the at least one second party account; and
the executed instructions further cause the at least one processor to perform the step of receiving the notification data from at least one of a device of the first party or a system of a financial institution associated with the first party.
16. The method of claim 14, wherein;
the identified dispute represents a dispute between the first and second parties regarding a conformity of the one or more performed activities to the contractual agreement; and
the method further comprises:
extracting data that characterizes the contractual agreement from at least a portion of the accessed blockchain ledger data;
determining, based on the data characterizing the contractual agreement and a portion of the notification data, that the performance of the one of more activities by the second party fails to conform to the contractual agreement;
in response to the determination, generate a first electronic command to initiate a reversal of the electronic transfer and
generating a second electronic command to establish at least one additional data block, the at least one additional data block comprising at least one of (i) data identifying the dispute, (ii) data establishing the non-conformity of the one or more performed activities with the contractual agreement, or (iii) data indicative of the initiated reversal of the electronic transfer.
17. The apparatus of claim 16, further comprising:
obtaining rules authority data identifying a plurality of entities that function as rules authorities for the at least one blockchain ledger;
transmit at least a portion of the obtained notification data and the extracted contractual agreement data to systems associated with corresponding ones of the entities, the transmitted portion of the notification data identifying the one or more performed activities;
receiving, from the entity systems, data indicative of the conformity of the one or more performed activities to the contractual agreement; and
determining, based on the received data, whether the one of more performs activities by the second party conforms to the contractual agreement.
18. The apparatus of claim 13, further comprising:
identifying an establishment of at least one additional data block;
determining that the establishment of the at least one additional data block corresponds to at least one of the triggering events;
identifying, based on the detected second data portion, at least one of the rules that exhibits a causal relationship with the detected first event; and
generating an electronic command to append the at least one additional data block to the at least one blockchain ledger in accordance with the at least one rule.
19. The apparatus of claim 13, further comprising;
receiving data identifying at least one additional rule, the additional rule being associated with at least one of the triggering events, and the data being received from a device associated with at least one of the first or second parties;
modifying the decrypted second data portion to incorporate at least a portion of the received data; and
encrypting the modified second data portion using the second cryptographic key.
20. The apparatus of claim 13, further comprising:
receiving data identifying at least one additional triggering event controlled by the rules authority, the data being received from a device associated with at least one of the first or second parties;
modifying the decrypted first data portion to incorporate at least a portion of the received data; and
encrypting the modified first data portion using the first cryptographic key.
21. The apparatus of claim 13, wherein:
the first cryptographic key comprises a private cryptographic key associated with at least one of the parties; and
the second cryptographic key corresponds to a master cryptographic key; and
the method further comprises:
generating the master cryptographic key;
storing the generated master cryptographic key in a portion of a secure data repository; and
establishing at least one access permission for the stored master cryptographic key, the at least one established access permission preventing at least one of parties from accessing the stored master cryptographic key.
22. A tangible, non-transitory computer-readable medium storing instructions that, when executed by at least one processor, cause the at least one processor to perform a method comprising the following steps:
accessing data corresponding to at least one blockchain ledger;
obtaining notification data identifying a dispute involving a contractual agreement between a first party and one or more second parties;
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, the decrypted first data portion identifying a plurality of triggering events controlled by a rules authority, and the decrypted second data portion identifying a plurality of rules associated with the triggering events;
establishing that the identified dispute corresponds to at least one of the triggering events;
identifying, based on the detected second data portion, at least one of the rules that exhibits a causal relationship with the detected first event; and
generating an electronic command to perform one or more operations to resolve the identified dispute consistent with the at least one identified rule.
US14/936,812 2015-08-13 2015-11-10 Systems and methods for detecting and resolving data inconsistencies among networked devices using hybrid private-public blockchain ledgers Pending US20170046693A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US201562204768P true 2015-08-13 2015-08-13
US14/936,812 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

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US14/936,812 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
CA2948239A CA2948239A1 (en) 2015-08-13 2016-11-10 Systems and methods for detecting and resolving data inconsistencies among networked devices using hybrid private-public blockchain ledgers

Publications (1)

Publication Number Publication Date
US20170046693A1 true US20170046693A1 (en) 2017-02-16

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 Pending US20170046652A1 (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 Pending US20170046698A1 (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,833 Pending US20170046664A1 (en) 2015-08-13 2015-11-10 Systems and methods for tracking and transferring ownership of connected devices using blockchain ledgers
US14/936,812 Pending 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
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,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,076 Abandoned US20170046694A1 (en) 2015-08-13 2016-08-11 Secure Tracking Beacons Using Distributed Ledgers
US15/235,528 Active 2037-01-20 US10163080B2 (en) 2015-08-13 2016-08-12 Document tracking on a distributed ledger
US15/235,199 Active 2038-06-16 US10552805B2 (en) 2015-08-13 2016-08-12 Systems and methods for monitoring referrals
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 Pending US20190340588A1 (en) 2015-08-13 2019-07-19 Systems and methods for tracking subdivided ownership of connected devices using block-chain ledgers
US16/519,122 Pending US20190347627A1 (en) 2015-08-13 2019-07-23 Systems and method for tracking enterprise events using hybrid public-private blockchain ledgers
US16/715,471 Pending US20200118094A1 (en) 2015-08-13 2019-12-16 Secure real-time product ownership tracking using distributed electronic ledgers

Family Applications Before (5)

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 Pending US20170046652A1 (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 Pending US20170046698A1 (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,833 Pending US20170046664A1 (en) 2015-08-13 2015-11-10 Systems and methods for tracking and transferring ownership of connected devices using blockchain ledgers

Family Applications After (12)

Application Number Title Priority Date Filing Date
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,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,076 Abandoned US20170046694A1 (en) 2015-08-13 2016-08-11 Secure Tracking Beacons Using Distributed Ledgers
US15/235,528 Active 2037-01-20 US10163080B2 (en) 2015-08-13 2016-08-12 Document tracking on a distributed ledger
US15/235,199 Active 2038-06-16 US10552805B2 (en) 2015-08-13 2016-08-12 Systems and methods for monitoring referrals
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 Pending US20190340588A1 (en) 2015-08-13 2019-07-19 Systems and methods for tracking subdivided ownership of connected devices using block-chain ledgers
US16/519,122 Pending US20190347627A1 (en) 2015-08-13 2019-07-23 Systems and method for tracking enterprise events using hybrid public-private blockchain ledgers
US16/715,471 Pending US20200118094A1 (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) CA2938530A1 (en)

Cited By (53)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106952124A (en) * 2017-03-16 2017-07-14 北京牛链科技有限公司 Electronic bill management system and method based on distribution book keeping operation
CN107070896A (en) * 2017-03-20 2017-08-18 智牛股权投资基金(平潭)合伙企业(有限合伙) A kind of safe and efficient block chain customization login method and security hardening system
US20170244757A1 (en) * 2016-02-22 2017-08-24 Bank Of America Corporation System for external validation of secure process transactions
CN107197036A (en) * 2017-06-22 2017-09-22 广东网金控股股份有限公司 A kind of consistent processing method of information based on block chain and terminal
CN107844710A (en) * 2017-09-26 2018-03-27 浙江大学 A kind of contract generation system and generation method
US9979718B2 (en) * 2016-05-11 2018-05-22 Bank Of America Corporation System for managing security and access to resource sub-components
US20180218454A1 (en) * 2017-01-27 2018-08-02 Walmart Apollo, Llc Managing participation in a monitored system using blockchain technology
CN108551437A (en) * 2018-03-13 2018-09-18 百度在线网络技术(北京)有限公司 Method and apparatus for authentication information
EP3379447A1 (en) * 2017-03-22 2018-09-26 Siemens Aktiengesellschaft Method and device for tamper-proof storing of information relating to object-specific measures
WO2018183099A1 (en) * 2017-03-29 2018-10-04 Alibaba Group Holding Limited Blockchain-based transaction processing method and apparatus
CN108667815A (en) * 2018-04-18 2018-10-16 价值互联(广州)信息技术有限公司 Block chain secret key encipher-decipher method, device and terminal based on bio-identification
US10110576B2 (en) 2016-05-23 2018-10-23 Accenture Global Solutions Limited Distributed key secret for rewritable blockchain
US10129238B2 (en) 2016-02-10 2018-11-13 Bank Of America Corporation System for control of secure access and communication with different process data networks with separate security features
CN108874890A (en) * 2017-05-16 2018-11-23 江峰 A kind of band can openly record the block catenary system of man-machine system
US10142347B2 (en) 2016-02-10 2018-11-27 Bank Of America Corporation System for centralized control of secure access to process data network
CN108985089A (en) * 2018-08-01 2018-12-11 清华大学 Internet data shared system
CN109542980A (en) * 2018-11-20 2019-03-29 北京磁云数字科技有限公司 A kind of data processing method, device, equipment and the medium of block chain
US20190122300A1 (en) * 2013-04-10 2019-04-25 Patrick Damien O'Brien Apparatus, code, methods and systems for providing proof of trust related to smart contracts
US20190139136A1 (en) * 2015-07-09 2019-05-09 Templum, Inc. Systems and methods for trading, clearing and settling securities transactions using blockchain technology
US10289716B1 (en) 2017-10-31 2019-05-14 International Business Machines Corporation Consistent reporting using blockchain
US20190149333A1 (en) * 2017-11-15 2019-05-16 International Business Machines Corporation Methods and systems for supporting fairness in secure computations
US10296248B2 (en) 2017-09-01 2019-05-21 Accenture Global Solutions Limited Turn-control rewritable blockchain
US10304062B1 (en) * 2018-03-23 2019-05-28 Td Professional Services, Llc Computer architecture incorporating blockchain based immutable audit ledger for compliance with data regulations
WO2019100112A1 (en) * 2017-11-22 2019-05-31 Resolve Disputes Online Technology Limited A system, method, computer program and data signal for communicating and event based verification
WO2019133800A1 (en) * 2017-12-29 2019-07-04 Paypal, Inc. Dispute resolution cryptocurrency sidechain system
US10361869B2 (en) * 2016-08-23 2019-07-23 International Business Machines Corporation Event ledger
US10382205B1 (en) * 2018-06-10 2019-08-13 Hajoon Ko Security system and method for using a blockchain service through privacy-aware blockchain arbitration server
US10402796B2 (en) 2016-08-29 2019-09-03 Bank Of America Corporation Application life-cycle transition record recreation system
WO2019168633A1 (en) * 2018-02-28 2019-09-06 Intuit Inc. Method and system for overseeing execution of graph-based contracts using hash chains
US20190303445A1 (en) * 2018-03-29 2019-10-03 salesforce.com,inc Hybrid Cloud Chain Management of Centralized and Decentralized Data
CN110490003A (en) * 2019-08-09 2019-11-22 杭州安存网络科技有限公司 User's trust data generation method, acquisition methods, apparatus and system
CN110489980A (en) * 2019-07-22 2019-11-22 杭州凯腾互联网技术有限公司 A kind of credit asset processing system based on block chain
EP3595241A1 (en) * 2018-07-13 2020-01-15 Kevin Kei Tuncer Distributed blockchain with delayed transaction
US20200074470A1 (en) * 2018-09-05 2020-03-05 International Business Machines Corporation Database configuration for asset transfers
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
WO2020068534A1 (en) * 2018-09-26 2020-04-02 Mastercard International Incorporated Method and system for dispute resolution in a public blockchain
US10693643B2 (en) 2018-11-07 2020-06-23 Pitt Ohio Methods and systems for distributed cryptographically secured data validation
WO2020142412A1 (en) * 2018-12-30 2020-07-09 Tunnel International Inc. Methods, devices, and systems for secure payments
US10735183B1 (en) * 2017-06-30 2020-08-04 Experian Information Solutions, Inc. Symmetric encryption for private smart contracts among multiple parties in a private peer-to-peer network
US10762504B2 (en) 2016-02-22 2020-09-01 Bank Of America Corporation System for external secure access to process data network
WO2020215083A1 (en) * 2019-04-19 2020-10-22 Coinbase, Inc. Systems and methods for blockchain administration
US10834062B2 (en) 2018-06-20 2020-11-10 International Business Machines Corporation Unlinking ownership of successive asset transfers on a blockchain
US10833843B1 (en) * 2015-12-03 2020-11-10 United Services Automobile Association (USAA0 Managing blockchain access
WO2020242550A1 (en) * 2019-05-29 2020-12-03 Vivigie Inc Ensuring trust levels when using electronic currencies
US10880078B2 (en) * 2016-08-19 2020-12-29 Advanced New Technologies Co., Ltd. Data storage, data check, and data linkage method and apparatus
EP3665696A4 (en) * 2017-08-08 2020-12-30 QuiO Technologies LLC Self-executing agents for gathering health information between trusted parties
US10887254B2 (en) * 2018-02-01 2021-01-05 Red Hat, Inc. Enterprise messaging using blockchain system
US10909617B2 (en) 2010-03-24 2021-02-02 Consumerinfo.Com, Inc. Indirect monitoring and reporting of a user's credit data
US10958438B2 (en) 2018-10-31 2021-03-23 Advanced New Technologies Co., Ltd. Method, apparatus, and electronic device for blockchain-based recordkeeping
US10958637B2 (en) 2018-12-28 2021-03-23 Mox-SpeedChain, LLC Preselected issuance and data operations loops in a hybrid distributed network ecosystem
US10992735B2 (en) 2019-07-22 2021-04-27 Bank Of America Corporation System for generating event-based linkages between distributed resources for tailored data access
US11004147B1 (en) 2008-08-14 2021-05-11 Experian Information Solutions, Inc. Multi-bureau credit file freeze and unfreeze
US11023604B1 (en) * 2020-03-09 2021-06-01 United Services Automobile Association (Usaa) Systems and methods to track, store, and manage events, rights and liabilities

Families Citing this family (495)

* 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
US8706530B2 (en) 2010-09-29 2014-04-22 Dacadoo Ag Automated health data acquisition, processing and communication system
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
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
US10740732B2 (en) 2015-05-20 2020-08-11 Ripple Luxembourg S.A. Resource transfer system
US20160342986A1 (en) * 2015-05-20 2016-11-24 402 Technologies S.A. Transfer costs in a resource transfer system
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
US10599679B2 (en) 2015-08-17 2020-03-24 Accenture Global Solutions Limited Platform data aggregation and semantic modeling
CA2941896C (en) * 2015-09-14 2020-10-13 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
US20170132393A1 (en) * 2015-11-10 2017-05-11 Wal-Mart Stores, Inc. Prescription home delivery
US20170132615A1 (en) * 2015-11-11 2017-05-11 Bank Of America Corporation Block chain alias for person-to-person payments
CN109874340A (en) * 2015-11-18 2019-06-11 全球样本解决方案股份有限公司 For encrypting the secure storage of biological sample data and the distributed system of retrieval
US10423938B1 (en) * 2015-11-20 2019-09-24 United Services Automobile Association Identifying negotiable instrument fraud using distributed ledger systems
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
JP2018536957A (en) * 2015-11-30 2018-12-13 シェイプシフト・アーゲーShapeShift AG System and method for improving security in blockchain asset transactions
KR101678795B1 (en) * 2015-11-30 2016-11-22 전삼구 Iot-basesd things management system and method using block chain authentification
US10013573B2 (en) * 2015-12-16 2018-07-03 International Business Machines Corporation Personal ledger blockchain
US10521780B1 (en) 2015-12-16 2019-12-31 United Services Automobile Association (Usaa) Blockchain based transaction management
US10521973B2 (en) * 2015-12-17 2019-12-31 International Business Machines Corporation System for monitoring and enforcement of an automated fee payment
SG10202006900PA (en) 2015-12-22 2020-08-28 Financial & Risk Organisation Ltd 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
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
US10810673B1 (en) * 2016-01-22 2020-10-20 United Services Automobile Association (Usaa) Systems and methods for automatically reallocating investment funds
US10116667B2 (en) 2016-01-26 2018-10-30 Bank Of America Corporation System for conversion of an instrument from a non-secured instrument to a secured instrument in a process data network
US20180078843A1 (en) * 2016-02-02 2018-03-22 Bao Tran Smart device
US10754964B2 (en) * 2016-11-01 2020-08-25 Bruce A Pelton Integrated building management sensor system
US10438209B2 (en) * 2016-02-10 2019-10-08 Bank Of America Corporation System for secure routing of data to various networks from a process data network
US20170236120A1 (en) * 2016-02-11 2017-08-17 Oracle International Corporation Accountability and Trust in Distributed Ledger Systems
US9935772B1 (en) * 2016-02-19 2018-04-03 Vijay K Madisetti Methods and systems for operating secure digital management aware applications
US10496989B2 (en) 2016-02-22 2019-12-03 Bank Of America Corporation System to enable contactless access to a transaction terminal using a process data network
US10636033B2 (en) 2016-02-22 2020-04-28 Bank Of America Corporation System for routing of process authorizations and settlement to a user in a process data network
US10440101B2 (en) * 2016-02-22 2019-10-08 Bank Of America Corporation System for external validation of private-to-public transition protocols
US10026118B2 (en) 2016-02-22 2018-07-17 Bank Of America Corporation System for allowing external validation of data in a process data network
US20170243209A1 (en) * 2016-02-22 2017-08-24 Bank Of America Corporation System for grant of user access and data usage in a process data network
US10318938B2 (en) 2016-02-22 2019-06-11 Bank Of America Corporation System for routing of process authorization and settlement to a user in process data network based on specified parameters
US10387878B2 (en) 2016-02-22 2019-08-20 Bank Of America Corporation System for tracking transfer of resources in a process data network
US10178105B2 (en) 2016-02-22 2019-01-08 Bank Of America Corporation System for providing levels of security access to a process data network
US10607285B2 (en) 2016-02-22 2020-03-31 Bank Of America Corporation System for managing serializability of resource transfers in a process data network
US10475030B2 (en) 2016-02-22 2019-11-12 Bank Of America Corporation System for implementing a distributed ledger across multiple network nodes
US10140470B2 (en) 2016-02-22 2018-11-27 Bank Of America Corporation System for external validation of distributed resource status
US10679215B2 (en) 2016-02-22 2020-06-09 Bank Of America Corporation System for control of device identity and usage in a process data network
US10142312B2 (en) 2016-02-22 2018-11-27 Bank Of America Corporation System for establishing secure access for users in a process data network
US10833863B2 (en) * 2016-02-29 2020-11-10 Intel Corporation Device provisioning service
US10540728B2 (en) * 2016-03-09 2020-01-21 Husqvarna Ab Locating substitute construction tools within a construction worksite
CN109219940A (en) * 2016-03-31 2019-01-15 比特飞翔株式会社 Privately owned node, the processing method in privately owned node and the program for it
US10311250B2 (en) * 2016-04-05 2019-06-04 Vchain Technology Limited Method and system for managing personal information within independent computer systems and digital networks
US10212145B2 (en) * 2016-04-06 2019-02-19 Avaya Inc. Methods and systems for creating and exchanging a device specific blockchain for device authentication
ES2716657T3 (en) * 2016-04-07 2019-06-13 Telefonica Sa A method to ensure the correct route of data packets through a particular path of a network
US10366388B2 (en) * 2016-04-13 2019-07-30 Tyco Fire & Security Gmbh Method and apparatus for information management
US10438197B2 (en) * 2016-04-13 2019-10-08 Paypal, Inc. Public ledger authentication system
US20170302663A1 (en) * 2016-04-14 2017-10-19 Cisco Technology, Inc. BLOCK CHAIN BASED IoT DEVICE IDENTITY VERIFICATION AND ANOMALY DETECTION
US10528748B2 (en) * 2016-04-22 2020-01-07 International Business Machines Corporation Context-driven on-device data protection
US10810583B2 (en) * 2016-04-29 2020-10-20 Digital Asset Holdings Digital asset modeling
US20190163883A1 (en) 2016-05-13 2019-05-30 nChain Holdings Limited A method and system for verifying ownership of a digital asset using a distributed hash table and a peer-to-peer distributed ledger
US10362058B2 (en) * 2016-05-13 2019-07-23 Vmware, Inc Secure and scalable data transfer using a hybrid blockchain-based approach
US20190208414A1 (en) * 2016-05-25 2019-07-04 Nokia Technologies Oy Method, Device and System for Utilizing Block Chain to Define Trusted Circle
US10587699B2 (en) * 2016-05-26 2020-03-10 International Business Machines Corporation Coordinating the use of independent radio receivers associated with a single transmitter
US10417188B2 (en) * 2016-05-27 2019-09-17 Mastercard International Incorporated Method and system for transferring trust across block chain segments
AU2017279012A1 (en) * 2016-06-06 2018-08-16 Financial & Risk Organisation Limited Systems and methods for providing a personal distributed ledger
CN108780390A (en) * 2016-06-06 2018-11-09 汤森路透全球资源无限公司 System and method for providing identity scoring
US10341309B1 (en) * 2016-06-13 2019-07-02 Allstate Insurance Company Cryptographically protecting data transferred between spatially distributed computing devices using an intermediary database
US10972448B2 (en) * 2016-06-20 2021-04-06 Intel Corporation Technologies for data broker assisted transfer of device ownership
EP3475889A4 (en) * 2016-06-23 2020-01-08 Capital One Services, LLC Neural network systems and methods for generating distributed representations of electronic transaction information
US10411905B2 (en) * 2016-07-01 2019-09-10 Intel Corporation Public key infrastructure using blockchains
US10700853B2 (en) * 2016-07-12 2020-06-30 International Business Machines Corporation Token identity and attribute management
US10425399B2 (en) 2016-07-12 2019-09-24 International Business Machines Corporation Template-based distributed certificate issuance in a multi-tenant environment
US10097344B2 (en) 2016-07-15 2018-10-09 Mastercard International Incorporated Method and system for partitioned blockchains and enhanced privacy for permissioned blockchains
US10755327B2 (en) 2016-07-18 2020-08-25 Royal Bank Of Canada Distributed ledger platform for vehicle records
US10417217B2 (en) 2016-08-05 2019-09-17 Chicago Mercantile Exchange Inc. Systems and methods for blockchain rule synchronization
US20180046992A1 (en) * 2016-08-10 2018-02-15 Jpmorgan Chase Bank, N.A. Systems and methods for account reconciliation using a distributed ledger
US10915969B2 (en) * 2016-08-11 2021-02-09 Jpmorgan Chase Bank, N.A. Systems and methods for enhanced organizational transparency using a credit chain
US11010830B2 (en) * 2016-08-16 2021-05-18 Autofi, Inc. Loan selection interface for a vehicle transfer transaction
US10402829B1 (en) * 2016-09-09 2019-09-03 Worldpay, Llc Systems and methods for using shared databases for managing supplemental payment sources
US10423947B1 (en) * 2016-09-09 2019-09-24 Worldpay, Llc User interfaces for using shared databases for managing supplemental payment sources
US20180075677A1 (en) 2016-09-09 2018-03-15 Tyco Integrated Security, LLC Architecture for Access Management
WO2019053694A1 (en) * 2017-09-18 2019-03-21 Thomson Reuters Global Resources Unlimited Company Systems and methods for smart contract intervention
US10419218B2 (en) * 2016-09-20 2019-09-17 United States Postal Service Methods and systems for a digital trust architecture
US10581847B1 (en) * 2016-09-27 2020-03-03 Amazon Technologies, Inc. Blockchain-backed device and user provisioning
US10339014B2 (en) * 2016-09-28 2019-07-02 Mcafee, Llc Query optimized distributed ledger system
US10984081B2 (en) * 2016-09-30 2021-04-20 Cable Television Laboratories, Inc. Systems and methods for secure person to device association
US10676219B2 (en) 2016-10-01 2020-06-09 Shay C. Colson Printing packaging in expanded material
US10791108B2 (en) * 2016-10-04 2020-09-29 Joseph Jay Austin Apparatuses, systems and methods for tracking network connected devices
US20180096349A1 (en) * 2016-10-05 2018-04-05 The Toronto-Dominion Bank Distributed electronic ledger with metadata
US20180108089A1 (en) * 2016-10-14 2018-04-19 International Business Machines Corporation Transactions and linked assets on a blockchain
US10666424B1 (en) * 2016-10-20 2020-05-26 Massachusetts Mutual Life Insurance Company Systems and methods for trigger based synchronized updates in a distributed records environment
US10679221B1 (en) * 2016-10-20 2020-06-09 Massachusetts Mutual Life Insurance Company Systems and methods for trigger based synchronized updates in a distributed records environment
US10685009B1 (en) * 2016-10-20 2020-06-16 Massachusetts Mutual Life Insurance Company Systems and methods for trigger based synchronized updates in a distributed records environment
US10733616B1 (en) * 2016-10-20 2020-08-04 Massachusets Mutual Life Insurance Company Systems and methods for trigger based synchronized updates in a distributed records environment
US11004130B2 (en) * 2016-10-26 2021-05-11 International Business Machines Corporation Computer implemented method, an apparatus and a non transitory computer readable storage medium for verifying reviews on a blockchain
US10171509B2 (en) * 2016-11-10 2019-01-01 International Business Machines Corporation Filtering and redacting blockchain transactions
US10491378B2 (en) * 2016-11-16 2019-11-26 StreamSpace, LLC Decentralized nodal network for providing security of files in distributed filesystems
US10164977B2 (en) 2016-11-17 2018-12-25 Avaya Inc. Mobile caller authentication for contact centers
WO2018094297A2 (en) * 2016-11-19 2018-05-24 COSTANZ, Mario A System and method for interaction object reconciliation in a public ledger blockchain environment
JP2019536398A (en) * 2016-11-19 2019-12-12 ウィリアムズ,ドミニク System architecture and method of processing data therein
US20180144292A1 (en) * 2016-11-22 2018-05-24 Wal-Mart Stores, Inc. Apparatus and method for tracking consumer premises inventory
US10862959B2 (en) * 2016-11-28 2020-12-08 Keir Finlow-Bates Consensus system and method for adding data to a blockchain
GB2557277A (en) * 2016-12-02 2018-06-20 Cavendish Wood Ltd A distributed ledger
US20180157688A1 (en) * 2016-12-03 2018-06-07 Dell Products, Lp Ledger-chained distributed information handling systems and methods
US10013246B2 (en) * 2016-12-03 2018-07-03 Dell Products, Lp Distributed information handling systems and methods for automatic object code replacement and patching
US20180157700A1 (en) * 2016-12-06 2018-06-07 International Business Machines Corporation Storing and verifying event logs in a blockchain
US10373159B2 (en) * 2016-12-07 2019-08-06 International Business Machines Corporation Concomitance of an asset and identity block of a blockchain
US10396997B2 (en) * 2016-12-14 2019-08-27 International Business Machines Corporation Container-based operating system and method
US20180167394A1 (en) * 2016-12-14 2018-06-14 Wal-Mart Stores, Inc. Controlling access to a locked space using cryptographic keys stored on a blockchain
US20180174094A1 (en) * 2016-12-15 2018-06-21 International Business Machines Corporation Blockchain-based food product shelf-life management
US10552381B2 (en) * 2016-12-16 2020-02-04 International Business Machines Corporation Shared document editing in the blockchain
US20180189816A1 (en) * 2016-12-30 2018-07-05 Daniel Lee DeVore Method for Networking Users for Submission and Processing of Referrals
US10114981B2 (en) * 2016-12-31 2018-10-30 Intel Corporation Architecture for telemetry and adaptive lifetime control of integrated circuits
US10275739B2 (en) * 2017-01-05 2019-04-30 International Business Machines Corporation Tracking assets with a blockchain
US10776879B1 (en) 2017-01-17 2020-09-15 State Farm Mutual Automobile Insurance Company Blockchain controlled multi-carrier auction system for usage-based auto insurance
US10824759B1 (en) 2017-01-25 2020-11-03 State Farm Mutual Automobile Insurance Company Systems and methods for verifying agent sales data via blockchain
US10861015B1 (en) 2017-01-25 2020-12-08 State Farm Mutual Automobile Insurance Company Blockchain based account funding and distribution
US20180218456A1 (en) * 2017-01-30 2018-08-02 Dais Technology, Inc. Risk securitization and pricing system
US10158479B2 (en) 2017-02-06 2018-12-18 Northern Trust Corporation Systems and methods for generating, uploading and executing code blocks within distributed network nodes
US20180225661A1 (en) 2017-02-07 2018-08-09 Microsoft Technology Licensing, Llc Consortium blockchain network with verified blockchain and consensus protocols
US20180232731A1 (en) * 2017-02-14 2018-08-16 Digital Treasury Corporation Supply chain recording method with traceable function by implementing blockchain technique
US20180232693A1 (en) * 2017-02-16 2018-08-16 United Parcel Service Of America, Inc. Autonomous services selection system and distributed transportation database(s)
CN107018125B (en) 2017-02-17 2019-08-09 阿里巴巴集团控股有限公司 A kind of block catenary system, date storage method and device
US10755322B2 (en) * 2017-02-22 2020-08-25 Red Hat, Inc. Blockchain-based software instance usage determination
CN106911465B (en) * 2017-02-27 2018-09-04 腾讯科技(深圳)有限公司 Block generation method and device
US20210133888A1 (en) 2017-03-03 2021-05-06 State Farm Mutual Automobile Insurance Company Using a Distributed Ledger for the Auto Claims Process
US20180253691A1 (en) * 2017-03-06 2018-09-06 Walmart Apollo, Llc Systems and Methods for Delivering Products to a Customer
US20180260921A1 (en) * 2017-03-08 2018-09-13 Bsquare Corp. Remote machine operation through distributed permissioning
CN106952094B (en) * 2017-03-10 2018-09-04 腾讯科技(深圳)有限公司 Electronic bill management method and device
US10257724B2 (en) 2017-03-10 2019-04-09 Walmart Apollo, Llc System and method for “always on” offline transaction collection
WO2018165940A1 (en) * 2017-03-16 2018-09-20 Hong Kong R & D Centre for Logistics and Supply Chain Management Enabling Technologies Limited A system and method for controlling a ledger of transactions
US10963889B2 (en) * 2017-03-16 2021-03-30 Sap Se Cross-system object tracking platform
US10693636B2 (en) * 2017-03-17 2020-06-23 Guigen Xia Authenticated network
WO2018170504A1 (en) 2017-03-17 2018-09-20 Labyrinth Research Llc Unified control of privacy-impacting devices
CN107451002B (en) * 2017-03-24 2020-11-10 北京瑞卓喜投科技发展有限公司 Active verification method and system for block chain of modified block volume data
US10680915B2 (en) * 2017-03-29 2020-06-09 Cisco Technology, Inc. Consumption-based licensing of network features based on blockchain transactions
US20180285971A1 (en) * 2017-03-31 2018-10-04 International Business Machines Corporation Management of consumer debt collection using a blockchain and machine learning
US10320566B2 (en) * 2017-04-04 2019-06-11 International Business Machines Corporation Distributed logging of application events in a blockchain
US10805068B1 (en) 2017-04-05 2020-10-13 State Farm Mutual Automobile Insurance Company Systems and methods for feature-based rating via blockchain
US20180294957A1 (en) * 2017-04-07 2018-10-11 Walmart Apollo, Llc System for Recording Ownership of Digital Works and Providing Backup Copies
WO2018187410A1 (en) * 2017-04-07 2018-10-11 Walmart Apollo, Llc Systems and methods for data backup and authentication using blockchain
DE102017006572A1 (en) * 2017-04-12 2018-10-18 Diehl Defence Gmbh & Co. Kg Method for protecting a networked military system
US20180300693A1 (en) * 2017-04-17 2018-10-18 International Business Machines Corporation Providing out-of-band verification for blockchain transactions
KR101882802B1 (en) * 2017-04-17 2018-07-27 주식회사 코인플러그 Method for blockchain based management of documents in use of unspent transaction output based protocol and document management server using the same
CN107220896A (en) * 2017-04-23 2017-09-29 杭州复杂美科技有限公司 A kind of financing by accounts receivable based on block chain technology
CN110546939A (en) * 2017-04-26 2019-12-06 维萨国际服务协会 System and method for recording data representing multiple interactions
US10419209B1 (en) * 2017-04-26 2019-09-17 Wells Fargo Bank, N.A. Parallel assurance of blockchain signatures
CN107122938A (en) * 2017-04-27 2017-09-01 电子科技大学 A kind of freight logistics scheduling and tracking based on block chain
US10832335B1 (en) 2017-05-01 2020-11-10 State Farm Mutual Automobile Insurance Company Systems and methods for generating usage-based insurance contracts for peer-to-peer transactions
US10929931B1 (en) 2017-05-02 2021-02-23 State Farm Mutual Automobile Insurance Company Distributed ledger system for carrier discovery
CN107273410B (en) * 2017-05-03 2020-07-07 上海点融信息科技有限责任公司 Block chain based distributed storage
US10411895B2 (en) * 2017-05-04 2019-09-10 International Business Machines Corporation Creating match cohorts and exchanging protected data using blockchain
CN107122985A (en) * 2017-05-09 2017-09-01 广东工业大学 A kind of agricultural-product supply-chain traceability system based on Internet of Things and block chain
US11010831B1 (en) 2017-05-10 2021-05-18 State Farm Mutual Automobile Insurance Company Identifying multiple mortgage ready properties
US10949919B1 (en) * 2017-05-10 2021-03-16 State Farm Mutual Automobile Insurance Company Approving and updating dynamic mortgage applications
WO2018209148A1 (en) * 2017-05-10 2018-11-15 Responsible Gold Operations Ltd. Method of tokenization of asset-backed digital assets
US10943294B1 (en) 2017-05-10 2021-03-09 State Farm Mutual Automobile Insurance Company Continuously monitoring and updating mortgage ready data
US9882918B1 (en) * 2017-05-15 2018-01-30 Forcepoint, LLC User behavior profile in a blockchain
CN107154850A (en) * 2017-05-17 2017-09-12 北京汇通金财信息科技有限公司 A kind of processing method and processing device of block chain data
TWI644556B (en) * 2017-05-18 2018-12-11 富邦金融控股股份有限公司 Know your customer (kyc) data sharing system with privacy and method thereof
WO2018213804A2 (en) * 2017-05-19 2018-11-22 Zest Labs, Inc. Process and condition recording and validation using a blockchain
CN107392623B (en) * 2017-05-22 2020-09-11 创新先进技术有限公司 Service execution method and device
CN107395664B (en) * 2017-05-22 2019-09-03 阿里巴巴集团控股有限公司 A kind of method and device that business executes
US10554649B1 (en) * 2017-05-22 2020-02-04 State Farm Mutual Automobile Insurance Company Systems and methods for blockchain validation of user identity and authority
US20180341775A1 (en) * 2017-05-23 2018-11-29 International Business Machines Corporation Digital license authentication with secure privacy logging
CN107194281B (en) * 2017-05-25 2019-07-16 成都知道创宇信息技术有限公司 A kind of anti-fake system based on block chain technology
US10740733B2 (en) 2017-05-25 2020-08-11 Oracle International Corporaton Sharded permissioned distributed ledgers
CN107368259B (en) * 2017-05-25 2020-07-10 创新先进技术有限公司 Method and device for writing service data into block chain system
US20180341915A1 (en) * 2017-05-29 2018-11-29 Wipro Limited Method and system for tracking and managing regulatory certificates of aircraft components
US10447770B2 (en) * 2017-05-30 2019-10-15 Verizon Patent And Licensing Inc. Blockchain micro-services framework
US10382965B2 (en) * 2017-05-30 2019-08-13 Sap Se Identity verification using computer-implemented decentralized ledger
WO2018222412A1 (en) * 2017-05-31 2018-12-06 Walmart Apollo, Llc Systems and methods to enable robotic node participation in peer-to-peer commercial transactions
US20180349990A1 (en) * 2017-06-06 2018-12-06 International Business Machines Corporation Point-of-sale system for real-time risk assessment, instant message-based collaborative guarantorship, and method for using the same
EP3413507A1 (en) * 2017-06-09 2018-12-12 Nokia Technologies Oy Electronic documents certification
KR101851261B1 (en) * 2017-06-09 2018-04-23 씨토 주식회사 Centralized remote metering system for security based on private block-chained data
WO2018226806A1 (en) * 2017-06-09 2018-12-13 Walmart Apollo, Llc Systems and methods for delivering retail items
US10796304B2 (en) * 2017-06-12 2020-10-06 Bank Of America Corporation System and method of managing computing resources
US20200119925A1 (en) * 2017-06-16 2020-04-16 Visa International Service Association Blockchain Network Interaction Controller
CN107194613B (en) * 2017-06-20 2020-12-08 无锡井通网络科技有限公司 Digital asset coding method
EP3419210A1 (en) * 2017-06-22 2018-12-26 PLC Group AG Method for generating a transaction of a blockchain and method for validating a block of a blockchain
US10567177B2 (en) * 2017-06-26 2020-02-18 Sony Corporation Media channel monitoring to prove content presentation
US10608910B2 (en) 2017-06-26 2020-03-31 Myomega Systems Gmbh Using blockchain to track information for devices on a network
WO2019005985A1 (en) * 2017-06-27 2019-01-03 Jpmorgan Chase Bank, N.A. System and method for using a distributed ledger gateway
CN107391298B (en) * 2017-07-06 2021-02-09 上海策链信息科技有限公司 Data storage state detection method and device and computer readable storage medium
US10944546B2 (en) * 2017-07-07 2021-03-09 Microsoft Technology Licensing, Llc Blockchain object interface
US10123202B1 (en) * 2017-07-11 2018-11-06 Verizon Patent And Licensing Inc. System and method for virtual SIM card
CN107316186A (en) * 2017-07-13 2017-11-03 齐德昱 The computer system method for supporting and support system of innovation undertaking employment
US20190026669A1 (en) * 2017-07-18 2019-01-24 Filmio, Inc. Methods, systems, and devices for producing video projects
US10664797B2 (en) * 2017-07-19 2020-05-26 Amazon Technologies, Inc. Distributed ledger certification
US10616324B1 (en) * 2017-07-20 2020-04-07 Architecture Technology Corporation Decentralized ledger system and method for enterprises
JP2020527817A (en) 2017-07-20 2020-09-10 ラーバ アイディー プロプライアタリー リミティド Safety tag
US10643202B2 (en) * 2017-07-25 2020-05-05 Bank Of America Corporation Real-time processing distributed ledger system
US10476879B2 (en) * 2017-07-26 2019-11-12 International Business Machines Corporation Blockchain authentication via hard/soft token verification
CN107481096A (en) * 2017-07-26 2017-12-15 中融亚太贸易有限公司 Life store internet+running business model
CN109308597A (en) * 2017-07-27 2019-02-05 冯军 The method and its system shared based on enterprise connections resource mutual assistance
US10594487B2 (en) 2017-07-27 2020-03-17 International Business Machines Corporation Password management and verification with a blockchain
US10924466B2 (en) * 2017-07-28 2021-02-16 SmartAxiom, Inc. System and method for IOT security
US10990687B2 (en) 2017-08-01 2021-04-27 Dell Products L.P. System and method for user managed encryption recovery using blockchain for data at rest
US10862671B2 (en) 2017-08-02 2020-12-08 Visa International Service Association Global ownership registry
CN109391643B (en) * 2017-08-03 2020-08-07 中国移动通信有限公司研究院 Block chain lightweight processing method, block chain node and storage medium
US20190052453A1 (en) * 2017-08-14 2019-02-14 Honeywell International Inc. Apparatus and method for using blockchains with secure custody transfer data, sealing data, and other data associated with material transfers
WO2019035111A1 (en) * 2017-08-17 2019-02-21 Osr Enterprises Ag A system and method for trading information
CN107609876A (en) * 2017-08-18 2018-01-19 北京云知科技有限公司 A kind of method and system for recovering block chain assets
EP3447993A1 (en) * 2017-08-23 2019-02-27 Panasonic Intellectual Property Corporation of America Driving management system, vehicle, and information processing method
US10795977B2 (en) * 2017-08-24 2020-10-06 Oracle International Corporation Digital asset traceability and assurance using a distributed ledger
EP3676849A4 (en) * 2017-08-28 2020-10-28 Visa International Service Association Layered recording networks
US20190065593A1 (en) * 2017-08-28 2019-02-28 Forward Blockchain, LLC Distributed Ledger Registry System
WO2019046473A1 (en) * 2017-08-29 2019-03-07 Walmart Apollo, Llc System and method for collaborative computing power
CN107508812B (en) * 2017-08-29 2020-10-23 广东工业大学 Industrial control network data storage method, calling method and system
US20190065733A1 (en) * 2017-08-29 2019-02-28 Seagate Technology Llc Device lifecycle distributed ledger
US20190066067A1 (en) * 2017-08-29 2019-02-28 Walmart Apollo, Llc System and method for collaborative sharing of digital currency
US20190065544A1 (en) * 2017-08-29 2019-02-28 Walmart Apollo, Llc System and method for collaborative sharing of database information
US20190066205A1 (en) * 2017-08-30 2019-02-28 StartEngine Crowdfunding, Inc. Peer-to-peer trading with blockchain technology
LT3451608T (en) * 2017-09-04 2020-02-25 Siemens Aktiengesellschaft Filter unit based data communication system including a blockchain platform
US10728036B2 (en) * 2017-09-05 2020-07-28 PeerNova, Inc. Cryptographically linking related events processed across multiple processing systems
US10872381B1 (en) 2017-09-06 2020-12-22 State Farm Mutual Automobile Insurance Company Evidence oracles
US10878062B1 (en) * 2017-09-06 2020-12-29 State Farm Mutual Automobile Insurance Company Systems and methods for analyzing captured biometric data
US10891694B1 (en) 2017-09-06 2021-01-12 State Farm Mutual Automobile Insurance Company Using vehicle mode for subrogation on a distributed ledger
WO2019055290A1 (en) * 2017-09-12 2019-03-21 Northwestern University Blockchain distribution network
US10361870B2 (en) 2017-09-14 2019-07-23 The Toronto-Dominion Bank Management of cryptographically secure exchanges of data using permissioned distributed ledgers
US10831890B2 (en) * 2017-09-19 2020-11-10 Palo Alto Research Center Incorporated Method and system for detecting attacks on cyber-physical systems using redundant devices and smart contracts
IT201700107125A1 (en) * 2017-09-25 2019-03-25 Shared Method for executing smart contracts by means of electronic processing using blockchain technology
WO2019067533A1 (en) * 2017-09-27 2019-04-04 Walmart Apollo, Llc System and methods for resolving data discrepancies in a distributed system with blockchain controls
CN107862215B (en) * 2017-09-29 2020-10-16 创新先进技术有限公司 Data storage method, data query method and device
CN107819572B (en) * 2017-09-29 2021-01-22 北京比特大陆科技有限公司 Command transmission method and device and electronic equipment
US10484343B1 (en) 2017-10-03 2019-11-19 Cerebri AI Inc. Distributed logging for securing non-repudiable multi-party transactions
US10339931B2 (en) 2017-10-04 2019-07-02 The Toronto-Dominion Bank Persona-based conversational interface personalization using social network preferences
US10460748B2 (en) 2017-10-04 2019-10-29 The Toronto-Dominion Bank Conversational interface determining lexical personality score for response generation with synonym replacement
US10491375B2 (en) * 2017-10-05 2019-11-26 Accenture Global Solutions Limited Secure verification of conditions of a contract using a set of verification tools
US10630642B2 (en) 2017-10-06 2020-04-21 Stealthpath, Inc. Methods for internet communication security
US10397186B2 (en) 2017-10-06 2019-08-27 Stealthpath, Inc. Methods for internet communication security
US10374803B2 (en) 2017-10-06 2019-08-06 Stealthpath, Inc. Methods for internet communication security
US10367811B2 (en) 2017-10-06 2019-07-30 Stealthpath, Inc. Methods for internet communication security
US10375019B2 (en) 2017-10-06 2019-08-06 Stealthpath, Inc. Methods for internet communication security
US10361859B2 (en) 2017-10-06 2019-07-23 Stealthpath, Inc. Methods for internet communication security
US10375050B2 (en) 2017-10-10 2019-08-06 Truepic Inc. Methods for authenticating photographic image data
US10832241B2 (en) 2017-10-11 2020-11-10 International Business Machines Corporation Transaction reservation for block space on a blockchain
CN107730176A (en) * 2017-10-18 2018-02-23 上海唯链信息科技有限公司 A kind of goods logistic information inquiry system and method based on block chain
US20190123889A1 (en) * 2017-10-20 2019-04-25 Sap Se Document flow tracking using blockchain
WO2019083837A2 (en) * 2017-10-23 2019-05-02 Spangenberg Erich Lawson System and method of ip ownership and ip registration via a blockchain transactional platform
US20200250665A1 (en) * 2017-10-24 2020-08-06 Eland Blockchain Fintech Inc. Blockchain-based electronic transaction system free of sales platform and method thereof
CN108038786A (en) * 2017-11-14 2018-05-15 北京欧链科技有限公司 The processing method and system of Claims Resolution event based on block chain
US10534923B2 (en) * 2017-11-14 2020-01-14 Wipro Limited System and method for tracking and managing additive manufacturing of components
US10628566B2 (en) 2017-11-20 2020-04-21 International Business Machines Corporation Authentication using delegated identities
US10810683B2 (en) 2017-11-21 2020-10-20 General Electric Company Hierarchical meta-ledger transaction recording
US10686611B2 (en) * 2017-11-24 2020-06-16 International Business Machines Corporation Data anonymizing blockchain system
US10819684B2 (en) * 2017-11-24 2020-10-27 International Business Machines Corporation Cognitive blockchain for internet of things
CN111386699A (en) * 2017-11-28 2020-07-07 索尼公司 Digital ledger camera and image functionality
US10764031B2 (en) * 2017-12-07 2020-09-01 International Business Machines Corporation Blockchain system for pattern recognition
US10320843B1 (en) 2017-12-08 2019-06-11 Symbiont.Io, Inc. Methods, systems, and devices for encrypted electronic storage and confidential network transfer of private data through a trustless distributed ledger technology system
US10637900B2 (en) * 2017-12-08 2020-04-28 Beatrice T. O'Brien Computerized network system for initiating, facilitating, auditing, and managing communications and documents involving professional expertise
US10699493B2 (en) * 2017-12-09 2020-06-30 Hausman Properties, Llc System and method for toll transactions utilizing a distributed ledger
US20190180274A1 (en) * 2017-12-11 2019-06-13 Global Mobile Finance, Inc. Methodology and system for a blockchain-based mobile money gateway
US10673620B2 (en) * 2017-12-14 2020-06-02 Paypal, Inc. Blockchain validation system
CN108039944B (en) * 2017-12-15 2020-09-01 复旦大学 De-ordering encryption framework algorithm with forward security
US20190188655A1 (en) * 2017-12-19 2019-06-20 International Business Machines Corporation Dynamic blockchain transactional policy management
EP3729305A1 (en) * 2017-12-19 2020-10-28 Blockchain IT Solutions Pty Ltd A system and method for implementing a computer network
KR102008757B1 (en) * 2017-12-19 2019-10-21 주식회사 이글루시스템즈 Data Security System And Data Security Method Based On Block Chain
US10630769B2 (en) * 2017-12-26 2020-04-21 Akamai Technologies, Inc. Distributed system of record transaction receipt handling in an overlay network
CN108197214B (en) * 2017-12-28 2020-12-29 中国人民银行数字货币研究所 Method and system for inquiring digital currency transaction information
US10958436B2 (en) 2017-12-28 2021-03-23 Industrial Technology Research Institute Methods contract generator and validation server for access control of contract data in a distributed system with distributed consensus
CN108074180A (en) * 2017-12-28 2018-05-25 广州富融信息技术有限公司 A kind of recent financial development air control system and its construction method based on block chain technology
CN110019235A (en) * 2017-12-29 2019-07-16 百度在线网络技术(北京)有限公司 Data storage, restoration methods, device, equipment and medium based on block chain
US10715323B2 (en) 2017-12-29 2020-07-14 Ebay Inc. Traceable key block-chain ledger
US10896418B2 (en) 2017-12-29 2021-01-19 Ebay Inc. Secure management of data files using a blockchain
WO2019133339A1 (en) 2017-12-29 2019-07-04 Walmart Apollo, Llc System and method for biometric credit based on blockchain
CN108229962B (en) * 2018-01-04 2021-04-06 众安信息技术服务有限公司 Permission management method and system based on block chain
CA3088610A1 (en) * 2018-01-17 2019-07-25 Geeq Corporation Blockchain methods, nodes, systems and products
US10627250B2 (en) 2018-01-25 2020-04-21 Walmart Apollo, Llc System and method for tracking vehicle mileage using blockchain
US20190236594A1 (en) * 2018-01-29 2019-08-01 KRNC Inc. Cryptographic and fiat currency mechanics
US10621542B2 (en) 2018-01-31 2020-04-14 Walmart Apollo, Llc System and method for crowd source loaned code with blockchain
US20190236564A1 (en) * 2018-01-31 2019-08-01 Walmart Apollo, Llc System and method for digital currency via blockchain
CA3087930A1 (en) * 2018-02-02 2019-08-08 F. Hoffmann-La Roche Ag A method for controlling distribution of a product in a computer network and system
US20190251627A1 (en) * 2018-02-11 2019-08-15 Loopring Project Ltd Methods and systems for digital asset transaction
TWI659373B (en) * 2018-02-14 2019-05-11 財團法人工業技術研究院 Blockchain system and method thereof
US10614253B2 (en) 2018-02-14 2020-04-07 Fortune Vieyra Systems and methods for state of data management
US10755201B2 (en) 2018-02-14 2020-08-25 Lucid Circuit, Inc. Systems and methods for data collection and analysis at the edge
US20190253247A1 (en) * 2018-02-14 2019-08-15 Lucid Circuit, Inc. Systems and methods for generating identity attestations attributable to internally generated data collected at the edge
US20190251526A1 (en) * 2018-02-15 2019-08-15 Mark Jackson Method and System for Implementing Digital Currency Tied to Physical Precious Metals
US10846806B2 (en) 2018-02-17 2020-11-24 Constru Ltd System and method for annotation of construction site images
US20190180273A1 (en) * 2018-02-20 2019-06-13 Intercontinental Exchange Holdings, Inc. Offline crypto asset custodian
US10693662B2 (en) * 2018-02-22 2020-06-23 Idlogiq Inc. Methods for secure serialization of supply chain product units
US10025797B1 (en) * 2018-02-23 2018-07-17 True Return Systems LLC Method and system for separating storage and process of a computerized ledger for improved function
US20190266577A1 (en) * 2018-02-23 2019-08-29 Jpmorgan Chase Bank, N.A. Systems and methods for private settlement of distributed ledger transactions
WO2019167116A1 (en) * 2018-02-27 2019-09-06 日本電気株式会社 Blockchain management system, blockchain management device, information provision device, and blockchain management method
CN108415784B (en) * 2018-02-27 2020-04-24 阿里巴巴集团控股有限公司 Cross-block-chain interaction method, device, system and electronic equipment
WO2019169374A1 (en) * 2018-03-02 2019-09-06 Ranieri Solutions, Llc Methods and apparatus for servicing an obligation utilizing a blockchain
SG11202008382QA (en) 2018-03-06 2020-09-29 Americorp Invest Llc Customized view of restricted information recorded into a blockchain
US10951626B2 (en) 2018-03-06 2021-03-16 Americorp Investments Llc Blockchain-based commercial inventory systems and methods
US20200406859A1 (en) * 2018-03-07 2020-12-31 Ford Global Technologies, Llc Blockchain authentication of a vehicle rider
CN108566375A (en) * 2018-03-12 2018-09-21 深圳壹账通智能科技有限公司 The method, terminal and storage medium of message communicating between multiterminal based on block chain
US10838996B2 (en) 2018-03-15 2020-11-17 International Business Machines Corporation Document revision change summarization
CN108449336A (en) * 2018-03-16 2018-08-24 浙江创邻科技有限公司 Data traceability based on block chain and strong encryption method, apparatus, medium and system
US20190288847A1 (en) * 2018-03-16 2019-09-19 General Electric Company Industrial data verification using secure, distributed ledger
DE102018002266A1 (en) * 2018-03-19 2019-09-19 Erich Utsch Ag Method for the cryptological securing of a license plate for a motor vehicle
EP3543891A1 (en) * 2018-03-23 2019-09-25 Telefonica Digital España, S.L.U. A computer implemented method and a system for tracking of certified documents lifecycle and computer programs thereof
KR101893729B1 (en) * 2018-03-28 2018-10-04 주식회사 마크로젠 Data sharing method based on multiple block-chains
US10498808B2 (en) 2018-03-28 2019-12-03 Bank Of America Corporation Blockchain-based property management
CN108520462B (en) 2018-03-30 2020-07-24 阿里巴巴集团控股有限公司 Service execution method and device based on block chain and electronic equipment
CN108470266A (en) * 2018-04-01 2018-08-31 南京交通职业技术学院 Product tracking system based on block chain
CN108573386A (en) * 2018-04-01 2018-09-25 南京米好信息安全有限公司 Product place of production traceability system based on block chain
CN108712257B (en) * 2018-04-03 2020-04-17 阿里巴巴集团控股有限公司 Cross-block-chain authentication method and device and electronic equipment
CN108632254B (en) * 2018-04-03 2020-09-25 电子科技大学 Access control method of intelligent home environment based on private chain
US10938922B2 (en) * 2018-04-04 2021-03-02 Christopher Allen Noble Cloud platforms, services, and methods
US20190311343A1 (en) * 2018-04-06 2019-10-10 Walmart Apollo, Llc Point of sale system network with distributed ownership record database
CN108809932A (en) * 2018-04-09 2018-11-13 杭州拾贝知识产权服务有限公司 A kind of deposit system, method and readable medium based on block chain
CN108492093A (en) * 2018-04-09 2018-09-04 李俊山 A kind of application model of block chain technology in efficiency of government promotion
US10365922B1 (en) 2018-04-10 2019-07-30 Sap Se Distributed-ledger based enterprise application deployment and management
US10846375B2 (en) * 2018-04-11 2020-11-24 Microsoft Technology Licensing, Llc Software license distribution and validation using a distributed immutable data store
US20190317924A1 (en) * 2018-04-12 2019-10-17 ISARA Corporation Constructing a Multiple Entity Root of Trust
WO2019204315A1 (en) * 2018-04-17 2019-10-24 Filmio, Inc. Project creation system using blockchain
CN110730960A (en) 2018-04-20 2020-01-24 因特比有限公司 Method and system for storing binary large object
US20190327080A1 (en) * 2018-04-24 2019-10-24 International Business Machines Corporation Document transfer processing for blockchains
US11010403B2 (en) 2018-04-24 2021-05-18 Microsoft Technology Licensing, Llc Relational distributed ledger for smart contracts
US20190340269A1 (en) * 2018-05-02 2019-11-07 Rockwell Automation Technologies, Inc. Blockchain-enabled industrial devices
US20210117933A1 (en) * 2018-05-03 2021-04-22 3M Innovative Properties Company Personal protective equipment management system with distributed digital blockchain ledger
DE102018206880A1 (en) * 2018-05-04 2019-11-07 Audi Ag Method for determining a functional set of activated functions in a functional unit as well as functional unit which can be operated according to the method
EP3791347A1 (en) * 2018-05-06 2021-03-17 Strong Force TX Portfolio 2018, LLC Methods and systems for improving machines and systems that automate execution of distributed ledger and other transactions in spot and forward markets for energy, compute, storage and other resources
US10692086B2 (en) * 2018-05-07 2020-06-23 Accenture Global Solutions Limited Distributed ledger based identity and origins of supply chain application enabling financial inclusion and sustainability
US20190347605A1 (en) * 2018-05-08 2019-11-14 Jpmorgan Chase Bank, N.A. Systems and methods for distributed ledger-based floorplanning
CN108632284B (en) * 2018-05-10 2021-02-23 网易(杭州)网络有限公司 User data authorization method, medium, device and computing equipment based on block chain
WO2019213752A1 (en) * 2018-05-11 2019-11-14 Echoai Corp. A method and system for managing digital assets in a blockchain
US10796022B2 (en) * 2018-05-16 2020-10-06 Ebay Inc. Weighted source data secured on blockchains
US20190356471A1 (en) * 2018-05-17 2019-11-21 International Business Machines Corporation Ad-hoc smart contract generation in a blockchain
CN108712423A (en) * 2018-05-18 2018-10-26 北京三六五八网络科技有限公司 Right management method and device
CN108804084A (en) * 2018-05-23 2018-11-13 夏文斌 A kind of overall situation block chain link border construction method
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
US20190363890A1 (en) * 2018-05-24 2019-11-28 Walmart Apollo, Llc Nested Blockchain System
CN108876572A (en) * 2018-05-29 2018-11-23 阿里巴巴集团控股有限公司 The account checking method and device, electronic equipment of block chain transaction
CN108694594A (en) * 2018-05-29 2018-10-23 阿里巴巴集团控股有限公司 Commodity source tracing method and device, electronic equipment based on block chain
CN108876401A (en) * 2018-05-29 2018-11-23 阿里巴巴集团控股有限公司 Commodity Claims Resolution method and device, electronic equipment based on block chain
US10693716B2 (en) 2018-05-29 2020-06-23 At&T Mobility Ii Llc Blockchain based device management
US20190372769A1 (en) * 2018-06-01 2019-12-05 Integra, Inc. Blockchain-universal document identification
US10891576B2 (en) 2018-06-04 2021-01-12 gabi Solutions, Inc. System and method for recommending a transaction to replace a device based upon total cost of ownership
US10812680B2 (en) * 2018-06-04 2020-10-20 gabi Solutions, Inc. System and method for securely accessing, manipulating and controlling documents and devices using natural language processing
WO2019236482A1 (en) 2018-06-04 2019-12-12 Rafalko Noah Telecommunication system and method for settling session transactions
US10762058B2 (en) 2018-06-04 2020-09-01 gabi Solutions, Inc. System and method for providing user-centric content to an electronic device
US10430125B1 (en) 2018-06-04 2019-10-01 gabi Solutions, Inc. System, network architecture and method for accessing and controlling an electronic device
US20190378133A1 (en) * 2018-06-06 2019-12-12 International Business Machines Corporation Decentralized out-of-band accelerated blockchain transaction processing
US10901493B2 (en) 2018-06-11 2021-01-26 Lucid Circuit, Inc. Systems and methods for autonomous hardware compute resiliency
US20190378152A1 (en) * 2018-06-11 2019-12-12 International Business Machines Corporation Direct marketing via chained interactions in a blockchain
EP3584759A1 (en) * 2018-06-18 2019-12-25 Panasonic Intellectual Property Corporation of America Management method, management apparatus, and program
DK3584654T3 (en) * 2018-06-19 2020-08-10 Siemens Ag Hierarchically distributed ledger
WO2019246399A1 (en) * 2018-06-20 2019-12-26 Google Llc Digital ledger for unique item ids with ownership
CN108921696B (en) * 2018-06-26 2020-10-16 广州天高软件科技有限公司 Intelligent contract calling and contract transaction verification method based on block chain
CN109519005B (en) * 2018-06-26 2021-02-02 杨豫森 Distributed building data station
US20200007344A1 (en) * 2018-06-28 2020-01-02 Blockchain Integrated Partners, Llc Systems and methods for data validation and assurance
US20200007343A1 (en) * 2018-06-28 2020-01-02 Blockchain Integrated Partners, Llc Systems and methods for data validation and assurance
US10887081B2 (en) 2018-06-28 2021-01-05 International Business Machines Corporation Audit trail configuration in a blockchain
US10915552B2 (en) * 2018-06-28 2021-02-09 International Business Machines Corporation Delegating credentials with a blockchain member service
CN108765615B (en) * 2018-06-29 2021-03-19 北京阿尔山区块链联盟科技有限公司 Block chain-based card punching information storage method and system
US10664799B2 (en) * 2018-06-29 2020-05-26 OMNY, Inc. Supply mesh platform
US10756884B2 (en) 2018-07-02 2020-08-25 International Business Machines Corporation On-chain governance of blockchain
US10979445B2 (en) 2018-07-09 2021-04-13 At&T Intellectual Property I, L.P. Security management of devices using blockchain technology
CN109088954A (en) * 2018-07-13 2018-12-25 中国电子科技集团公司第十五研究所 A kind of method of distribution object identification information registering and parsing
CN109003051A (en) * 2018-07-18 2018-12-14 杭州复杂美科技有限公司 A kind of car insurance setting loss Claims Resolution system, method, equipment and storage medium
CN110491131A (en) * 2018-07-18 2019-11-22 江苏恒宝智能系统技术有限公司 A kind of vehicle violation management system based on block chain
US20200027183A1 (en) * 2018-07-19 2020-01-23 Uber Technologies, Inc. Network computer system to determine suitabilities of vehicles using blockchain records
CN110309325A (en) * 2018-07-24 2019-10-08 腾讯科技(深圳)有限公司 Data processing method, device and storage medium based on block chain
WO2020023441A1 (en) * 2018-07-24 2020-01-30 Trucki Llc Systems for supply chain event management
US10887082B2 (en) * 2018-07-24 2021-01-05 Vmware, Inc. Internet of things blockchain auditing
CN108921518A (en) * 2018-07-27 2018-11-30 中国水产科学研究院渔业机械仪器研究所 Deep-sea fishing ship drawing review system and method
US10929545B2 (en) 2018-07-31 2021-02-23 Bank Of America Corporation System for providing access to data stored in a distributed trust computing network
CN109067524B (en) * 2018-07-31 2020-07-10 杭州复杂美科技有限公司 Public and private key pair generation method and system
US10776781B2 (en) * 2018-08-01 2020-09-15 Mff Llc Systems and methods for facilitating transactions using a digital currency
US20200042913A1 (en) * 2018-08-01 2020-02-06 Sap Se Distributed ledger-based enterprise resource planning system
US10944560B2 (en) * 2018-08-02 2021-03-09 International Business Machines Corporation Privacy-preserving identity asset exchange
WO2020033458A1 (en) * 2018-08-06 2020-02-13 Dale Hunt Direct-scan cash-management systems and methods
CN108880823A (en) * 2018-08-07 2018-11-23 佛山市苔藓云链科技有限公司 A kind of method and system generating the block chain quickly to navigate
US10360668B1 (en) 2018-08-13 2019-07-23 Truepic Inc. Methods for requesting and authenticating photographic image data
US10361866B1 (en) 2018-08-13 2019-07-23 Truepic Inc. Proof of image authentication on a blockchain
US10992455B2 (en) * 2018-08-14 2021-04-27 International Business Machines Corporation Consensus based ad-hoc group creation
CA3109624A1 (en) * 2018-08-16 2020-02-20 Car Iq Inc. Blockchain based hardware authentication
CN109214822A (en) * 2018-08-19 2019-01-15 黄旭婷 A kind of company information identifying system and method based on block chain technology
CN109257334B (en) * 2018-08-21 2021-04-09 广州杰赛科技股份有限公司 Block chain-based data uplink system, method and storage medium
DE102018214158A1 (en) * 2018-08-22 2020-02-27 Audi Ag Control device for enabling functions, motor vehicle with a control device and a method for operating a control device
WO2020046786A1 (en) * 2018-08-27 2020-03-05 Fireblocks Ltd. System and method for securing crypto-asset transactions
CN108683690A (en) * 2018-08-27 2018-10-19 创新维度科技(北京)有限公司 Method for authenticating, user equipment, authentication device, authentication server and storage medium
WO2020042931A1 (en) * 2018-08-28 2020-03-05 白杰 Public chain-based transaction method and blockchain system
WO2020042926A1 (en) * 2018-08-28 2020-03-05 白杰 Blockchain public chain maintenance method, device, node and blockchain public chain
US20200076612A1 (en) * 2018-08-29 2020-03-05 Advanced Messaging Technologies, Inc. Electronic Document Signing Using Blockchain
WO2020044350A1 (en) * 2018-08-29 2020-03-05 G.B. Bittax Ltd Tracing cryptocurrencies
WO2020044211A1 (en) * 2018-08-30 2020-03-05 Lorenzo RICCA Method and system of distributing and tracking products and/or services
AU2019327577A1 (en) * 2018-08-31 2021-04-29 Bleu Tech Enterprises, Inc. Long range decentralized mobile payment network using bluetooth
WO2020052878A1 (en) * 2018-09-11 2020-03-19 Sicpa Holding Sa Advanced methods, systems and devices for registering information in a database
WO2020055829A1 (en) * 2018-09-12 2020-03-19 Liveramp, Inc. Consent provenance and compliance tracking over a complex consumer data supply chain using blockchain distributed ledger
WO2020055413A1 (en) * 2018-09-13 2020-03-19 Hitachi, Ltd. Blockchain for audit
CN109213452A (en) * 2018-09-14 2019-01-15 广州闰业信息技术服务有限公司 A kind of electronics safety system based on block chain
WO2020060733A1 (en) * 2018-09-18 2020-03-26 Operem Inc. Computer method for secure disclosure of information
WO2020060542A1 (en) * 2018-09-19 2020-03-26 Gabi Solutions, LLC System and method for securely accessing, manipulating and controlling documents and devices using natural language processing
WO2020058966A1 (en) * 2018-09-21 2020-03-26 Blocktest Global Systems and methods for research and development using blockchain and smart contract technology
WO2020061593A1 (en) * 2018-09-22 2020-03-26 Yakira David Decentralized key generation and distribution over a blockchain-based network
US20200104810A1 (en) * 2018-09-28 2020-04-02 Paypal, Inc. Systems, methods, and computer program products providing an identity-storing browser
WO2020072659A1 (en) * 2018-10-02 2020-04-09 Mutualink, Inc. Consensus-based voting for network member identification employing blockchain-based identity signature mechanisms
US10521196B1 (en) 2018-10-04 2019-12-31 Sap Se Distributed ledger-based rapid application development
US10992456B2 (en) * 2018-10-09 2021-04-27 International Business Machines Corporation Certifying authenticity of data modifications
CN110309259A (en) * 2018-10-10 2019-10-08 腾讯科技(深圳)有限公司 Audit result data storage, querying method, audit item storage method and device
CN108989475A (en) * 2018-10-11 2018-12-11 国网河南省电力公司 Distributed storage transmission architecture based on block chain
US10958419B2 (en) 2018-10-22 2021-03-23 Motorola Solutions, Inc. Method to establish distributed ledger networks with multiple access levels for an incident
WO2020085347A1 (en) * 2018-10-22 2020-04-30 力 松永 Construction procedure management system employing blockchain and data transaction system using same
CN109447803B (en) * 2018-10-26 2020-10-27 全链通有限公司 Alliance chain accounting method, equipment, alliance chain and storage medium
WO2020088735A1 (en) * 2018-10-29 2020-05-07 Telefonaktiebolaget Lm Ericsson (Publ) Verifying data integrity
US20200134638A1 (en) * 2018-10-30 2020-04-30 Verint Americas Inc. Systems and methods using blockchain for monitoring and tracking customer service representative actions
CN109660350A (en) * 2018-10-31 2019-04-19 阿里巴巴集团控股有限公司 Data based on block chain deposit card method and device, electronic equipment
US20200134606A1 (en) * 2018-10-31 2020-04-30 EMC IP Holding Company LLC Asset management in asset-based blockchain system
US10965472B2 (en) * 2018-11-02 2021-03-30 Hitachi, Ltd. Secure bootstrap for a blockchain network
JP6810259B2 (en) * 2018-11-07 2021-01-06 アドバンスド ニュー テクノロジーズ カンパニー リミテッド Manage private transactions on the blockchain network based on workflow
US10642825B2 (en) * 2018-11-09 2020-05-05 Innoplexus Ag System and method for interoperability of blockchains
CN109446845A (en) * 2018-11-15 2019-03-08 蒋魁 A kind of information processing system and method based on block chain
US20200160340A1 (en) * 2018-11-21 2020-05-21 Capital One Services, Llc Distributed fraud detection system within mesh networks
ZA201907671B (en) * 2018-11-23 2020-11-25 Xchain Pty Ltd T/A Atmx Systems and methods relating to cryptocurrencies
CN109635584B (en) * 2018-11-23 2019-08-27 浙江工商大学 A kind of data link privacy calculation method based on block chain
US10979298B2 (en) 2018-11-23 2021-04-13 International Business Machines Corporation Collaboration network and server
US10841178B2 (en) * 2018-11-26 2020-11-17 International Business Machines Corporation Cognitive balancing IT ecosystems
CN109685448A (en) * 2018-11-27 2019-04-26 建经投资咨询有限公司 A kind of engineering project bidding Management method and system
US20200167770A1 (en) * 2018-11-28 2020-05-28 Bank Of America Corporation Blockchain implementation across multiple organizations
CN109685486B (en) * 2018-11-28 2020-12-11 杭州云象网络技术有限公司 Block chain technology-based aggregation chain architecture
US20200175033A1 (en) * 2018-11-29 2020-06-04 International Business Machines Corporation Distributed decentralized matching
CN109587253A (en) * 2018-12-11 2019-04-05 浙江大学 A method of distributed storage is realized to file based on block chain
US10826705B2 (en) 2018-12-13 2020-11-03 International Business Machines Corporation Compact state database system
WO2020122990A1 (en) * 2018-12-14 2020-06-18 Ibuild Global Inc. Systems, methods, and user interfaces for planning, execution, and verification of construction tasks
US20200204344A1 (en) * 2018-12-19 2020-06-25 Oath Inc. Blockchain ledger growth management
US20200202668A1 (en) * 2018-12-20 2020-06-25 Sony Interactive Entertainment LLC Anti-fraud cloud gaming blockchain
CN109711191A (en) * 2018-12-20 2019-05-03 佛山市建宇工程招标代理有限公司 It invites and submit bids method and system
US10861008B2 (en) 2018-12-21 2020-12-08 Capital One Services, Llc System and method for optimizing cryptocurrency transactions
US10637644B1 (en) * 2018-12-21 2020-04-28 Capital One Services, Llc System and method for authorizing transactions in an authorized member network
CN110020543B (en) * 2018-12-21 2020-09-15 阿里巴巴集团控股有限公司 Data processing method and device based on block chain
US20200210996A1 (en) * 2018-12-27 2020-07-02 Capital One Services, Llc Systems, methods, and platforms for providing tracking through blockchain networks
TWI694704B (en) * 2018-12-28 2020-05-21 鴻海精密工業股份有限公司 Data batch storage method, device and computer storage medium
WO2020140015A1 (en) * 2018-12-28 2020-07-02 Mox-SpeedChain, LLC Private blockchain ecosystems for enabling secure computing operations
CN109660357A (en) * 2018-12-29 2019-04-19 东莞见达信息技术有限公司 Digital asset register method, verification method, device, equipment and storage medium
CN109493235A (en) * 2018-12-29 2019-03-19 杭州趣链科技有限公司 A kind of supply chain financial system and its construction method based on block chain
US10999077B2 (en) 2019-01-02 2021-05-04 Bank Of America Corporation Data protection using sporadically generated universal tags
CN109615403A (en) * 2019-01-02 2019-04-12 固安京蓝云科技有限公司 Internet of Things equipment, server and the agricultural product source tracing method based on block chain
US10962965B2 (en) * 2019-01-15 2021-03-30 Fisher-Rosemount Systems, Inc. Maintaining quality control, regulatory, and parameter measurement data using distributed ledgers in process control systems
US10992676B2 (en) 2019-01-16 2021-04-27 EMC IP Holding Company LLC Leveraging blockchain technology for auditing cloud service for data protection compliance
US10992458B2 (en) * 2019-01-16 2021-04-27 EMC IP Holding Company LLC Blockchain technology for data integrity regulation and proof of existence in data protection systems
CN109903151A (en) * 2019-01-21 2019-06-18 苏宁易购集团股份有限公司 Mortgage vehicle fence realization method and system based on block chain technology
US20200235912A1 (en) * 2019-01-23 2020-07-23 Servicenow, Inc. Immutable asset and connected service management
CN109872139B (en) * 2019-01-31 2020-10-23 杭州复杂美科技有限公司 Transaction replacement method, apparatus and storage medium
CN110008715B (en) * 2019-01-31 2020-05-05 阿里巴巴集团控股有限公司 Method for realizing privacy protection in block chain, node and storage medium
CN109760632B (en) * 2019-01-31 2020-06-02 青岛科技大学 Vehicle tracking system based on block chain GPS positioning identification
CN109889866A (en) * 2019-02-13 2019-06-14 湖南众益文化传媒股份有限公司 A kind of advertisement detecting system and method based on block chain
US11010394B2 (en) * 2019-02-15 2021-05-18 Drfirst.Com, Inc. Efficient access of chainable records
US10425230B1 (en) * 2019-03-01 2019-09-24 Capital One Services, Llc Identity and electronic signature verification in blockchain
JP2020528586A (en) * 2019-03-04 2020-09-24 アリババ グループ ホウルディング リミテッド Methods and devices for providing transaction data to blockchain systems for processing
US10909533B2 (en) * 2019-03-13 2021-02-02 Stream Source Technologies System and methods of securely matching a buyer to a seller
US20200313890A1 (en) * 2019-03-25 2020-10-01 Micron Technology, Inc. Verifying identity of a vehicle entering a trust zone
US20200313851A1 (en) * 2019-03-25 2020-10-01 Micron Technology, Inc. Local ledger block chain for secure updates
CN110096903B (en) * 2019-03-26 2021-04-30 罗克佳华科技集团股份有限公司 Asset verification method based on block chain and block chain network system
US10491608B1 (en) * 2019-03-26 2019-11-26 Farmobile Llc Distributed transaction-based security and tracking of agricultural machine and agronomic data
US10990563B2 (en) 2019-04-11 2021-04-27 Advanced New Technologies Co., Ltd. Information read/write method and apparatus based on blockchain
US10825024B1 (en) 2019-04-12 2020-11-03 Symbiont.Io, Inc. Systems, devices, and methods for DLT-based data management platforms and data products
EP3723013A1 (en) * 2019-04-12 2020-10-14 Siemens Aktiengesellschaft Asset tracking system and method
US10691640B1 (en) * 2019-04-18 2020-06-23 Alibaba Group Holding Limited Storing an asset update record
US10992460B2 (en) * 2019-04-23 2021-04-27 Advanced New Technologies Co., Ltd. Blockchain-based advertisement monitoring method and apparatus, and electronic device
CN110163604B (en) * 2019-04-29 2021-02-09 华中科技大学 Block chain asset transfer method based on multi-party verification
US11009859B2 (en) 2019-05-06 2021-05-18 Fisher-Rosemount Systems, Inc. Framework for privacy-preserving big-data sharing using distributed ledger
CN110097382A (en) * 2019-05-08 2019-08-06 杜柏池 A kind of market behavior traceability system
CN110111108A (en) * 2019-05-15 2019-08-09 袁园 A kind of secure financial management system based on block chain technology
WO2020236560A1 (en) * 2019-05-23 2020-11-26 Mastercard International Incorporated Method and system for generalized provenance solution for blockchain supply chain applications
WO2020243652A1 (en) * 2019-05-31 2020-12-03 Nike Innovate C.V. Multi-channel communication platform with dynamic response goals
CN110191133A (en) * 2019-06-04 2019-08-30 湖北五五互联科技有限公司 CDN server use right management method, equipment and computer readable storage medium
US10826684B1 (en) * 2019-06-06 2020-11-03 Syniverse Technologies, Llc System and method of validating Internet of Things (IOT) devices
US20200387619A1 (en) * 2019-06-10 2020-12-10 Microsoft Technology Licensing, Llc Scoped sharing of did-associated data using a selector
CN110225043B (en) * 2019-06-17 2021-04-02 北京瑞策科技有限公司 Packing method and device applied to block chain
US10790990B2 (en) * 2019-06-26 2020-09-29 Alibaba Group Holding Limited Ring signature-based anonymous transaction
SG11202003891YA (en) 2019-06-28 2020-05-28 Advanced New Technologies Co Ltd System and method for blockchain address mapping
CN111164586A (en) 2019-06-28 2020-05-15 阿里巴巴集团控股有限公司 System and method for updating data in a blockchain
CN110471984B (en) 2019-07-15 2020-08-25 阿里巴巴集团控股有限公司 Service processing method and device based on block chain and electronic equipment
US10937096B2 (en) 2019-07-15 2021-03-02 Advanced New Technologies Co., Ltd. Transaction processing in a service blockchain
US20210019680A1 (en) * 2019-07-17 2021-01-21 Biosphere Aerospace, Llc Systems and methods for managing physical assets across territorial boundaries
US10810528B1 (en) 2019-07-19 2020-10-20 Capital One Services, Llc Identifying and utilizing the availability of enterprise resources
US10963828B2 (en) * 2019-07-19 2021-03-30 Capital One Services, Llc Identifying and managing enterprise product availability
US10644889B1 (en) 2019-07-30 2020-05-05 Tetra Ventures LLC Consent management apparatus and system
US10602202B1 (en) 2019-07-30 2020-03-24 Capital One Services, Llc System and techniques for digital data lineage verification
US10673958B1 (en) 2019-08-23 2020-06-02 Capital One Services, Llc System and method for maintaining user session continuity across multiple devices and/or multiple platforms
WO2021038600A1 (en) * 2019-08-31 2021-03-04 Jois Subramanya System and method for real time reconciling, auditing transactions in decentralised network with distributed ledger
SG11202006576UA (en) 2019-09-11 2020-08-28 Alibaba Group Holding Ltd System and method for digital asset management
SG11202003794UA (en) 2019-09-11 2020-05-28 Advanced New Technologies Co Ltd System and method for digital asset transfer
CN111213173A (en) * 2019-09-11 2020-05-29 阿里巴巴集团控股有限公司 System and method for controlling restrictions on digital assets
CN110807209B (en) * 2019-11-01 2021-04-30 腾讯科技(深圳)有限公司 Data processing method, device and storage medium
US10867288B1 (en) 2019-11-25 2020-12-15 Capital One Services, Llc Blockchain payment notification system
CN111080447B (en) * 2019-12-02 2020-10-30 百望股份有限公司 Rotation method and system for neutral node in block chain system
CN111144866B (en) * 2019-12-25 2021-04-30 腾讯科技(深圳)有限公司 Data transfer method, device, node equipment and storage medium
CN111311179A (en) * 2020-02-07 2020-06-19 北京星选科技有限公司 Object processing method and device, electronic equipment and computer readable storage medium
CN111581290A (en) * 2020-05-09 2020-08-25 国网电子商务有限公司 Block chain-based violation operation data processing method and device
CN111340496B (en) * 2020-05-20 2020-10-27 南京如般量子科技有限公司 Block chain system and method for automatically optimizing historical transaction data
CN111857892B (en) * 2020-09-22 2020-12-18 支付宝(杭州)信息技术有限公司 Method and device for processing service through block chain
US10958450B1 (en) 2020-10-15 2021-03-23 ISARA Corporation Constructing a multiple-entity root certificate data block chain
CN112214552A (en) * 2020-11-05 2021-01-12 深圳市瀚兰区块链地产有限公司 Construction engineering construction intelligent contract execution method and device and electronic equipment
CN112330343A (en) * 2020-11-17 2021-02-05 北京三维天地科技股份有限公司 Medicine batch archive tracing system based on block chain
CN112597526A (en) * 2021-03-05 2021-04-02 浙江数秦科技有限公司 Security data access method for alliance chain

Family Cites Families (68)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1577816A3 (en) 1996-09-04 2006-08-02 Intertrust Technologies Corp. Trusted infrastructure support systems, methods and techniques for secure electronic commerce and rights management
US5924094A (en) * 1996-11-01 1999-07-13 Current Network Technologies Corporation Independent distributed database system
US6820202B1 (en) * 1998-11-09 2004-11-16 First Data Corporation Account authority digital signature (AADS) system
BR0005548A (en) 1999-03-24 2001-01-30 Avix Inc Process for displaying multicolored bitmap image data on a dot matrix type video screen, and video device that operates based on the display process
US6473794B1 (en) * 1999-05-27 2002-10-29 Accenture Llp System for establishing plan to test components of web based framework by displaying pictorial representation and conveying indicia coded components of existing network framework
EP1224627B1 (en) 1999-10-18 2016-07-06 Stamps.Com Security system for secure printing of value-bearing items
US7167844B1 (en) * 1999-12-22 2007-01-23 Accenture Llp Electronic menu document creator in a virtual financial environment
US20020111907A1 (en) 2000-01-26 2002-08-15 Ling Marvin T. Systems and methods for conducting electronic commerce transactions requiring micropayment
JP2001290866A (en) * 2000-04-05 2001-10-19 Iida Sangyo:Kk Management and inquiry system for construction progress state
US20020128917A1 (en) 2001-03-06 2002-09-12 Electronic Data Systems Corporation Method and apparatus for processing financial transactions
US7194543B2 (en) 2001-11-12 2007-03-20 Mci, Llc System and method for creating and managing survivable, service hosting networks
US20030191669A1 (en) * 2002-04-09 2003-10-09 Fitzgerald David System for providing consumer access to healthcare related information
ITRM20030341A1 (en) 2003-07-14 2005-01-15 Michele Giudilli Method for charging the costs of using content
US7135967B2 (en) 2003-08-01 2006-11-14 Spectrum Tracking Systems, Inc. Method for locating an asset
JP4460251B2 (en) * 2003-09-19 2010-05-12 株式会社エヌ・ティ・ティ・ドコモ Structured document signature apparatus, structured document adaptation apparatus, and structured document verification apparatus.
US7703140B2 (en) 2003-09-30 2010-04-20 Guardian Data Storage, Llc Method and system for securing digital assets using process-driven security policies
US20050091173A1 (en) 2003-10-24 2005-04-28 Nokia Corporation Method and system for content distribution
US7383231B2 (en) 2004-07-19 2008-06-03 Amazon Technologies, Inc. Performing automatically authorized programmatic transactions
US7324976B2 (en) 2004-07-19 2008-01-29 Amazon Technologies, Inc. Automatic authorization of programmatic transactions
US8347088B2 (en) 2005-02-01 2013-01-01 Newsilike Media Group, Inc Security systems and methods for use with structured and unstructured data
US7841010B2 (en) * 2007-01-08 2010-11-23 Apple Inc. Software or other information integrity verification using variable block length and selection
US8695089B2 (en) * 2007-03-30 2014-04-08 International Business Machines Corporation Method and system for resilient packet traceback in wireless mesh and sensor networks
EP2060053B1 (en) 2007-09-14 2017-03-29 Security First Corp. Systems and methods for managing cryptographic keys
US7676501B2 (en) 2008-03-22 2010-03-09 Wilson Kelce S Document integrity verification
US20090259547A1 (en) * 2008-04-11 2009-10-15 Brian Clopp Affiliate and cross promotion systems and methods
US7818256B1 (en) * 2008-11-20 2010-10-19 Citibank, N.A. Digital receipt for electronic data and methods and systems for generating same
CA2862080C (en) 2012-01-23 2020-08-18 Headwater Partners I Llc Service plan design, user interfaces, application programming interfaces, and device management
US9112862B2 (en) * 2009-02-02 2015-08-18 Adobe Systems Incorporated System and method for parts-based digital rights management
US8869299B2 (en) * 2009-03-04 2014-10-21 Titus Inc. Method and system for generating trusted security labels for electronic documents
WO2011002922A1 (en) 2009-06-30 2011-01-06 Secondmarket Holdings, Inc. Issuer-controlled market platform and system for restricted holdings and transaction management
US20150379510A1 (en) * 2012-07-10 2015-12-31 Stanley Benjamin Smith Method and system to use a block chain infrastructure and Smart Contracts to monetize data transactions involving changes to data included into a data supply chain.
US9350599B1 (en) * 2012-06-26 2016-05-24 Google Inc. User content access management and control
US10326678B2 (en) 2012-06-27 2019-06-18 Ubiquiti Networks, Inc. Method and apparatus for controlling power to an electrical load based on sensor data
JP2016502295A (en) * 2012-10-10 2016-01-21 レッド.コム,インコーポレイテッド Video distribution and playback
US8824772B2 (en) 2012-10-23 2014-09-02 Ensenta Inc. System and method for improved remote deposit image handling
US10600010B2 (en) * 2013-03-15 2020-03-24 The Board Of Trustees Of The Leland Stanford Junior University Systems and methods for generating scheduling options in consideration of elements within a construction site
US20140279694A1 (en) * 2013-03-15 2014-09-18 RePower Captial, Inc. Method and device for facilitating financing for projects
US20140297468A1 (en) * 2013-03-27 2014-10-02 Fraser Patterson Consumer Contractor Connector Apparatuses, Methods and Systems
AU2014262897B2 (en) 2013-05-04 2018-03-22 Christopher Decharms Mobile security technology
US20140344015A1 (en) 2013-05-20 2014-11-20 José Antonio Puértolas-Montañés Systems and methods enabling consumers to control and monetize their personal data
US20150046337A1 (en) 2013-08-06 2015-02-12 Chin-hao Hu Offline virtual currency transaction
US9710808B2 (en) 2013-09-16 2017-07-18 Igor V. SLEPININ Direct digital cash system and method
US9595034B2 (en) * 2013-10-25 2017-03-14 Stellenbosch University System and method for monitoring third party access to a restricted item
KR102152641B1 (en) 2013-10-31 2020-09-08 엘지전자 주식회사 Mobile robot
US9400739B2 (en) * 2013-11-01 2016-07-26 International Business Machines Corporation Capacity forecasting based on capacity policies and transactions
WO2015066511A1 (en) 2013-11-01 2015-05-07 Ncluud Corporation Determining identity of individuals using authenticators
US20150154527A1 (en) * 2013-11-29 2015-06-04 LaborVoices, Inc. Workplace information systems and methods for confidentially collecting, validating, analyzing and displaying information
US20150161541A1 (en) * 2013-12-06 2015-06-11 Bank Of America Corporation Processing and Routing Referrals
US20150220928A1 (en) 2014-01-31 2015-08-06 Robert Allen Platform for the purchase and sale of digital currency
US20150227890A1 (en) * 2014-02-07 2015-08-13 Kristin Kaye Bednarek Communications system and smart device apps supporting segmented order distributed distribution system
US20150371548A1 (en) 2014-06-18 2015-12-24 Gideon Samid Knowledge and network currency systems and payment procedures
US9397832B2 (en) 2014-08-27 2016-07-19 International Business Machines Corporation Shared data encryption and confidentiality
US9756834B2 (en) 2014-09-04 2017-09-12 Lisa Mary Forsythe Pet toy with edible and/or digestible components
US20160098723A1 (en) * 2014-10-01 2016-04-07 The Filing Cabinet, LLC System and method for block-chain verification of goods
US20160162897A1 (en) 2014-12-03 2016-06-09 The Filing Cabinet, LLC System and method for user authentication using crypto-currency transactions as access tokens
US20160164884A1 (en) * 2014-12-05 2016-06-09 Skuchain, Inc. Cryptographic verification of provenance in a supply chain
US9875458B2 (en) * 2014-12-27 2018-01-23 Trimble Inc. Tracking of built components by using ID tags
WO2016115620A1 (en) * 2015-01-19 2016-07-28 Royal Bank Of Canada Secure processing of electronic payments
CN107408245A (en) * 2015-02-27 2017-11-28 维萨国际服务协会 Utilize the trading signature of Asymmetric Cryptography
US9965628B2 (en) * 2015-03-02 2018-05-08 Dell Products Lp Device reporting and protection systems and methods using a secure distributed transactional ledger
WO2016164310A1 (en) 2015-04-05 2016-10-13 Digital Asset Holdings Digital asset intermediary electronic settlement platform
US10497066B2 (en) * 2015-04-30 2019-12-03 NetSuite Inc. System and methods for creating and using revenue arrangements for efficient revenue management
US20160342989A1 (en) 2015-05-21 2016-11-24 Mastercard International Incorporated Method and system for processing blockchain-based transactions on existing payment networks
WO2016200885A1 (en) * 2015-06-08 2016-12-15 Blockstream Corporation Cryptographically concealing amounts transacted on a ledger while preserving a network's ability to verify the transaction
US20170011460A1 (en) * 2015-07-09 2017-01-12 Ouisa, LLC Systems and methods for trading, clearing and settling securities transactions using blockchain technology
US20170046689A1 (en) 2015-07-14 2017-02-16 Fmr Llc Crypto Voting and Social Aggregating, Fractionally Efficient Transfer Guidance, Conditional Triggered Transaction, Datastructures, Apparatuses, Methods and Systems
WO2017069874A1 (en) * 2015-10-21 2017-04-27 Manifold Technology, Inc. Event synchronization systems and methods
US10013573B2 (en) 2015-12-16 2018-07-03 International Business Machines Corporation Personal ledger blockchain

Cited By (71)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11004147B1 (en) 2008-08-14 2021-05-11 Experian Information Solutions, Inc. Multi-bureau credit file freeze and unfreeze
US10909617B2 (en) 2010-03-24 2021-02-02 Consumerinfo.Com, Inc. Indirect monitoring and reporting of a user's credit data
US10535111B2 (en) * 2013-04-10 2020-01-14 The Proof Of Trust Limited Apparatus, code, methods and systems for providing proof of trust related to smart contracts
US20190122300A1 (en) * 2013-04-10 2019-04-25 Patrick Damien O'Brien Apparatus, code, methods and systems for providing proof of trust related to smart contracts
US20190139136A1 (en) * 2015-07-09 2019-05-09 Templum, Inc. Systems and methods for trading, clearing and settling securities transactions using blockchain technology
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
US10833843B1 (en) * 2015-12-03 2020-11-10 United Services Automobile Association (USAA0 Managing blockchain access
US10142347B2 (en) 2016-02-10 2018-11-27 Bank Of America Corporation System for centralized control of secure access to process data network
US10129238B2 (en) 2016-02-10 2018-11-13 Bank Of America Corporation System for control of secure access and communication with different process data networks with separate security features
US10762504B2 (en) 2016-02-22 2020-09-01 Bank Of America Corporation System for external secure access to process data network
US20170244757A1 (en) * 2016-02-22 2017-08-24 Bank Of America Corporation System for external validation of secure process transactions
US10135870B2 (en) * 2016-02-22 2018-11-20 Bank Of America Corporation System for external validation of secure process transactions
US9979718B2 (en) * 2016-05-11 2018-05-22 Bank Of America Corporation System for managing security and access to resource sub-components
US10356066B2 (en) 2016-05-23 2019-07-16 Accenture Global Solutions Limited Wrapped-up blockchain
US10110576B2 (en) 2016-05-23 2018-10-23 Accenture Global Solutions Limited Distributed key secret for rewritable blockchain
US10348707B2 (en) * 2016-05-23 2019-07-09 Accenture Global Solutions Limited Rewritable blockchain
US10305875B1 (en) 2016-05-23 2019-05-28 Accenture Global Solutions Limited Hybrid blockchain
US10623387B2 (en) 2016-05-23 2020-04-14 Accenture Global Solutions Limited Distributed key secret for rewritable blockchain
US10931441B2 (en) * 2016-08-19 2021-02-23 Advanced New Technologies Co., Ltd. Data storage, data check, and data linkage method and apparatus
US10880078B2 (en) * 2016-08-19 2020-12-29 Advanced New Technologies Co., Ltd. Data storage, data check, and data linkage method and apparatus
US10361869B2 (en) * 2016-08-23 2019-07-23 International Business Machines Corporation Event ledger
US10402796B2 (en) 2016-08-29 2019-09-03 Bank Of America Corporation Application life-cycle transition record recreation system
US20180218454A1 (en) * 2017-01-27 2018-08-02 Walmart Apollo, Llc Managing participation in a monitored system using blockchain technology
CN106952124A (en) * 2017-03-16 2017-07-14 北京牛链科技有限公司 Electronic bill management system and method based on distribution book keeping operation
CN107070896A (en) * 2017-03-20 2017-08-18 智牛股权投资基金(平潭)合伙企业(有限合伙) A kind of safe and efficient block chain customization login method and security hardening system
EP3379447A1 (en) * 2017-03-22 2018-09-26 Siemens Aktiengesellschaft Method and device for tamper-proof storing of information relating to object-specific measures
WO2018171949A1 (en) * 2017-03-22 2018-09-27 Siemens Aktiengesellschaft Method and apparatus for the tamper-proof storage of information about object-related measures
WO2018183099A1 (en) * 2017-03-29 2018-10-04 Alibaba Group Holding Limited Blockchain-based transaction processing method and apparatus
US10740763B2 (en) 2017-03-29 2020-08-11 Alibaba Group Holding Limited Blockchain-based transaction processing method and apparatus
US10740761B2 (en) 2017-03-29 2020-08-11 Alibaba Group Holding Limited Blockchain-based transaction processing method and apparatus
US10878423B2 (en) 2017-03-29 2020-12-29 Advanced New Technologies Co., Ltd. Blockchain-based transaction processing method and apparatus
CN108874890A (en) * 2017-05-16 2018-11-23 江峰 A kind of band can openly record the block catenary system of man-machine system
CN107197036A (en) * 2017-06-22 2017-09-22 广东网金控股股份有限公司 A kind of consistent processing method of information based on block chain and terminal
US10735183B1 (en) * 2017-06-30 2020-08-04 Experian Information Solutions, Inc. Symmetric encryption for private smart contracts among multiple parties in a private peer-to-peer network
EP3665696A4 (en) * 2017-08-08 2020-12-30 QuiO Technologies LLC Self-executing agents for gathering health information between trusted parties
US10404455B2 (en) 2017-09-01 2019-09-03 Accenture Global Solutions Limited Multiple-phase rewritable blockchain
US10296248B2 (en) 2017-09-01 2019-05-21 Accenture Global Solutions Limited Turn-control rewritable blockchain
CN107844710A (en) * 2017-09-26 2018-03-27 浙江大学 A kind of contract generation system and generation method
US10289716B1 (en) 2017-10-31 2019-05-14 International Business Machines Corporation Consistent reporting using blockchain
US10691678B2 (en) 2017-10-31 2020-06-23 International Business Machines Corporation Consistent reporting using blockchain
US20190149333A1 (en) * 2017-11-15 2019-05-16 International Business Machines Corporation Methods and systems for supporting fairness in secure computations
US10944566B2 (en) * 2017-11-15 2021-03-09 International Business Machines Corporation Methods and systems for supporting fairness in secure computations
WO2019100112A1 (en) * 2017-11-22 2019-05-31 Resolve Disputes Online Technology Limited A system, method, computer program and data signal for communicating and event based verification
US10789589B2 (en) * 2017-12-29 2020-09-29 Paypal, Inc. Dispute resolution cryptocurrency sidechain system
WO2019133800A1 (en) * 2017-12-29 2019-07-04 Paypal, Inc. Dispute resolution cryptocurrency sidechain system
US10887254B2 (en) * 2018-02-01 2021-01-05 Red Hat, Inc. Enterprise messaging using blockchain system
WO2019168633A1 (en) * 2018-02-28 2019-09-06 Intuit Inc. Method and system for overseeing execution of graph-based contracts using hash chains
CN108551437A (en) * 2018-03-13 2018-09-18 百度在线网络技术(北京)有限公司 Method and apparatus for authentication information
US10304062B1 (en) * 2018-03-23 2019-05-28 Td Professional Services, Llc Computer architecture incorporating blockchain based immutable audit ledger for compliance with data regulations
US10628833B2 (en) 2018-03-23 2020-04-21 Td Professional Services, Llc Computer architecture incorporating blockchain based immutable audit ledger for compliance with data regulations
US20190303445A1 (en) * 2018-03-29 2019-10-03 salesforce.com,inc Hybrid Cloud Chain Management of Centralized and Decentralized Data
US10901974B2 (en) * 2018-03-29 2021-01-26 Salesforce.Com, Inc. Hybrid cloud chain management of centralized and decentralized data
CN108667815A (en) * 2018-04-18 2018-10-16 价值互联(广州)信息技术有限公司 Block chain secret key encipher-decipher method, device and terminal based on bio-identification
US10382205B1 (en) * 2018-06-10 2019-08-13 Hajoon Ko Security system and method for using a blockchain service through privacy-aware blockchain arbitration server
US10834062B2 (en) 2018-06-20 2020-11-10 International Business Machines Corporation Unlinking ownership of successive asset transfers on a blockchain
EP3595241A1 (en) * 2018-07-13 2020-01-15 Kevin Kei Tuncer Distributed blockchain with delayed transaction
CN108985089A (en) * 2018-08-01 2018-12-11 清华大学 Internet data shared system
US20200074470A1 (en) * 2018-09-05 2020-03-05 International Business Machines Corporation Database configuration for asset transfers
WO2020068534A1 (en) * 2018-09-26 2020-04-02 Mastercard International Incorporated Method and system for dispute resolution in a public blockchain
US10958438B2 (en) 2018-10-31 2021-03-23 Advanced New Technologies Co., Ltd. Method, apparatus, and electronic device for blockchain-based recordkeeping
US10693643B2 (en) 2018-11-07 2020-06-23 Pitt Ohio Methods and systems for distributed cryptographically secured data validation
CN109542980A (en) * 2018-11-20 2019-03-29 北京磁云数字科技有限公司 A kind of data processing method, device, equipment and the medium of block chain
US10999270B2 (en) 2018-12-28 2021-05-04 Mox-SpeedChain, LLC Hybrid distributed network ecosystem using systemized blockchain reconciliation, preselected issuance and data operations loops, and reconciliation digital facilitators
US10958637B2 (en) 2018-12-28 2021-03-23 Mox-SpeedChain, LLC Preselected issuance and data operations loops in a hybrid distributed network ecosystem
WO2020142412A1 (en) * 2018-12-30 2020-07-09 Tunnel International Inc. Methods, devices, and systems for secure payments
WO2020215083A1 (en) * 2019-04-19 2020-10-22 Coinbase, Inc. Systems and methods for blockchain administration
WO2020242550A1 (en) * 2019-05-29 2020-12-03 Vivigie Inc Ensuring trust levels when using electronic currencies
US10992735B2 (en) 2019-07-22 2021-04-27 Bank Of America Corporation System for generating event-based linkages between distributed resources for tailored data access
CN110489980A (en) * 2019-07-22 2019-11-22 杭州凯腾互联网技术有限公司 A kind of credit asset processing system based on block chain
CN110490003A (en) * 2019-08-09 2019-11-22 杭州安存网络科技有限公司 User's trust data generation method, acquisition methods, apparatus and system
US11023604B1 (en) * 2020-03-09 2021-06-01 United Services Automobile Association (Usaa) Systems and methods to track, store, and manage events, rights and liabilities

Also Published As

Publication number Publication date
CA2948239A1 (en) 2017-05-10
CA2938530A1 (en) 2017-02-13
US10282711B2 (en) 2019-05-07
US20200118094A1 (en) 2020-04-16
US20190213564A1 (en) 2019-07-11
US10402793B2 (en) 2019-09-03
US20170046652A1 (en) 2017-02-16
CA2938758A1 (en) 2017-02-13
CA2938519A1 (en) 2017-02-13
US20170048216A1 (en) 2017-02-16
US20190347627A1 (en) 2019-11-14
US10552805B2 (en) 2020-02-04
US20190087792A1 (en) 2019-03-21
US20170046806A1 (en) 2017-02-16
CA2938754A1 (en) 2017-02-13
US20170046651A1 (en) 2017-02-16
US20170046638A1 (en) 2017-02-16
CA2948241A1 (en) 2017-05-10
US20170046709A1 (en) 2017-02-16
US20190340588A1 (en) 2019-11-07
US20170046694A1 (en) 2017-02-16
US10558955B2 (en) 2020-02-11
US10692054B2 (en) 2020-06-23
CA2938759A1 (en) 2017-02-13
US20170046664A1 (en) 2017-02-16
US10540641B2 (en) 2020-01-21
US20170046792A1 (en) 2017-02-16
US10163080B2 (en) 2018-12-25
US20170046526A1 (en) 2017-02-16
US20170046698A1 (en) 2017-02-16
US10824999B2 (en) 2020-11-03
US20170046799A1 (en) 2017-02-16
CA3080037A1 (en) 2017-02-13
CA2938756A1 (en) 2017-02-13
CA2948106A1 (en) 2017-05-09
CA3080037C (en) 2020-12-29
US10402792B2 (en) 2019-09-03
CA2938757A1 (en) 2017-02-13
CA2948116A1 (en) 2017-05-09

Similar Documents

Publication Publication Date Title
US10416966B2 (en) Data processing systems for identity validation of data subject access requests and related methods
US10938835B2 (en) Systems and methods for managing digital identities
Dagher et al. Ancile: Privacy-preserving framework for access control and interoperability of electronic health records using blockchain technology
US9992022B1 (en) Systems and methods for digital identity management and permission controls within distributed network nodes
CA3027741C (en) Blockchain systems and methods for user authentication
US10701054B2 (en) Systems, methods, and apparatuses for implementing super community and community sidechains with consent management for distributed ledger technologies in a cloud based computing environment
JP2019096339A (en) System and method for monitoring and controlling business information saved on cloud computing service (ccs), and encrypting business information for each document
RU2747947C2 (en) Systems and methods of personal identification and verification
US10558820B2 (en) System and method for maintaining a segregated database in a multiple distributed ledger system
US20170330180A1 (en) Method for using and revoking authentication information and blockchain-based server using the same
US20200145399A1 (en) System and Method for Identity Management
US20200167453A1 (en) System and Method for Identity Management
JP2018186550A (en) Delay data access
US10020942B2 (en) Token-based secure data management
US20200128355A1 (en) Blockchain systems and methods for confirming presence
US20190124146A1 (en) Systems and methods of blockchain platform for distributed applications
US9876803B2 (en) System and method for identity management
US9762553B2 (en) Systems and methods of secure data exchange
US10764254B2 (en) Systems and methods of secure data exchange
US10142113B2 (en) Identifying and maintaining secure communications
JP2020009500A (en) Data security service
CN108055352B (en) System and method for keychain synchronization
US10146947B1 (en) Systems and methods for generating and maintaining immutable digital meeting records within distributed network nodes
US20190236598A1 (en) Systems, methods, and apparatuses for implementing machine learning models for smart contracts using distributed ledger technologies in a cloud based computing environment
US10511964B1 (en) Switching mobile service provider using blockchain

Legal Events

Date Code Title Description
STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

AS Assignment

Owner name: THE TORONTO-DOMINION BANK, CANADA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HALDENBY, PERRY AARON JONES;LEE, JOHN JONG SUK;CHAN, PAUL MOH-WAH;AND OTHERS;SIGNING DATES FROM 20170116 TO 20170327;REEL/FRAME:050727/0364

STCB Information on status: application discontinuation

Free format text: FINAL REJECTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE AFTER FINAL ACTION FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STCB Information on status: application discontinuation

Free format text: FINAL REJECTION MAILED

STCV Information on status: appeal procedure

Free format text: NOTICE OF APPEAL FILED

STCV Information on status: appeal procedure

Free format text: NOTICE OF APPEAL FILED

STCV Information on status: appeal procedure

Free format text: APPEAL BRIEF (OR SUPPLEMENTAL BRIEF) ENTERED AND FORWARDED TO EXAMINER