ExternalVendorCode/corda
1
0
Fork 0
mirror of https://github.com/corda/corda.git synced 2024-12-23 14:52:29 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Add remark about flow deniability.

Browse Source
This commit is contained in:
Mike Hearn 2019-06-21 15:14:46 +01:00
parent d3c9679389
commit 59f839d80a
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/source/whitepaper/corda-technical-whitepaper.tex
View File

@ -377,6 +377,10 @@ itself, for example in case of database deadlocks that require a retry. The abil
useful for cases where the other side isn't sure why you are contacting them, for example, the specified reason for useful for cases where the other side isn't sure why you are contacting them, for example, the specified reason for
sending a payment is not recognised, or when the asset used for a payment is not considered acceptable. sending a payment is not recognised, or when the asset used for a payment is not considered acceptable.
For performance reasons messages sent over flows are protected only with TLS. This means messages sent via flows
are deniable unless explicitly signed by the application. Automatic signing and recording of flow contents may be
added in future.
Flows are identified using Java class names i.e. reverse DNS notation, and several are defined by the base Flows are identified using Java class names i.e. reverse DNS notation, and several are defined by the base
protocol. Note that the framework is not required to implement the wire protocols, it is just a development aid. protocol. Note that the framework is not required to implement the wire protocols, it is just a development aid.