Add Go chaincode for asset-transfer-events #1189
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Mark S. Lewis <Mark.S.Lewis@outlook.com>
|
Cool, thanks. I'll merge with the failing SBE test since it is not related. I've opened #1190 for the failing SBE test. I didn't see an obvious reason for the failure since the other Java chaincodes are still working... |
denyeart
approved these changes
Apr 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There were recently questions on how to emit chaincode events from Go smart contracts: hyperledger/fabric-gateway#698
This implementation is based on the asset-transfer-basic chaincode (as the README already suggests) and does not include the private data used by the other language implementations. I don't know why private data is necessary to demonstrate chaincode eventing.