Context data update in a blockchain network
View Patent ↗An example operation may include one or more of collecting, by a transaction manager node, consensus data from a plurality of peers of a blockchain network, identifying, by the transaction manager node, a conditional consensus for a coordinated transaction based on the consensus data, storing, by the transaction manager node, context data of a coordinated process associated with the coordinated transaction, and updating, by the transaction manager node, the context data in response to a detection of an interim transaction associated with the coordinated process.
1. A system, comprising:
a memory storing one or more instructions; and
a processor that when executing the one or more instructions is configured to:
collect consensus data from a plurality of peers of a blockchain network;
identify a conditional consensus for a coordinated transaction based on the consensus data;
store context data of a coordinated process associated with the coordinated transaction; and
update the context data in response to a detection of an interim transaction associated with the coordinated process.
2. The system of claim 1 , wherein the processor is further configured to:
structure the context data prior to storage.
3. The system of claim 1 , wherein the processor is further configured to:
delete the context data upon a detection of a consensus for a final transaction of the coordinated process.
4. The system of claim 1 , wherein the processor is further configured to:
detect a transaction of the coordinated process that attempts to change a data element in a world state and to deny an execution of the transaction if the data element is locked by the coordinated process.
5. The system of claim 1 , wherein the processor is further configured to:
determine if a context of the coordinated transaction includes an expiration point.
6. The system of claim 5 , wherein the instructions further cause the processor to trigger a final transaction for the coordinated process once the expiration point is reached.
7. The system of claim 1 , wherein the processor is further configured to:
detect a consensus for the coordinated transaction that carries a cancel action; and
roll back a world state based on roll back qualifiers derived from the context data.
8. A method, comprising:
collecting, by a transaction manager node, consensus data from a plurality of peers of a blockchain network;
identifying, by the transaction manager node, a conditional consensus for a coordinated transaction based on the consensus data;
storing, by the transaction manager node, context data of a coordinated process associated with the coordinated transaction; and
updating, by the transaction manager node, the context data in response to a detection of an interim transaction associated with the coordinated process.
9. The method of claim 8 , further comprising:
structuring the context data prior to storage.
10. The method of claim 8 , further comprising:
deleting the context data upon a detection of a consensus for a final transaction of the coordinated process.
11. The method of claim 8 , further comprising:
detecting a transaction of the coordinated process that attempts to change a data element in a world state and denying an execution of the transaction if the data element is locked by the coordinated process.
12. The method of claim 8 , further comprising:
determining if a context of the coordinated transaction includes an expiration point.
13. The method of claim 12 , further comprising:
triggering a final transaction for the coordinated process once the expiration point is reached.
14. The method of claim 8 , further comprising:
detecting a consensus for the coordinated transaction that carries a cancel action; and
rolling back a world state based on roll back qualifiers derived from the context data.
15. A non-transitory computer readable medium comprising one or more instructions that when executed by a processor cause the processor to perform:
collecting consensus data from a plurality of peers of a blockchain network;
identifying a conditional consensus for a coordinated transaction based on the consensus data;
storing context data of a coordinated process associated with the coordinated transaction; and
updating the context data in response to a detection of an interim transaction associated with the coordinated process.
16. The non-transitory computer readable medium of claim 15 , wherein the one or more instructions further cause the processor to perform:
structuring the context data prior to storage.
17. The non-transitory computer readable medium of claim 15 , wherein the one or more instructions further cause the processor to perform:
deleting the context data upon a detection of a consensus for a final transaction of the coordinated process.
18. The non-transitory computer readable medium of claim 15 , wherein the one or more instructions further cause the processor to perform:
detecting a transaction of the coordinated process that attempts to change a data element in a world state and to deny an execution of the transaction if the data element is locked by the coordinated process.
19. The non-transitory computer readable medium of claim 15 , wherein the one or more instructions further cause the processor to perform:
triggering a final transaction for the coordinated process once an expiration point within a context of the coordinated transaction is reached.
20. The non-transitory computer readable medium of claim 15 , wherein the one or more instructions further cause the processor to perform:
a consensus for the coordinated transaction that carries a cancel action; and
rolling back a world state based on roll back qualifiers derived from the context data.