Techniques for providing a digital certificate management for blockchain technologies are described. One example method includes a transaction request including a digital certificate is received from a certificate authority at a node in a blockchain network, and the transaction request is a request to write the digital certificate into a blockchain associated with the blockchain network, and the digital certificate is issued to a node in the blockchain network. A consensus verification result is determined for the transaction request, and the consensus verification result is produced by nodes in the blockchain network. The consensus verification result is compared to a predetermined threshold value. In response to determining the consensus verification result is greater than or equal to the predetermined threshold value, the digital certificate is stored in the blockchain associated with the blockchain network.

Techniques for providing a digital certificate management for blockchain technologies are described. One example method includes a transaction request including a digital certificate is received from a certificate authority at a node in a blockchain network, and the transaction request is a request to write the digital certificate into a blockchain associated with the blockchain network, and the digital certificate is issued to a node in the blockchain network. A consensus verification result is determined for the transaction request, and the consensus verification result is produced by nodes in the blockchain network. The consensus verification result is compared to a predetermined threshold value. In response to determining the consensus verification result is greater than or equal to the predetermined threshold value, the digital certificate is stored in the blockchain associated with the blockchain network.

Raw merchant data of real-time ISO transactions is enriched with normalized merchant data, including a normalized merchant name, a normalized merchant location, by transmitting the raw merchant data to an external resource and receiving the normalized raw merchant data from the external resource. An authorization request from a real-time ISO transaction concerning a specific mobile user can be initiated by a specific merchant device at a merchant location. A user location is obtained and utilized to identify enriched merchant data. It is the enriched merchant data that is used for deciding whether to approve or deny a transaction with more accuracy.

While mobile device location remains, private, user transaction controls are applied to a specific authorization request. The user transaction controls are pre-configured by the user of the mobile account holder device and identified by the enriched merchant data. Location algorithms predict transaction locations used to obtain enriched merchant data responsive to location privacy mode. Responsive to the user transaction controls, a fraud recommendation response is sent to the approval system, in real time with the transaction. The fraud recommendation response prevents a false negative by using an enriched merchant location rather than the raw merchant location.

A computer implemented method includes receiving, by a trusted execution environment (TEE) application, a cross-chain data request from a first blockchain node of a first blockchain; obtaining, by the TEE application, cross-chain data corresponding to the cross-chain data request from a second blockchain node of a second blockchain; verifying, by the TEE application, the cross-chain data; generating, by the TEE application, a signature using a private key of the TEE application, where a public key corresponding to the private key is stored in the first blockchain; and returning, by the TEE application, the cross-chain data and the signature to the first blockchain node.

A computer-implemented method includes receiving, by a first blockchain node, an encrypted transaction comprising a smart contract that includes code, wherein the code of the smart contract comprises a contract state indicated by a privacy identifier; decrypting, by the first blockchain node, the encrypted transaction to obtain the code of the smart contract in plaintext; executing, by the first blockchain node, the code of the smart contract in plaintext in a trusted execution environment; encrypting, by the first blockchain node using a key, the contract state indicated by the privacy identifier; and writing, by the first blockchain node, the encrypted contract state indicated by the privacy identifier to a database.

Disclosed herein are methods, systems, and apparatus, including computer programs encoded on computer storage media, for processing blockchain-based guarantee information. One of the methods includes receiving a cyphertext of a digital document specifying a guarantee from a first computing device associated with a first guarantor and one or more zero-knowledge proofs (ZKPs) related to one or more values associated with the guarantee; verifying that the one or more ZKPs are correct; upon verifying that the one or more ZKPs are correct, storing the cyphertext to a blockchain based on performing a consensus algorithm; receiving a first message from a second computing device associated with a beneficiary or a representative of the beneficiary, the first message including an acceptance of the guarantee by the beneficiary; and updating a status of the guarantee to indicate that the guarantee has been accepted by the beneficiary.

A computer-implemented method includes: determining assets held by a remitter, the assets to be spent in a remittance transaction between the remitter and one or more payees, in which each asset corresponds to a respective asset identifier, a respective asset amount, and a respective asset commitment value; determining a remitter pseudo public key and a remitter pseudo private key; determining a cover party pseudo public key, in which the cover party pseudo public key is obtained based on asset commitment values of assets held by the cover party; and generating a linkable ring signature for the remittance transaction.

Systems and methods are described for authorizing users and/or devices. An example method may comprise receiving, from a user device, a request to access a function associated with a service account. The request may comprise an identifier of the user device. The example method may comprise determining, based on the identifier, a primary authority holder of the service account. The example method may comprise determining that a first record on a first distributed ledger associated with the primary authority holder indicates that the user device is associated with the primary authority holder. The example method may comprise determining that a second record on a second distributed ledger associated with the user device indicates that the user device is associated with the primary authority holder. The example method may comprise granting, based on the request, the first record, and the second record, the user device access to the function.

A compute node currently operating within a given computing environment and currently enabled to support at least a first communication protocol obtains one or more instructions for enabling the compute node to support a second communication protocol. In response to the one or more instructions, one or more configuration parameters associated with the compute node are automatically reconfigured to support the second communication protocol. An automatic determination is made, in the given computing environment within which the compute node currently operates, whether or not to certify the compute node for the second communication protocol.