Bruno Vavala
Bruno Vavala
Notes: at the time #501 was merged, FPC updates the read/write set in `shim.cpp` and behaves as follows for a given key `k`: * only the hash of the first...
Additional info in: * comment https://github.com/hyperledger-labs/fabric-private-chaincode/pull/388/files#r447985598 (including suggestion to look for the validation plugin)
> Do we really want to do this as part of MVP mileston? We don’t support composite keys in FPC lite security model? And even if we would decide to...
Sounds good to me.
> The other case where we may want to leverage cc2cc call is to let ercc retrieve the chaincode definition, in particular the MRENCLAVE, for a FPC chaincode. As ercc...
(The inputs in theory should include the "transient" fields as well, but they don't.) The gist of the solution is in your point (1): MVCC does the trick, as long...
> btw: to securely get the caller CC's identity/namespace [this fabric-ml article](https://lists.hyperledger.org/g/fabric/message/8404) might be helpful ... I think that that's not the caller, but rather the **_callee_** of a chaincode...
epid-based attestations work with DCAP. Additional work is required to support ECDSA.
Moving this issue to a later project
Another useful feature and test that can be added in this setting is the following: * 3 peers/orgs, only one of which is the SGX-capable FPC endorser, and only that...