Decentralized secure data sharing
View Patent ↗An example operation may include one or more of authenticating, by a first service node, to a first client node, receiving, by the first service node, a data access request from the first client node, comprising request parameters and a request token, generating, by the first service node, a receipt key corresponding to the data access request, and sharing data with a second client node based on the request token and the receipt key.
1. A service node in a blockchain network, the first service node, comprising:
a processor that when executing one or more instructions stored in a memory is configured to:
authenticate the service node to a first client node;
receive a request from the first client node to access data stored in a blockchain ledger common to the first client node and to a second client node, the request comprising parameters and a request token;
generate a receipt key that corresponds to the data access request;
share data with a second client node based on the request token and the receipt key; and
store a computed result for the data access request, the request token, and the receipt key in the ledger.
2. The service node of claim 1 , wherein the processor is further configured to:
send a receipt including the receipt key to the first client node in response to the request.
3. The service node of claim 1 , wherein the processor is further configured to:
register at least one service for accessing the data store based on the request token and the receipt key.
4. A method, comprising:
authenticating, by a service node, to a first client node;
receiving, by the first service node, a request from the first client node to access data stored in a blockchain ledger common to the first client node and to a second client node, the request comprising parameters and a request token;
generating, by the first service node, a receipt key corresponding to the data access request;
sharing, by the first service node, data with a second client node based on the request token and the receipt key; and
storing, by the first service node, a computed result for the data access request, the request token, and the receipt key in the ledger.
5. The method of claim 4 , further comprising:
sending a receipt including the receipt key to the first client node in response to the request.
6. The method of claim 4 , further comprising:
registering at least one service for accessing the data store based on the request token and the receipt key.
7. A non-transitory computer readable medium comprising one or more instructions that when executed by a processor of a service node cause the processor to perform:
authenticating to a first client node;
receiving a request from the first client node to access data stored in a blockchain ledger common to the first client node and to a second client node, the request comprising parameters and a request token;
generating a receipt key corresponding to the data access request;
sharing data with a second client node based on the request token and the receipt key; and
storing a computed result for the data access request, the request token, and the receipt key in the ledger.
8. The non-transitory computer readable medium of claim 7 , wherein the one or more instructions further cause the processor to perform:
sending a receipt including the receipt key to the first client node in response to the request.
9. The non-transitory computer readable medium of claim 7 , wherein the one or more instructions further cause the processor to perform:
registering at least one service for accessing the data store based on the request token and the receipt key.