You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: ccf_transaction_processor/Readme.md
+3-7Lines changed: 3 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,8 @@ The TP must viewed as a CCF application. Documentation for building and deployin
14
14
can be found at https://microsoft.github.io/CCF/. The CCF legder that stores the PDO TP registries is
15
15
encrypted, and is accessible only within CCF encalves. Currently PDO/CCF combination is supported
16
16
only under the virtual enclave mode for both PDO and CCF. (set env variable SGX_MODE=SIM for PDO &
17
-
set cmake flag TARGET=virtual for ccf). Support for HW mode for both PDO and CCF will be added soon.
17
+
set cmake flag TARGET=virtual for ccf). Support for HW mode for both PDO and CCF will be added soon. Further,
18
+
the current implementation of PDO TP hasn't been tested under multi-threaded CCF enclaves.(CCF 0.7.1 offers initial support for multi-threading). It is recommended that the application is deployed with single worker thread per enclave. Please see https://microsoft.github.io/CCF/developers/threading.html for instructions.
18
19
19
20
CCF uses mutually authenticated TLS channels for transactions. Given that in PDO client authentication is implemented within the transaction processor itself, we do not utilize the client authentication feature provided by CCF. Once CCF is deployed, CCF's network certificate (networkcert.pem) and one set of user keys (userccf_cert.pem & userccf_privk.pem)
20
21
must be made available to all PDO processes that want to submit a CCF transaction. In this case, every
@@ -26,12 +27,7 @@ As far as PDO is concerned, CCF based TP is functionally identical to the Sawtoo
26
27
TP (except for one additional feature described below). A key difference beween the two ledgers
27
28
is the fact that while the ledger in CCF is encrypted as noted above, the ledger is Sawtooth is stored in plain text.
28
29
Even though the no part of conract state gets stored in the ledger in both CCF & Sawtooth, encrypting the
29
-
ledger as in CCF helps to hide transaction patterns that are otherwise visible in Sawtooth ledger. Detailed documentation
30
-
about Sawtooth based TP can be found at $PDO_SRC/sawtooth/docs. The schema for JSON payloads used to submit
For additional references to documentation about PDO, including transaction processor protocols,
34
-
see [${PDO_SRC}/README.md](../README.md)
30
+
ledger as in CCF helps to hide transaction patterns that are otherwise visible in Sawtooth ledger. Detailed documentation about Sawtooth based TP can be found at $PDO_SRC/sawtooth/docs. The schema for JSON payloads used to submit CCF transactions can be found at [${PDO_SRC}/python/pdo/submitter/ccf/docs/](../python/pdo/submitter/ccf/docs/ccf_payload_schema.json). For additional references to documentation about PDO, including transaction processor protocols, see [${PDO_SRC}/README.md](../README.md)
35
31
36
32
A feature of the CCF based TP that is not supported by Sawtooth based TP is the fact that
37
33
responses to read-transactions include a payload signature, where the signature is generated by the CCF enclave
0 commit comments