Abstract: A distributed processing system for transactions of digital assets includes autonomous agents that execute off-chain. Each agent has an encapsulation of state representing at least one digital asset and is configured to process transaction requests that modify the agent state. A proof aggregation layer prevents double spending of the digital assets. A consensus layer forms a decentralized trust anchor that maintains a blockchain and certifies state transitions of the proof aggregation layer. A sending agent issues a request to certify that a particular asset state has not been previously spent and if the proof aggregation layer returns a uniqueness attestation, a recipient agent can use it to verify both correctness of the transaction execution, and validity of the uniqueness attestation. Transaction execution may take place off-chain at the agents without reliance on global consensus or shared state among all network participants.

Abstract: Exclusive ownership of data units, such as monetary units, is transferred by inputting a request from a transferor, to transfer to a transferee at least a designated one of the data units, said request including an identifier of the transferor, an identifier of the designated data unit, and an identifier of a transferee. The identifier of the transferor is verified and the absence of any other request to transfer the designated data unit during an update period is confirmed. A designation of ownership of the designated data unit is then changed from the transferor to the transferee in a ledger, which is comprised of a group of subledgers, each configured as a blockchain. Ownership is thereby processed per-unit instead of per-account.

Abstract: Exclusive ownership of data units, such as monetary units, is transferred by inputting a request from a transferor, to transfer to a transferee at least a designated one of the data units, said request including an identifier of the transferor, an identifier of the designated data unit, and an identifier of a transferee. The identifier of the transferor is verified and the absence of any other request to transfer the designated data unit is confirmed. A designation of ownership of the designated data unit is then changed from the transferor to the transferee in a ledger, which is comprised of a group of subledgers, each configured as a blockchain.

Abstract: Exclusive ownership of data units, such as monetary units, is transferred by inputting a request from a transferor, to transfer to a transferee at least a designated one of the data units, said request including an identifier of the transferor, an identifier of the designated data unit, and an identifier of a transferee. The identifier of the transferor is verified and the absence of any other request to transfer the designated data unit is confirmed. A designation of ownership of the designated data unit is then changed from the transferor to the transferee in a ledger, which is comprised of a group of subledgers, each configured as a blockchain.

Abstract: Exclusive ownership of data units, such as monetary units, is transferred by inputting a request from a transferor, to transfer to a transferee at least a designated one of the data units, said request including an identifier of the transferor, an identifier of the designated data unit, and an identifier of a transferee. The identifier of the transferor is verified and the absence of any other request to transfer the designated data unit during an update period is confirmed. A designation of ownership of the designated data unit is then changed from the transferor to the transferee in a ledger, which is comprised of a group of subledgers, each configured as a blockchain. Ownership is thereby processed per-unit instead of per-account.

Abstract: At least one node in a distributed hash tree verification infrastructure is augmented with an identifier of an entity in a registration path. A data signature, which includes parameters for recomputation of a verifying value, and which is associated with a digital input record, will therefore also include data that identifies at least one entity in the hash tree path used for its initial registration in the infrastructure. An uppermost value of the hash tree verification infrastructure is entered as, or as part of, a transaction in a blockchain.

Abstract: At least one node in a distributed hash tree verification infrastructure is augmented with an identifier of an entity in a registration path. A data signature, which includes parameters for recomputation of a verifying value, and which is associated with a digital input record, will therefore also include data that identifies at least one entity in the hash tree path used for its initial registration in the infrastructure. An uppermost value of the hash tree verification infrastructure is entered as, or as part of, a transaction in a blockchain.

Abstract: Occurrence of an event is detected within a device such as a computer, a communications device, a machine or process component. A non-deterministic time value (NDT) is requested for and associated with the detected event. Each NDT value is generated as a function of a calendar value created at time intervals as a root hash value of a distributed, hash-tree document authentication infrastructure.

Abstract: A code is added as a marking to a document and encodes an identifier that maps to a copy of the document stored in a database. Database copies of stored documents are preferably digitally signed. Using a device such as a smart phone, a user may extract the document identifier from the marking on a purported authentic version of the document and retrieve a copy of the document from the corresponding location in the database. The user can then visually compare the purported authentic version of the document with the retrieved database copy.

Abstract: A non-deterministic time value (NDT) is generated as a function of a calendar value created at time intervals as a root hash value of a distributed, hash-tree document authentication infrastructure. A clock displays the NDT value, which it may derive from a sub-set of the calendar value, and presents the NDT to a user in either visual or audible form, or both. may be presented to is presented may also be generated simply for display by a clock, for example as an NDT time zone.

Abstract: A capture device such as a camera and/or sound recorder records an event, which includes a visual and/or audible presentation of a time value that is non-deterministic, yet a function of physical time. The non-deterministic time value (NDT) may be generated as a function of a calendar value created at time intervals as a root hash value of a distributed, hash-tree document authentication infrastructure. If the NDT value included in the recording of the event does not match the NDT value corresponding to the calendar value from which it was generated, the recording may be assumed to be altered. Digital time-stamping may be included for the recording of the event to reduce the opportunity for back-dating of the recording. NDT may also be generated simply for display by a clock, for example as an NDT time zone.

Abstract: A capture device such as a camera and/or sound recorder records an event, which includes a visual and/or audible presentation of a time value that is non-deterministic, yet a function of physical time. The non-deterministic time value (NDT) may be generated as a function of a calendar value created at time intervals as a root hash value of a distributed, hash-tree document authentication infrastructure. If the NDT value included in the recording of the event does not match the NDT value corresponding to the calendar value from which it was generated, the recording may be assumed to be altered. Digital time-stamping may be included for the recording of the event to reduce the opportunity for back-dating of the recording. NDT may also be generated simply for display by a clock, for example as an NDT time zone.

Abstract: A code is added as a marking to a document and encodes an identifier that maps to a copy of the document stored in a database. Database copies of stored documents are preferably digitally signed. Using a device such as a smart phone, a user may extract the document identifier from the marking on a purported authentic version of the document and retrieve a copy of the document from the corresponding location in the database. The user can then visually compare the purported authentic version of the document with the retrieved database copy.