fabric-private-chaincode
fabric-private-chaincode copied to clipboard
hyperledger
FPC enables Confidential Chaincode Execution for Hyperledger Fabric using Intel SGX.
The code in demo/client/backend is currently auction-specific but has the potential of being much more widely usable to either efficiently test chaincode (mock) or running UI apps (fabric-gateway). Note this...
[Validation/Committer refactor](https://jira.hyperledger.org/browse/FAB-12221) was being worked on prior to 2.0 release and was supposed to pick up steam post release. Would be good to sync up and coordinate for alignment in...
Any chaincode transaction can have exactly one endorsing peer (enclave) but it could be any involved peer. Requires #273, key distribution but does not yet require yet deterministic (de-randomized) state...
Do crypto-paging and keep only cache inside memory ....
This is the current pragmatic state. Obviously has as challenge to keep TLCC code consistent with fabric code. #276 would be more long-term approach
Requires go support for sgx (#279) and a refactoring of fabric core to allow for minimal amount of fabric core code having to be integrated into TLCC See #277 and...
In many (most?) cases when private information/result is returned to a the transaction requester, it should be only revealed _after_ the transaction is committed (or the requester might cheat, e.g.,...
sate queries from ecc to TLCC for meta-data and get_state to peer have to be consistent between each other but also across time. Ideally would have a view identifier. Might...
On a peer restart, an admin has to manually trigger a `JOIN_CHANNEL` transaction to tlcc. Main concern is that "channel owner/creator" is not necessarily some person as "peer admin" yet...
Metadata
Owner
Metadata
FPC enables Confidential Chaincode Execution for Hyperledger Fabric using Intel SGX.