There is provided a method performed by a first entity of a network. Contextual information for the first entity and a timestamp for the contextual information is acquired (102). An authentication token is generated (104) using the acquired contextual information. Transmission of an authentication request message is initiated (106) towards a second entity of the network requesting authentication of the first entity with the second entity. The authentication request message comprises the generated authentication token and the timestamp for use in the authentication. An authentication response message indicative of whether authentication of the first entity with the second entity is successful or unsuccessful received (108).

Embodiments are directed to generating and training a distributed machine learning model using data received from a plurality of third parties using a distributed ledger system, such as a blockchain. As each third party submits data suitable for model training, the data submissions are recorded onto the distributed ledger. By traversing the ledger, the learning platform identifies what data has been submitted and by which parties, and trains a model using the submitted data. Each party is also able to remove their data from the learning platform, which is also reflected in the distributed ledger. The distributed ledger thus maintains a record of which parties submitted data, and which parties removed their data from the learning platform, allowing for different third parties to contribute data for model training, while retaining control over their submitted data by being able to remove their data from the learning platform.

Permissioned blockchains with off-chain storage establish integrity and no-later-than date-of-existence for documents, leveraging records containing hash values of documents. When a document's integrity or date is challenged, a new hash value is compared with a record in the blockchain. Proving date-of-existence (via hash value in a publication and/or SMS) for the block containing the record establishes no-later-than date-of-existence for the document. Permissioning monetizes operations, enforcing rules for submission rights and content, thereby precluding problematic material (privacy, obscenity, malicious logic, copyright violations) that threatens long-term viability. Compact records and off-chain storage in a document corral (with quarantine capability) preserve document confidentiality and ease storage burdens for distributed blockchain copies. Using multiple hash values for each document hardens against preimage attacks with quantum computing. Daisy chaining records establishes that relationships existed among documents at registration. Self-addressed blockchain registration (SABRe) permits documents to self-identify their blockchain record address (block ID, index).

A method for publishing a smart contract includes: generating a version number index value according to a contract name of the smart contract, and searching for an associated target contract version number from a blockchain network according to the version number index value; generating a contract index value according to a contract version number of the smart contract and the contract name, in response to determining that the contract version number of the smart contract is greater than the target contract version number; associating the contract index value with the smart contract and associating the version number index value with the contract version number of the smart contract, to generate transaction information; and publishing the transaction information to the blockchain network, to publish the smart contract to the blockchain network.

A blockchain-based data processing method and apparatus, a computer device, and a computer-readable storage medium. The method includes: obtaining a data authorization request transmitted by an authorization terminal, the data authorization request including a data authorization certificate associated with an authorizer; performing authorization verification on the authorizer according to the data authorization request to obtain a first verification result; signing the data authorization certificate according to a private key of a first blockchain in a case that the first verification result is a valid result to obtain a first certificate signature, determining the first certificate signature as a to-be-uploaded signature, and performing uploading on the data authorization certificate carrying the to-be-uploaded signature; and transmitting the data authorization certificate to a second blockchain, and providing a query permission to a query terminal in a case that signature verification on the to-be-uploaded signature by the second blockchain succeeds.

A system and a method for digital proof generation are provided. The system includes a data management module to manage dataset having plurality of data rows and a query execution and verification module including a commitment storage sub-module, a query execution sub-module and a result verification sub-module. The data management module receives query from the query execution sub-module, related to operation on data rows of plurality of data rows, which is processed to generate execution result associated with data rows. The execution result is transferred along with data rows to the query execution sub-module. A set of commitments associated with execution result is transferred to the commitment storage sub-module. The query execution sub-module transfers set of commitments, from the commitment storage sub-module, and data rows to the result verification sub-module for verification, and receives a verification result from the result verification sub-module.

A method for preventing a replay attack on a Segment Routing over Internet Protocol version 6 (SRv6) keyed hashed message authentication code (HMAC) verification. The method includes a network device receiving an SRv6 packet comprising anti-replay attack verification information. The network device performs anti-replay attack verification based on the anti-replay attack verification information. The network device performs HMAC hash computation on the SRv6 packet in response to the first SRv6 packet passing passes the anti-replay attack verification.

An example operation may include one or more of identifying a blockchain transaction requiring commitment processing for commitment to a blockchain, determining the blockchain transaction is delayed, responsive to identifying the blockchain transaction is delayed, creating a transaction acceleration smart contract defining an incentive for performing the commitment processing of the blockchain transaction, and storing the transaction acceleration smart contract blockchain in a different blockchain.

A set of security templates is maintained including first and second templates. The first template specifies time and location stamp authentication for a file, and contextual security conditions that must be met before the file can be accessed. The second template specifies the time and location stamp authentication, but not the contextual security conditions. One of the first or second security templates is applied to the particular file. When the second security template is applied, a GPS-crypto device adds a time and location stamp to the particular file. The particular file is signed using a private key associated with the GPS-crypto device to generate an authentication signature based on the time and location stamp. The authentication signature is added to the particular file to allow a recipient to verify the time and location stamp of the particular file using a public key corresponding to the private key.

The present disclosure provides systems, methods, and computer-readable storage media having functionality to prove immutability of blockchains without accessing user data. A user may submit data for storage to a data management server and the data management server may generate one or more data records corresponding to the data at a database and one or more blocks at a blockchain, each block corresponding to of the data records. Block information associated with the generated blocks may be transmitted to a remote computing device for storage at a database. Prior to storing the block information, the remote computing device may sign the data using a private key or other cryptographic technique. To validate a block, raw block information may be retrieved from the blockchain and compared to the signed block information. If the signed block information matches the raw block information, the block may be determined to be valid (e.g., unchanged).