(19) *EP003793130A1*

(11) EP 3 793 130 A1

(12) EUROPEAN PATENT APPLICATION

(43) Date of publication: (51) Int Cl.: 17.03.2021 Bulletin 2021/11 H04L 9/32 (2006.01) H04L 9/08 (2006.01)

(21) Application number: 19197425.2

(22) Date of filing: 14.09.2019

(84) Designated Contracting States: (71) Applicant: Ethernity Hodl UG AL AT BE BG CH CY CZ DE DK EE ES FI FR GB 83671 Benediktbeuern Bayern (DE) GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR (72) Inventors: Designated Extension States: • The inventor has waived his right to be thus BA ME mentioned. Designated Validation States: KH MA MD TN

(27) Previously filed application: 09.10.2018 EP 18199471

(54) SECURE DECENTRALIZED WITH PRIVACY CONTROLS

(57) It is an object of the invention to provide a de- monly referred as technology, to record meta- centralized cloud computing system which protects data data about each cloud computing service request and privacy while user’s data is being transferred, stored or each cloud service provider offer. Using cryptographic processed within the ecosystem. Currently, cloud com- methods, the data is protected while in transit and at rest puting users have to trust their cloud computing provider when is transferred from the user to the service provider. in regard to how their private data is handled. Moreover, Using trusted execution environment technology, an en- usually there is no way to verify technically how the data clave is used to protect data privacy while it is being proc- was processed without a very complicated process. The essed by the service provider. invention leverages distributed ledger technology, com- EP 3 793 130 A1

Printed by Jouve, 75001 PARIS (FR) 1 EP 3 793 130 A1 2

Description steps, but not the exclusion of any other element, integer or step, or group of elements, integers or steps. TECHNICAL FIELD SUMMARY [0001] The disclosed relates to blockchain technology, 5 security mechanisms, and cloud computing infrastruc- [0009] Embodiments of the invention may comprise a ture. It is particularly suited for use as a mechanism of method and corresponding system operating a decen- securing execution in a decentralized cloud in- tralized cloud infrastructure that safeguard the user’s pri- frastructure spread across a plurality of computing de- vacy and the software payload’s confidentiality, integrity vices while enforcing the three principles of information 10 and availability while is being executed by the payload security: confidentiality, integrity, availability processor. [0010] One embodiment may comprise one or more BACKGROUND blockchain solutions which store users requests for serv- ice as well as payload processors service offers and their [0002] In this document we use the term "blockchain 15 associated metadata. The user’s requests and payload solution" to refer to a system comprising a distributed processor’s offers are compared and when matches are ledger, the software that operates the data on the distrib- found, the software payload may be securely transferred uted ledger, a plurality of devices that share the ledger to the one or more payload processors and executed. information and/or operate the data on the distributed [0011] One or more embodiments may comprise cryp- ledger via operations referred as blockchain transac- 20 tographic methods or other computer-implemented tions. methods that may enforce the requesting user’s privacy [0003] In this document we use the term "software pay- controls and may also enforce the requested security load" to refer to a software process and its related infor- controls that safeguard software payload’s confidential- mation which may comprise the data stored on a com- ity, integrity and availability while a payload processor is puting device storage, the data stored in a computing 25 providing the requested services. device memory, the data that is being transmitted over [0012] The invention may be described as a security a communication network and the data that is being re- method/system for securing a software payload integrity ceived over a communication network. when executed in a decentralized manner. The invention [0004] In this document we use the term "payload proc- may be described as a method/system for securing a essor" to refer to an entity that processes software pay- 30 software payload confidentiality when executed in a de- loads acting as a what is commonly referred as, a cloud centralized manner. service provider. Hereafter, the term "hypervisor soft- [0013] The invention may be described as a meth- ware" refers to a computer program, software, or soft- od/system for securing a software payload availability ware module ran by the payload processor to interact when executed in a decentralized manner. The invention with the blockchain solution. 35 may be described as a method/system for securing us- [0005] Decentralized cloud computing refers to an in- er’s privacy when executing a software payload in a de- formation processing technology that enables users to centralized manner. execute a software payload without having to provide, [0014] Other embodiments of the invention may in- maintain or manipulate, an underlying hardware infra- clude a software component, module, plug-in or exten- structure, regardless of the identity of the payload proc- 40 sion for the hypervisor software. Other embodiments of essor performing the software execution. the invention may include a device running the hypervisor [0006] In contrast to the regular cloud, the software software and the hypervisor software. execution requests are not honored by a specific payload processor and instead the payload processor is deter- BRIEF DESCRIPTION OF DRAWINGS mined automatically and most likely it is determined by 45 the blockchain solution based on predefined rules, com- [0015] monly known as a "smart contract". [0007] Any discussion of documents, acts, materials, Fig. 1 Depicts a cloud computing ecosystem accord- devices, articles or the like which have been included in ing to an embodiment of the present invention the present specification is not to be taken as an admis- 50 sion that any or all of these matters from part of the prior Fig. 2 Depicts a cloud computing payload processor art base or where common general knowledge in the field node (hardware) with integrated storage according relevant to the present disclosure as it existed before the to an embodiment of the present invention priority date of each claim on this application. [0008] Throughout this specification the word "com- 55 Fig. 3 Depicts a cloud computing payload processor prise", or variations such as "comprises" or "comprising", node (hardware) with external storage according to will be understood to imply the inclusion of a stated ele- an embodiment of the present invention ment, integer or step, or group of elements, integers or

2 3 EP 3 793 130 A1 4

Fig. 4 Is a flow diagram of a process being performed MEANS FOR SOLVING THE PROBLEM by the user at the blockchain level to maintain soft- ware payload confidentiality. [0022] Using the system the users have the possibility to automatically encrypt and anonymize their data while Fig. 5 Is a flow diagram of a process being performed 5 in transit. Acting this way, the system ensures confiden- by payload processor at the blockchain level to main- tiality of the software payload. tain software payload confidentiality. [0023] Using the system the users have the possibility to automatically encrypt their data while at rest and pre- Fig. 6 Is a flow diagram of a process being performed vent the payload processors from accessing or tampering to keep software payload integrity when uploading 10 their data by remotely controlling the unlocking of the data. virtual machine storage at boot time. Acting this way, the system ensures confidentiality of the software payload. Fig. 7 Is a flow diagram of a processes being per- [0024] Using the system the users have the possibility formed for validating software payload integrity. to automatically validate file integrity when their software 15 payload is being transferred and executed. This possible DETAILED DESCRIPTION by allowing cryptographic hashes to be associated with distributed ledger transactions. Acting this way, the sys- [0016] In the prior art decentralized cloud user’s appli- tem ensures integrity of the software payload. cations and data are being transferred to a most likely [0025] Using the system the users have the possibility unknown payload processor hardware. On the payload 20 to automatically load balance their software payload be- processor hardware, a virtual container or a virtual ma- tween multiple payload processors. This is possible by chine is being provisioned automatically and the user’s associating multiple instances of the same software pay- data is transferred on it and then the software runs ac- load to a distributed ledger transaction. Acting this way, cording to user’s preferences. the system ensures increased availability of the software [0017] Most of the cloud computing platforms offer en- 25 payload. cryption possibilities for the virtual storage, however the locking and unlocking operations are performed locally, OVERVIEW OF THE SYSTEM therefore these operations are in control of the payload processor. [0026] Fig. 1 illustrates one embodiment which may [0018] Due to the decentralized nature of the system, 30 comprise a user (17), a primary blockchain solution (1), it is very difficult to control or to restrict the bad actors multiple payload processors (2, 3, 4) running hypervisor operating as payload processors. Anyone can become software and several software payloads (5, 6, 7, 8, 9, 10, a payload processor and make their computing resourc- 11, 12, 13). This embodiment may comprise additional es available for exploitable users. These bad actors have blockchain solutions that interact privately with specific full access to see all the data that is stored on their hard- 35 software payloads: solution (14) interacts ware, including but not limited to: database passwords, with software payloads (5, 8, 11); blockchains solution administrative passwords hashes, SSL private keys. (15) interacts with software payloads (6, 9, 12); block- [0019] Moreover, a bad actor operating as a payload chains solution (16) interacts with software payloads (7, processor can modify user’s data and introduce viruses 10, 13); or malware as there is no security mechanism in place 40 [0027] One embodiment may allow users create soft- preventing them from doing so. In addition to this issue, ware payload processing requests which may comprise the bad actors can act as man in the middle and snoop hardware requirements (CPU, Memory, Storage), soft- on the connections and the network activity of the network ware requirements (software payload), cryptographic users using common sniffing techniques. keys and hashes, other metadata. Other metadata may [0020] Taking the above into account, is it possible to 45 comprise duration, price, location, hypervisor specific easily understand how dangerous the decentralized technologies. This information is stored on a distributed cloud computing is without the right security and privacy ledger to be processed by the blockchain solution. controls in place. [0028] One embodiment may allow payload proces- [0021] The present invention has made a view on such sors to create processing offers which may comprise a point and it is a technical object of the invention to pro- 50 available hardware, cryptographic keys and hashes, oth- vide a system that makes use of a smart contract design er metadata. Other metadata may comprise duration, and a software module design that integrates with most price, location, hypervisor specific technologies. This in- of the cloud computing platforms. The smart contract and formation is stored on a distributed ledger to be proc- the software module work together to allow cloud com- essed by the blockchain solution. puting users to make use of additional cryptographic keys 55 [0029] One embodiment may allow users and payload associated with their distributed ledger transactions. processors to match payload processing requests and offers and create a binding distributed ledger contract that instructs the payload processor to provide the serv-

3 5 EP 3 793 130 A1 6 ices as described in the payload processing request. Be- integrity procedure 300 is being performed. fore, after or during the payload processing one or more [0038] In a block 105 a user generates a cryptographic cryptocurrency transactions occur according to prede- key pair used for Open Authentication (OATH) Chal- fined rules. lenge-Response Algorithm (OCRA). Besides OCRA, the [0030] One or more embodiments may be using net- 5 key pair is also used to exchange cryptographic messag- work anonymizing technology like / or similar, to es using the blockchain solution. communicate with the blockchain solution, the hypervisor [0039] In a block 106 a user stores on a blockchain software or the software payloads. Acting this way, the solution an operational request such as "start" or "stop" system maintains the user’s privacy. which instructs the payload processor to perform such [0031] One embodiment may allow additional software 10 commands on the software payload. Also, in the same payloads to be ran by the payload processor, without block a user stores the public key of the key pair gener- matching a specific software payload processing re- ated at block 105 using the blockchain solution, as well quest. These payloads may have roles necessary to as other associated metadata. maintain the performance, availability and legal status of [0040] In a block 107 a user reads into the blockchain the whole decentralized cloud system. 15 solution in attempt to find a reply from the payload proc- essor. The reply contains the payload processor public HARDWARE DESCRIPTION key. [0041] In a decision block 108 is determined if such [0032] Fig. 2 and Fig. 3 illustrate another embodiment, reply exists. If not, the blockchain solution is checked a hardware appliance (1) part of the invention comprising 20 once more in a do-while style loop. If a matching reply a processing unit (2), and one or more memory chips (3). exists, then in a block 109 a user computes an OCRA This embodiment may additionally comprise internal client challenge, encrypts it using the payload processor storage Fig. 2 (4) and external storage Fig. 3 (4), a net- public key and stores it using the blockchain. work interface Fig. 2 (5), an external wireless network [0042] In a block 110 a user reads into the blockchain interface Fig. 3 (5), an alphanumerical input device (6), 25 solution in attempt to find a reply from the payload proc- a pointer input device (7), a monitor (8) and any associ- essor. The reply contains an OCRA server response and ated electronic parts for the components to function to- an OCRA server challenge. The private key generated gether. at block 105 will be used to decrypt the data in the reply. [0043] In a decision block 111 is determined if such SOFTWARE PAYLOAD CONFIDENTIALITY 30 reply exists. If not, the blockchains solution is checked once more in a do-while style loop. If a matching reply [0033] The software payload is encrypted before being exists, then in a decision block 112 is determined if the transferred to the payload processor. The payload proc- OCRA server response is valid. essor needs to be able to decrypt and run the software [0044] In a block 112 a user checks if the OCRA server payload on demand. The user can decrypt the data re- 35 response is cryptographically valid. If is invalid, the proc- motely using OCRA (OAUTH Challenge-Response Al- ess ends. If the server response is valid, in a block 113 gorithms) or similar authentication mechanisms. a user is computing the client response. [0034] Fig. 4 illustrates a flow diagram of a procedure [0045] In a block 114 a user is encrypting the DEK us- 100 which uses the distributed ledger as intermediary for ing the client response as Key Encryption Key (KEK). In the OCRA Multi Challenge-Response using dual key. 40 a block 115 a user is encrypting a reply using the payload This ensures additional level of audit trails and may be processor public key and stores it using the blockchain used as part of one or more embodiments. This process solution. The reply contains the KEK and the client re- is performed by the requesting user using a software pro- sponse. gram part of the blockchains solution. [0046] In a block 116 a user reads into the blockchain [0035] Fig. 5 illustrates a flow diagram of a procedure 45 solution in attempt to find a reply from the payload proc- 200 which may use the distributed ledger as intermediary essor. The reply contains the result of the requested op- for the OCRA Multi Challenge-Response using dual key. eration which can be a confirmation, a rejection or an This ensures additional level of audit trails and may be error. The user decrypts the reply data using the private used as part of one or more embodiments. This process key generated at block 105. is performed by the payload processor. 50 [0047] In a decision block 117 is determined if such [0036] In a block 102 a user generates a data encryp- reply exists. If not, the blockchains solution is checked tion key (DEK) using a cryptographic algorithm such as once more in a do-while style loop. If the reply containing AES 128/ AES 256 or similar. In a block 103 the user the operational request result exists, then the process is encrypts its software payload using the generated DEK. ended. [0037] In a block 104 a user uploads the encrypted 55 [0048] In a block 202 a payload processor checks the payload to cloud storage. The cloud storage can be a blockchain solution for an operation request such as regular cloud storage or a decentralized cloud storage "start" or "stop", a related public key, and the associated such as ipfs or similar. In this block the software payload metadata.

4 7 EP 3 793 130 A1 8

[0049] In a decision block 203 is determined if such the user’s public key, then stores it using the blockchain request exists. If not, the blockchain solution is checked solution. once more in a do-while style loop. If a matching request [0061] In a decision block 216 a payload processor de- exists, in a block 204 a payload processor downloads termines the result of the requested operation. If the result the encrypted software payload and checks the encrypt- 5 is unsuccessful, in a block 218 a payload processor com- ed software payload integrity using procedure 400. putes a reply containing a error message using the user’s [0050] In a block 205 a payload processor generates public key, then stores it using the blockchain solution. a cryptographic key pair used for Open Authentication [0062] One or more embodiments may use various (OATH) Challenge-Response Algorithm (OCRA). Be- cryptographic methods to encrypt the software payload sides OCRA, the key pair is also used to exchange cryp- 10 before, during or after it is being uploaded to be proc- tographic messages using the blockchain solution. essed by the payload processor. The system may store [0051] In a block 206 a payload processor creates a related data on the distributed ledger to establish identity, reply comprising the public key generated at block 205 maintain trust and preserve confidentiality while commu- and stores it using the blockchain solution. nicating with the payload processor. [0052] In a block 207 a payload processor reads into 15 the blockchain solution in attempt to find a reply from the SOFTWARE PAYLOAD INTEGRITY user. The reply contains an encrypted OCRA client chal- lenge. The data from the reply is decrypted using the [0063] Because the software payload is being trans- private key generated at block 205. ferred across the between unknown parties, the [0053] In a decision block 208 is determined if such 20 payload processor must validate the integrity of the soft- reply exists. If not, the blockchain solution is checked ware payload before executing it. This may be performed once more in a do-while style loop. If a matching reply by the payload processor before decryption and after de- exists, then in a block 209 a payload processor computes cryption. an OCRA server response and an OCRA server chal- [0064] Fig. 6 and Fig. 7 illustrate a flow diagram of two lenge. 25 process 300 and 400 which may use the distributed ledg- [0054] Afterwards in block 209, a payload processor er for storing file hashes that can be validated at various encrypts the OCRA server response and the OCRA serv- levels during payload execution. The user stores within er challenge using the user’s public key and stores the the distributed ledger transaction several hashes that can result using the blockchain solution. be checked against by the payload processor before or [0055] In a block 210 a payload processor reads into 30 during the execution of the software payload. the blockchain solution in attempt to find a reply from the [0065] In a block 302 a user calculates the hash of the user. The replay contains and encrypted client response encrypted software payload using a hash function such and a encrypted DEK. The data from the reply is decrypt- as SHA256/SHA512 or similar. In block 303 a user up- ed using the private key generated at block 205. loads the data to the cloud. The cloud storage can be [0056] In decision block 211 is determined if such reply 35 regular cloud storage or preferably decentralized storage exists. If not, the blockchain solution is checked once such as ipfs, sia, storj or similar. more in a do-while style loop. If a matching reply exists, [0066] In a block 304 a user stores the location of the then in a decision block 212 is determined if the OCRA data, the hash of the data and other related metadata client response is valid. using a blockchain solution. [0057] In a decision block 212 a payload processor de- 40 [0067] In a block 402 a payload processor reads from termines if the OCRA client response is valid. If is invalid, a blockchain solution the encrypted software payload lo- in a block 219 a payload processor computes a rejection cation, the encrypted payload hash and the associated message, encrypts it using the user’s public key and metadata. In a block 403 a payload processor downloads stores it using the blockchain solution. the software payload from the cloud storage. [0058] In a decision block 212 a payload processor de- 45 [0068] In a block 404 a payload processor calculates termines if the OCRA client response is valid. If is valid, the cryptographic hash of the downloaded software pay- in a block 213 a payload processor decrypts the DEK load. In a decision block 405 a payload processor checks and stores it in a cryptographic vault using in a protected the calculated data against the hash information read space that cannot be accessed in any way by the payload from the blockchain. If the information does not match, processor outside the hypervisor software process. 50 another download is attempted, and the check is per- [0059] In a block 214, a payload processor, using the formed once again in a do-while style loop. If the infor- hypervisor software, decrypts the software payload. In a mation matches, the process ends. block 215 a payload processor performs the requested [0069] One or more embodiments may validate the operation on the decrypted software payload. software payload integrity by using the information on [0060] In a decision block 216 a payload processor de- 55 the distributed ledger, and this allows multiple software termines the result of the requested operation. If the result payloads to be part of one another, therefore providing is successful, in a block 217 a payload processor com- integrity validations at different levels of payload execu- putes a reply containing a confirmation message using tion.

5 9 EP 3 793 130 A1 10

[0070] One or more embodiments may use different Claims cryptographic hashing algorithms to validate file integrity. The system may store related data, including hashes, on 1. A computer-implemented method for decentralized the distributed ledger to preserve integrity of data while computing comprising: on transit and while at rest. 5 providing, by one or more blockchain proces- SOFTWARE PAYLOAD HIGH AVAILABILITY sors, a distributed ledger that specifies a plurality of software payload processing offers and a plu- [0071] Because the software payload runs on hard- rality software payload processing requests; ware that is provided by the payload processor, the sys- 10 presenting, by one or more blockchain proces- tem takes into consideration the possibility that the hard- sors, the plurality of payload processing offers ware might fail, therefore rendering the software payload to a user’s device; inaccessible by its user. presenting, by one or more blockchain proces- [0072] The system illustrated by Fig. 1 may use one or sors, the plurality of payload processing re- more distributed ledgers to coordinate multiple instances 15 quests to a payload processor device; of the same software payload executed by multiple pay- receiving, by one or more blockchain proces- load processors. sors, a processing request from the user device, [0073] The user (17) stores within the distributed ledg- wherein the particular processing request com- er transaction preferences and metadata used for the prises minimum hardware requirements and a cluster-style or similar communication. 20 software payload; [0074] Payload processors (2,3,4) read high availabil- receiving, by one or more blockchain proces- ity related information from the software payload sors, a processing offer from the payload proc- processing requests and provide the requested services. essor device, wherein the particular processing Payload processors may use one or more blockchain offer comprises available hardware for payload solutions to exchange high availability information. 25 processing services; [0075] Software payloads (5,6,7,8,9,10,11,12,13) may appending, by one or more payload processors, use one or more blockchain solutions (14,15,16) to ex- metadata describing minimum cryptocurrency change high availability information. cost of each of the payload processing offers, [0076] In one embodiment, the communication and co- and ordination between the payload processors may be man- 30 receiving, by one or more payload processors, aged by the hypervisor software, using one or more payment for payload processing services blockchains. In another embodiment, the communication through the distributed ledger. and coordination between the payload processor may be managed by the software payload itself, using one or 2. The computer-implemented method of claim 1, more blockchains. 35 wherein the payload processing request from the us- [0077] In one or more embodiments the communica- er device is sent using anonymizing technology to tion may be encrypted and anonymous and may use one maintain the privacy of a user and a user’s device. or more blockchain solutions. The system may store re- lated data on the distributed ledger to establish network 3. The computer-implemented method of claim 1, fur- identity of the participants and their roles in the cluster. 40 ther comprising:

NON-LIMITING EXAMPLES appending, by one or more payload processors, metadata describing encryption capabilities for [0078] The discretion of the present application has each of the payload processing offers; been presented for purposes of illustration and descrip- 45 appending, by one or more users, metadata de- tion but is not intended to be exhaustive or limited to the scribing encryption requirements for each of the invention in the form disclosed. Many modifications and payload processing request; variations will be apparent to those of ordinary skill in the appending, by one or more users, metadata de- art without departing from the scope and spirit of the in- scribing a cryptographic public key to the vention. The embodiment was chosen and described to 50 processing request, and best explain the principles of the invention and practical appending, by one or more users, metadata de- application, and to enable others of ordinary skill in the scribing a cryptographic hash to the processing art to understand the invention for various embodiments request. with various modifications as are suited to the particular use contemplated. 55 4. The computer-implemented method of claim 1, fur- ther comprising: appending, by one or more users, metadata describ- ing a payload concurrency processing value to the

6 11 EP 3 793 130 A1 12

processing request. appending, by one or more users, metadata describ- ing a payload concurrency processing value to the 5. The computer-implemented method of claim 1, processing request. wherein the distributed ledger is a blockchain. 5 11. The system of claim 7, wherein the distributed ledger 6. The computer-implemented method of claim 1, is a blockchain. wherein the distributed ledger uses a smart contract. 12. The system of claim 7, wherein the distributed ledger 7. A system for decentralized computing comprising: uses a smart contract. 10 a memory; 13. A system for decentralized computing comprising: a processor communicatively coupled to the memory; a memory; providing, a distributed ledger that specifies a a processor communicatively coupled to the plurality of software payload processing offers 15 memory; and a plurality software payload processing re- providing, a distributed ledger that specifies a quests; plurality of software payload processing offers presenting, the plurality of payload processing and a plurality software payload processing re- offers to a user’s device; quests; presenting, the plurality of payload processing 20 providing, a processing offer from the payload requests to a payload processor device; processor device, wherein the particular receiving, a processing request from the user processing offer comprises available hardware device, wherein the particular processing re- for payload processing services, and quest comprises minimum hardware require- receiving, a processing request from the distrib- ments and a software payload; 25 uted ledger, wherein the particular processing receiving, a processing offer from the payload request comprises minimum hardware require- processor device, wherein the particular ments and a software payload; processing offer comprises available hardware providing, the particular payload processing for payload processing services; service, as per payload processing request, appending, by one or more payload processors, 30 along ensuring confidentiality, integrity and metadata describing minimum cryptocurrency availability of the software payload. cost of each of the payload processing offers, and 14. The system of claim 13, wherein the distributed ledg- providing, to one or more payload processors, er is a blockchain. payment for payload processing services 35 through the distributed ledger. 15. The system of claim 14, wherein the distributed ledg- er uses a smart contract. 8. The system of claim 7, wherein the payload process- ing request from the user device is sent using ano- 16. A computer program product for decentralized com- nymizing technology to maintain the privacy of a user 40 puting comprising a computer storage medium hav- and a user’s device. ing computer readable program code embodied therewith, the computer readable program code con- 9. The system of claim 7, further comprising: figured to perform:

appending, by one or more payload processors, 45 providing, a distributed ledger that specifies a metadata describing encryption capabilities for plurality of software payload processing offers each of the payload processing offers; and a plurality software payload processing re- appending, by one or more users, metadata de- quests; scribing encryption requirements for each of the presenting, the plurality of payload processing payload processing request; 50 offers to a user’s device; appending, by one or more users, metadata de- presenting, the plurality of payload processing scribing a cryptographic public key to the requests to a payload processor device; processing request, and receiving, a processing request from the user appending, by one or more users, metadata de- device, wherein the particular processing re- scribing a cryptographic hash to the processing 55 quest comprises minimum hardware require- request. ments and a software payload; receiving, a processing offer from the payload 10. The system of claim 7, further comprising: processor device, wherein the particular

7 13 EP 3 793 130 A1 14

processing offer comprises available hardware for payload processing services.

17. A computer program product for decentralized com- puting comprising a computer storage medium hav- 5 ing computer readable program code embodied therewith, the computer readable program code con- figured to perform:

providing, a distributed ledger that specifies a 10 plurality of software payload processing offers and a plurality software payload processing re- quests; providing, a processing offer from the payload processor device, wherein the particular 15 processing offer comprises available hardware for payload processing services, and providing, the particular payload processing service, as per payload processing request, along ensuring confidentiality, integrity and 20 availability of the software payload.

25

30

35

40

45

50

55

8 EP 3 793 130 A1

9 EP 3 793 130 A1

10 EP 3 793 130 A1

11 EP 3 793 130 A1

12 EP 3 793 130 A1

13 EP 3 793 130 A1

14 EP 3 793 130 A1

15 EP 3 793 130 A1

5

10

15

20

25

30

35

40

45

50

55

16