Remove dependency on name data that cash/obligation state objects will not have access to party details (such as name)
once privacy is correctly enforced.
Make FinalityFlow do more, and be used more consistently.
Add a new waitForLedgerCommit API that is intended to be used at the end of flows, or at any other point where a flow wants to wait for a transaction to finalise (but the finalisation flow is being done by someone else).
Update the docs a bit.
* Move merkle building extension functions on wire tx to WireTransaction class.
* Add timestamp, notary, transaction type and signers to wire transaction id calculation.
* Change construction of MerkleTree from duplicating last node on a given level to padding leaves' list with zero hash to size of the nearest power of 2 - so we always have a full binary tree.
The problem was that it was possible to construct 2 different transactions with the same ids. Trick worked for txs having number of leaves that were not power of 2.
* Update tear-offs documentation and diagrams to reflect changes in construction of Merkle trees - padding with zero hashes and including all WireTransaction fields in id computation.
* Change in filtering API of WireTransaction for partial Merkle trees calculation.
Instead of many filtering functions over a transaction only one needs to be provided.
Additional change to check and verification of FilteredTransaction.
* IRS demo change. Make filtering function a protected method of RatesFixFlow class.
Comment on situation when capturing too much scope and connected problems with checkpointing.
Change oracle and tear-offs documentation.
* Prevent node from starting across upgrades (until we support it better).
On first run a version file is created in the node dir, and on subsequent runs the node version is matched against it.
* Move version check from caplet to node.
InMemoryNetworkMapCacheTest was not actually asserting that an expected exception was thrown, which
meant when earlier changes to the service changed the operation it wasn't caught. The service now
overwrites previous node if a new matching node is added, and this updates the test to follow that
design.
The IRS demo uses names of parties to identify them in flows, which introduces problems when a node may not
know who a party is, as well as being a poor choice of key generally. This switches to use the owning key
instead.
Change Party instances to be uniquely identified by the owning key, without taking into account name.
This requires that mock node key generation is reworked so that keys for services and the node itself
are distinct, otherwise the network map service cannot differentiate them.
Signed-off-by: Ross Nicoll <ross.nicoll@r3.com>
First draft
Re-structured Key Concepts; added plenty of diagrams; additional content.
Added references to other security docs.
Re-structured Key Concepts; added plenty of diagrams; additional content.
Added references to other security docs.
Updated information, indexes and images.
Incorporated feedback from PR review comments (RGB, RW)
Reformatted diagrams and incorporated feedback from PR reviewers.
Addressed formatting problems.
Updated Flow Framework diagram
Added colour coding to Flow Framework diagram to aid readibility.
Small clarification to vault unconsumed state usage.
Added tutorial reference as suggested by RGB
Updated TOC tree.
Updates following PR review comment from Roger
First pass updates following PR review comments from MH.
Further updates following PR review (including 2 edited diagrams)
Diagram changes and minor text edits following review with MGB
Remove unused diagrams.
Fixed spurious indentation errors.
Changes following review and feedback from JD.
Added clauses and merkle-trees back into TOC.
Added small sub-section on transaction representation in Data Model.
Added future work as note in Vault.
Minor updates to diagrams following MH review.
Updated Corda Ecosystem diagram.
Minor changes to Core & Financial docs following PR review by MH.
Updated following review by MBG.
Remove TransferRecipient from StateMachineManagerTests to get rid one of the approximately 6 different ways
in which we refer to endpoints, as part of work to simplify this data model.
Signed-off-by: Ross Nicoll <ross.nicoll@r3.com>
