You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use the following code to call the chaincode. First, I use client A to write the world state, and then I use client B to read the value from the world state. But the data I read from B is the old value instead of the value just written to the world state. Why?
Doesn't Execute return the result only after receiving the information that the peer node has successfully verified it?
Note: This API is deprecated and is no longer maintained as of Fabric v2.5. When developing applications for Hyperledger Fabric v2.4 and later, you should use the Fabric Gateway client API.
Note: This API is deprecated and is no longer maintained as of Fabric v2.5. When developing applications for Hyperledger Fabric v2.4 and later, you should use the Fabric Gateway client API.
I am using v2.3, do you have any other suggestions?
Note: This API is deprecated and is no longer maintained as of Fabric v2.5. When developing applications for Hyperledger Fabric v2.4 and later, you should use the Fabric Gateway client API.
I am using v2.3, do you have any other suggestions?
I use the following code to call the chaincode. First, I use client A to write the world state, and then I use client B to read the value from the world state. But the data I read from B is the old value instead of the value just written to the world state. Why?
Doesn't Execute return the result only after receiving the information that the peer node has successfully verified it?
My test chaincode is as follows
The text was updated successfully, but these errors were encountered: