CCF
CCF copied to clipboard
microsoft
Confidential Consortium Framework
With links to the endorsement diagram.
Hello, I am currently attempting to run, a CCF node in SGX hardware mode (release enclave type). **To Reproduce** Run `/opt/ccf/bin/sandbox.sh --enclave-type release` Output: ``` Setting up Python environment... No...
We could make governance substantially stronger against replay attacks, without requiring member re-keying as we do now, when non-specific proposals have been created. The scheme would involve having members add...
The per-endpoint metrics (number of calls, error, retries) has been a weird bridge between the `Frontend` and the `EndpointRegistry` for a while - primarily owned and updated by the `Frontend`,...
There are a number of contexts, such as producing commitments to private claims in receipts that require keys to be derived from a master secret. That master secret does not...
The logging sample ought to be extended to support private claims and illustrate what's suggested under https://microsoft.github.io/CCF/main/use_apps/verify_tx.html#application-claims. The documentation should be updated to clarify that the private claims are commitments...
For initial implementation (with HTTP transport), we can simply iterate through all registered executors, and choose the first match. Additionally, we can queue all client requests and actually provide them...
To prove out the utility of multi-container CCF, we should provide and maintain sample executor apps in multiple languages. We should also demonstrate interesting, flexible behaviours possible in container executors,...
For a first-pass, I think we have executors speaking to CCF over the client API, interleaved with client traffic. Eventually we want to expose these separately, both for API clarity...
_Originally posted by @achamayou in https://github.com/microsoft/CCF/pull/4106#discussion_r947705993_
