Patent classifications
H04L63/12
System and techniques for digital data lineage verification
Disclosed are examples for providing functions to receive a media file to be stored in a media repository. In the examples, a location in the media repository may be assigned to the media file. A media file address in a blockchain platform may be assigned to the media file. Metadata including the assigned location in the media repository and the assigned media file address in the blockchain platform may be added to the media file. A media file hash value may be generated by applying a hash function to the media file including the metadata. The media file hash value may be included in a message and uploaded to the assigned media file address in the blockchain platform as a transaction in the blockchain. An indication that the media file is uploaded to the media repository may be delivered to a subscriber device from which the media file was received.
Blockchained media stored in a material exchange format file
Digital media that has been blockchained into a blockchain file format may be stored into a secondary file format like a Material eXchange Format (MXF) digital file by deconstructing the blockchain file and storing its subcomponent blockchain data and blockchain hash digests for each block within separate structures of the MXF digital file by generating a table for the blockchain hash digests that links to the blockchain data through data pointers. These separate structures of the MXF digital file are the generic container for a media file and a SDTI-CP (Serial Data Transport Interface—Content Package) compatible system item.
Pyramid construct with trusted score validation
Disclosed herein are systems and methods for decentralized data distribution by a database network system comprising a hierarchical blockchain model. The hierarchical blockchain model may comprise a quantum pyramid consensus to distribute data throughout the database network system in a decentralized and secure manner. The hierarchical construct may be built according to trusted scores calculated for the nodes of the network over their lifetime at the network.
Central trust hub for interconnectivity device registration and data provenance
Apparatus and method for device and data authentication in a computer network, such as but not limited to an IoT (Internet of Things) network. In some embodiments, a trust hub device is coupled to an interconnectivity device. The trust hub device includes a controller and non-volatile memory (NVM), and may be a network capable data storage device. The interconnectivity device is configured as an Internet of Things (IoT) or Operational Technology (OT) device, and includes a controller and a sensor. Data from the sensor are transferred from the interconnectivity device to the trust hub device. The trust hub device proceeds to attest a provenance of the data from the sensor to a remote entity associated with the interconnectivity device. The trust hub device includes a firewall to the external network, establishes a root of trust for the local interconnectivity device, and performs enrollment and signing services for the interconnectivity device.
Trustable product delivery with RFID and smart chip
Trustable delivery of a product uses a package with a printed label having a unique product ID, an RFID marker applied to the product that contains the ID, and a smart chip inside the product that contains the ID and a digital key. The ID from the RFID marker is compared to the label for initial validation of the package. The smart chip is further interrogated to generate an encoded value of the ID, such as a hash value, using the digital key. The hash value is then used to authenticate the ID, thereby verifying that the product as delivered is the original, untampered product. The product ID and the hash value are recorded in a blockchain ledger associated with the product. In this manner, the packaged product can be validated by any party in the delivery chain, e.g., manufacturer, seller, distributor, delivery service, and final recipient.
Method for personal data administration in a multi-actor environment
A method for personal data administration in a multi-actor environment is performed by a system that includes a data management process managed by a remote server. The system includes a user profile that is associated to a user PC device and includes a set of data management protocols and a user data registry. The system also includes a third-party account that is associated to an account ID and a third-party data registry. The method begins when a data transmission notification is received by the remote server. The remote server analyzes the notification to select an appropriate protocol from the data management protocols. The method then executes the data management protocol, makes a record of the interaction, and transmits an outgoing data packet to the third-party account. The method then monitors the outgoing data packet to determine if the user data contained therein has been transferred interacted or tampered with.
Systems, methods, and program products for depositing, holding and/or distributing collateral as a token in the form of digital assets on an underlying blockchain
The present invention relates to a method, system, and program product for depositing, holding and/or distributing collateral in the form of a stable value token for a security token, the tokens being on the same underlying blockchain. Furthermore, the present invention relates to methods, systems, and program products for lending digital assets, such as crypto currency and other related products.
PROJECT CREATION SYSTEM USING BLOCKCHAIN
An embodiment comprises methods of managing and systems for processing media projects. The project processing system comprises a memory circuit and a hardware processor configured to execute computer-executable instructions. The hardware processor executes the computer-executable instructions to identify a first dynamic structure associated with a first media project and determine that a first user is permitted to view and modify details regarding the first media project on the first dynamic structure. The hardware processor also executes the computer-executable instructions to create a first data block representing a first transaction by which the first user agrees to contribute at least one service, good, or fund to the first media project and broadcast the first data block to a distributed network for validation of one or more aspects of the first transaction. The hardware processor further executes the computer-executable instructions to append the first data block to the first dynamic structure based on the distributed network validating the one or more aspects of the first transaction and store, in the memory circuit, a copy of the first dynamic structure as appended with the first data block for future comparison and authentication.
SYSTEMS AND METHODS FOR VALIDATION OF POLICIES OF A SMART CONTRACT ON A CENTRALIZED OR DISTRIBUTED DIGITAL LEDGER
Systems and methods are described for policy-validated transactions using a centralized or distributed ledger. A request to execute a transaction and a transaction signature is received from a user's computing device. The transaction signature is generated with a private key of the user's computing device. The transaction corresponds to a token associated with the user's computing device and the transaction is subject to a first policy of a set of one or more policies. The transaction signature corresponds to the request to execute the transaction is determined using a public key of the user's computing device. In response to the determination, the token associated with the user's computing device is retrieved from the centralized or distributed ledger. The transaction is executed if the token is associated with the first policy and the token is valid.
ENDORSEMENT CLAIM IN A VERFIFIABLE CREDENTIAL
A first verifiable claim is received at a second entity from a first entity. The first verifiable claim is signed by the first entity. A second verifiable claim is generated. The second verifiable claim embeds the first verifiable claim therein and specifies a service that is to be performed on behalf of a fourth entity. The second verifiable claim is provided to a third entity. The second verifiable claim is configured to cause the third entity to verify the signature of the first entity with a public key associated with a decentralized identifier (DID) of the first entity to determine that the first entity is a trusted entity that is able to verify that the second entity is authorized to specify the service to be performed on behalf of the fourth entity.