Resumen de: WO2026039126A1
Systems and methods for securely accessing information pertaining to an upstream entity using a verifiable credential with an embedded distributed identifier includes generating an authorization request for access to the information by a downstream entity. The authorization request includes a decentralized identifier associated with the downstream entity and is transmitted to a content storage entity. An authorization notification corresponding to the authorization request is received. An authorization token is retrieved. The authorization token includes a verifiable credential generated by the upstream entity and incorporating the decentralized identifier. A request transaction including a request to access the information pertaining to the upstream entity and the authorization token is generated and transmitted to the content storage entity. A verification challenge corresponding to the request transaction based on the verifiable credential is received and a response is transmitted. A reply transaction is received granting access to the information pertaining to the upstream entity.
Resumen de: WO2024224051A1
A computer-implemented method of processing a blockchain transaction request comprises receiving (2014; 3014; 4012) a blockchain transaction request and directing (2020; 3020; 4020) the blockchain transaction request to a specific node of a blockchain. The specific node interrupts (2030) execution of the blockchain transaction request, and directly or indirectly performs (2046) at least one service in relation to the blockchain transaction request.
Resumen de: EP4697174A1
This application provides a data management method, and the method includes: A client receives a backup plan configured by a user for to-be-backed-up data; the client divides the to-be-backed-up data into c data blocks based on a quantity of cloud nodes used for backup and a quantity of backup copies, and stores the c data blocks in n cloud nodes on multi-cloud platforms in a distributed manner, where for at least one data block in the c data blocks, the multi-cloud platforms store b backup copies of the at least one data block; and the client provides, for a blockchain network, metadata of the data stored on the multi-cloud platforms, so that the blockchain network encodes the metadata into a backup identifier, and stores the backup identifier, where the backup identifier is used to address the data stored on the multi-cloud platforms. In this method, cloud-chain convergence is performed with reference to features of the blockchain network of being decentralized, secure, and reliable, to improve security of multi-cloud backup data and eliminate a single-point security bottleneck in a conventional method.
Resumen de: CN120981828A
The blockchain system is capable of participating in distributed transactions using a two-stage commit protocol ("2PC"). In a 2PC, a computer system, such as a DBMS or blockchain system, submits transactions that change data (e.g., database, world state) using two stages. To participate in a distributed transaction using a 2PC, a blockchain system performs a "staged transaction". The staged transaction passes through a 2PC stage. In the preparation stage, the new value of the world state record is temporarily stored in the stage record as a stage value. In a second stage, if a distributed transaction is to be submitted, a world stage record is set to a stage value.
Nº publicación: GB2643423A 18/02/2026
Solicitante:
NCHAIN LICENSING AG [CH]
nChain Licensing AG
Resumen de: GB2643423A
Methods are disclosed whereby a coordinating party generates a first blockchain transaction that is configured to verify that a second blockchain transaction supplied to the first transaction contains at least two data values, and consequently release an amount of a digital asset. The first data value is generated by a first party digitally signing a first message. Similarly, the second data value is generated by a second party digitally signing a second message. The second party must have knowledge of both the first and second data values to generate the second transaction, with the first data value, along with a blockchain transaction template, sent by the first party to the second party. The method can be used as a VAT automation protocol, with VAT sent directly to HMRC