Skip to content

Commit

Permalink
Remove stubwrapper from inside transactions
Browse files Browse the repository at this point in the history
Signed-off-by: Aline Lermen <[email protected]>
  • Loading branch information
AlineLermen authored Oct 20, 2023
1 parent 0ff7c55 commit 44e91dc
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -88,7 +88,7 @@ It is possible to also create custom transactions in the chaincode, that must be

The transactions package has the `StartupCheck` just like the assets package, which is a function that verifies if all the transactions are correctly implemented in the chaincode.

#### **StubWrapper**
### **StubWrapper**
The main purpose of the StubWrapper is to provide additional functionalities and simplify the development of chaincodes.

The StubWrapper maintains a WriteSet to ensure that modifications made during the execution of a chaincode are properly reflected when querying the ledger state. Even if these changes have not been confirmed on the ledger yet, the StubWrapper records the pending modifications in the WriteSet. This allows subsequent queries to utilize the WriteSet to return the updated data, ensuring consistency and accuracy of information during the execution of the chaincode. The same applies to private data.
Expand All @@ -108,4 +108,4 @@ Feel free to fork it, create issues and PRs. We'll be happy to review them.

## Join our community

If you want to chat about Fabric, cc-tools and blockchain, you can reach GoLedger's technical team at our [Discord](https://discord.com/invite/GndkYHxNyQ)!
If you want to chat about Fabric, cc-tools and blockchain, you can reach GoLedger's technical team at our [Discord](https://discord.com/invite/GndkYHxNyQ)!

0 comments on commit 44e91dc

Please sign in to comment.