Blockchain notification board storing blockchain resources
An example operation may include one or more of receiving a resource request from a client, identifying a unique chaincode identifier associated with the resource request, re-instantiating a version of chaincode based on the unique chaincode identifier, the re-instantiation configured to disregard any subsequently implemented versions of the chaincode at the computing node, executing the resource request based on the re-instantiated version of the chaincode to generate a result, and transmitting the result to the client.
1. A computing node comprising:
a network interface configured to receive a resource request from a client; and
a processor configured to
identify a unique blockchain-based uniform resource identifier (BURI) comprising information about chaincode used by a blockchain peer to access a mutable notification board that is stored within a blockchain ledger of the blockchain peer,
determine a version of the chaincode of the blockchain peer at a time the BURI was created based on a chaincode identifier and a time value stored within the BURI,
re-instantiate the version of the chaincode and execute the resource request based on the re-instantiated version of the chaincode to generate a result, and
transmit the result to the client.
2. The computing node of claim 1 , wherein the time value comprises a time at which the BURI is added to the mutable notification board on the blockchain ledger associated with the resource request.
3. The computing node of claim 1 , wherein the processor is further configured to generate a read set to be read by the chaincode in which previous key values are substituted for current values based on the time value included in the BURI.
4. The computing node of claim 1 , wherein the processor is configured to prevent a subsequent version of the chaincode from being reinstated based on the chaincode identifier and the time value included in the BURI.
5. The computing node of claim 1 , wherein the result identifies a set of current BURIs of a plurality of peer nodes that are members of the immutable blockchain.
6. A computer implemented method comprising:
receiving a resource request from a client;
identifying a unique blockchain-based uniform resource identifier (BURI) comprising information about chaincode used by a blockchain peer to access a mutable notification board that is stored within a blockchain ledger of the blockchain peer;
determining a version of the chaincode of the blockchain peer at a time the BURI was created based on a chaincode identifier and a time value stored within the BURI;
re-instantiating the version of the chaincode and executing the resource request based on the re-instantiated version of the chaincode to generate a result; and
transmitting the result to the client.
7. The method of claim 6 , wherein the time value comprises a time at which the BURI is added to the mutable notification board on the blockchain ledger associated with the resource request.
8. The method of claim 6 , wherein the executing further comprises generating a read set to be read by the chaincode in which previous key values are substituted for current values based on the time value included in the BURI.
9. The method of claim 6 , wherein the re instating comprises preventing a subsequent version of the chaincode to from being reinstated based on the chaincode identifier and the time value included in the BURI.
10. The method of claim 6 , wherein the result identifies a set of current BURIs of a plurality of peer nodes that are members of the immutable blockchain.
11. A non-transitory computer readable medium comprising instructions, that when read by a processor, cause the processor to perform a method comprising:
receiving a resource request from a client;
identifying a unique blockchain-based uniform resource identifier (BURI) comprising information about chaincode used by a blockchain peer to access a mutable notification board that is stored within a blockchain ledger of the blockchain peer;
determining a version of the chaincode of the blockchain peer at a time the BURI was created based on a chaincode identifier and a time value stored within the BURI;
re-instantiating the version of the chaincode and executing the resource request based on the re-instantiated version of the chaincode to generate a result; and
transmitting the result to the client.
12. The non-transitory computer readable medium of claim 11 , wherein the time value comprises a time at which the BURI is added to the mutable notification board on the blockchain ledger associated with the resource request.
13. The non-transitory computer readable medium of claim 12 , wherein the executing further comprises generating a read set to be read by the chaincode in which previous key values are substituted for current values based on the time value included in the BURI.
14. The non-transitory computer readable medium of claim 11 , wherein the re instating comprises preventing a subsequent version of the chaincode to re instantiate from being reinstated based on the chaincode identifier and the time value included in the BURI.
15. The non-transitory computer readable medium of claim 11 , wherein the result identifies a set of current BURIs of a plurality of peer nodes that are members of the immutable blockchain.