Accenture Global Solutions Limited

Gsc Secrypt, LLC

Stevens Institute of Technology

Keyless Technologies Ltd

Giuseppe Ateniese

David Baurle Treat

Michael T Chiaramonte

Daniele Venturi

Bernardo Magri

Paolo Gasti

Jaroslav Sedenka

Andrea Carmignani

Fabian Eberle

Giuseppe Giordano

Luca Schiatti

John Velissarios

Andrea Maria Milazzo

Abdoulaye Faye

Fernando Perez-Cruz

Briland Hitaj

Angelo Massimo Perillo

Danilo Francati

Elena Yurievna Medvedeva

Maksim Aleksandrovich Pavlov

Ilya Aleksandrovich Trofimov

A system includes circuitry for rewriting blockchains in a non-tamper-evident or tamper-evident operation using a key secret held in portions by multiple individually untrusted parties. The blockchains may include a series of blocks secured by integrity codes that may prevent non-tamper-evident rewrites by non-trusted parties that are not in possession of the key secret or individually-untrusted parties in possession of only a portion of the key secret. In some cases, multiple individually-untrusted parties may combine their portions into the key secret. As a group, the multiple individually-untrusted parties may perform non-tamper-evident operation with respect to at least one integrity code within the blockchain.

Distributed key secret for rewritable blockchain

A system may provide blockchain-based storage node control for unified proof-of-storage interaction for off-chain data chunk storage. The system may include verification circuitry that may provide a challenge to a storage node to audit the storage status of a data chunk. The verification circuitry may obtain identities for the storage node and data chunk based on blockchain records. The verification circuitry may obtain a challenge answer from the storage node in response. The verification circuitry may analyze the challenge answer in view of a challenge key to confirm whether the storage node has possession of the data chunk. When the storage node has possession of the data chunk chain circuitry may add a verification record to the blockchain.

Cryptologic blockchain-based off-chain storage verification

Embodiments of the invention provide a system including a first logic module for receiving a data stream that includes at least one neural network configured to generate at least one first password sample based at least in part on at least a portion of the data stream. A second logic module can be operatively coupled to the first logic module to receive the first password sample and at least one input dataset including a second password sample. The system can perform calculations to distinguish between at least one password of the first password sample and at least one password of the second password sample. Further, the system can iteratively learn and produce a feedback dataset based on the calculations, where the feedback dataset is configured to be provided to the first logic module.

System and process for generating passwords or password guesses

Systems, methods, and computer-readable media for facilitating an authentication processing service are provided.

Authentication processing service

A system and method includes a blockchain operation stack which may control access to reading and writing operations for a blockchain. The blockchain operation stack may include a credential authority layer that may control permissions for profiles maintained by the credential authority layer. When the permissions are granted by the credential authority layer, a presentation layer may generate a display that may include information on the blockchain structure. Integrity outputs stored in a successor block may verify that a predecessor block has been rewritten and is valid. The presentation layer may provide tools to facilitate write layer operations to rewrite and append to the blockchain.

Blockchain operation stack for rewritable blockchain

A system includes circuitry for rewriting blockchains in a non-tamper-evident or tamper-evident operation by a trusted party during a rewrite-permissive phase. During a rewrite-embargoed phase, at least one trusted party with rewrite access during the rewrite-permissive phase may have rewrite access revoked. In some implementations, rewrite access may be implemented by controlling access to a key secret for the blockchain. In some cases, access to the key secret may be changed by deleting the key secret or by changing access permissions for a particular device.

Multiple-phase rewritable blockchain

A system includes circuitry for wrapping up blockchains into blockchain loops. A blockchain may include a series of blocks extending from an initial block to a terminal block. The circuitry may wrap-up the blockchain by storing an integrity output coding-consistent with the terminal block within the initial block. In some cases, when the terminal block and initial block include end blocks for the blockchain, wrapping-up the series may form a closed-loop.

Wrapped-up blockchain

A system includes circuitry for rewriting blockchains in a validity-preserving operation. In some cases, using a key secret held by a trusted party. In some cases, the blockchains may include a series of blocks secured integrity codes that may prevent non-tamper-evident rewrites by non-trusted parties that are not in possession of the key secret. In some cases, the key may allow valid but tamper-evident rewrites of the blockchain by trusted entities. In some cases, integrity outputs may be generated from the integrity codes based on the content of the previous blocks in the series such that attempts by untrusted parties to replace a block may be detected through coding-inconsistencies with other blocks.

Rewritable blockchain

A system includes circuitry for performing hybrid blockchain rewrites by trusted parties. The hybrid blockchain may include blocks with multiple parts. In some cases, the blocks may include a core part and a tertiary part. The system may include conditions for validity preserving and/or non-tamper-evident rewrites to the parts of the block. The conditions to support rewrites to the core part may be more stringent than the corresponding conditions to support rewrites to the tertiary part. In some cases, the core part may be write-locked.

Hybrid blockchain

A system includes circuitry for rewriting blockchains in a non-tamper-evident or tamper-evident operation by a selected trusted party during a rewrite-permissive phase for the selected trusted party. During a rewrite-embargoed phase for the selected trusted party, rewrite access may pass to at least one second trusted party in a turn-based scheme. In some implementations, rewrite access may be implemented by controlling access to combination of a turn-control key secret portion with respective key secret portions controlled the by the individual trusted parties. Using the access to combination with the turn-control key secret portion, the trusted parties may preform rewrites to the blockchain.

Turn-control rewritable blockchain

A system includes circuitry for rewriting blockchains in a non-tamper-evident or tamper-evident operation using a key secret held by a trusted party. The blockchains may include a series of blocks secured integrity codes that may prevent non-tamper-evident rewrites by non-trusted parties that are not in possession of the key secret. In some cases, the key may allow valid but tamper-evident rewrites of the blockchain by trusted entities. Integrity outputs may be generated from the integrity codes based on the content of the previous blocks in the series such that attempts by untrusted parties to replace a block may be detected through coding-inconsistencies with other blocks.

Growing community of inventors

Hoboken, NJ, United States of America

Giuseppe Ateniese