New pending patent applications are published by the USPTO on Thursdays. Both of today's Spotlight Applications continue the theme of blockchains (smart contracts, distributed ledgers) and rights management broadly construed. Assigned to Blockchain ASICS, the first application discloses techniques for dynamic transform in blockchain header validation. Assigned to Telefonica (ES), the second application discloses techniques for recovering cryptographic keys of a blockchain network.
20200228319, "Dynamic transform in blockchain header validation," assigned to Blockchain ASICS, Inc.
Integrated circuits, methods, and computer programs are directed to performing proof-of-work (POW) operations. One integrated circuit includes a nonce register for storing a nonce value, a first one-way function (OWF) circuit configured to generate a hash of a header, a dynamic transform circuit configured to transform the hash of the header to generate a transform value, and a second OWF circuit configured to generate a hash of the transform value to obtain a validation parameter. The header includes the nonce value for POW validation of the header. Further, the transformation by the dynamic transform circuit is based on the nonce value. The validation parameter determines whether the POW meets a predetermined target for validation of the header with the nonce value.
20200235921, "Method and system for recovering cryptographic keys of a blockchain network," assigned to Telefonica Digital Espana, S.L.U.
Method and system for recovering cryptographic keys of a blockchain network. A computing device or an element associated with the same has stored a pair of cryptographic keys representative of the identity of the user in a blockchain network, including a public key and a private key. An identity manager maintains a registry of the user in a distributed directory. When a request from the user is received due to the loss/theft of their private key, the information on the public key of the user is eliminated from the registry and the user is revoked as the owner of a smart contract, a new pair of keys is generated, stored in the device or in said element; and the user is identified and authenticated. Once correctly authenticated, the manager receives the new public key of the user, updates the registry and updates the ownership of the smart contract.