hyperledger / hyperledger/fabric-x-sdk
Add FinalityProvider, wait for finality on classic fabric submit (optional)
- Dominant language
- Go
- Stars
- 3
- Forks
- 5
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 9
Description
Followup of PR https://github.com/hyperledger/fabric-x-sdk/pull/37 ; but instead of Fabric-X, now implementing it for classic Fabric.
This can be done by implementing DeliverFiltered and qscc.GetTransactionByID as sources for the finalityprovider, along with some simple mapping of the status codes.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading follow-up PR 37, then inspect the classic Fabric submit flow and the DeliverFiltered and qscc.GetTransactionByID entry points named in the issue. Determine how they can provide finality information and map their status codes; done means classic Fabric submission can optionally wait for finality.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100