ExternalVendorCode/corda
1
0
Fork 0
mirror of https://github.com/corda/corda.git synced 2025-01-29 15:43:55 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Docs: address review comments from Richard.

Browse Source
This commit is contained in:
Mike Hearn 2018-12-20 16:35:47 +01:00
parent ee5536da14
commit f8026e9775
1 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/source/release-notes.rst
View File

@ -87,6 +87,11 @@ beans inside your flows and services.
Please do write apps that read and write directly to tables running alongside the node's own tables. Using
SQL is a convenient and robust design pattern for accessing data on or off the ledger.
.. important:: Please do not attempt to write to tables starting with ``node_`` or ``contract_`` as those
are maintained by the node. Additionally, the ``node_`` tables are private to Corda and should not be
directly accessed at all. Tables starting with ``contract_`` are generated by apps and are designed to
be queried by end users, GUIs, tools etc.
Security upgrades
+++++++++++++++++
@ -127,8 +132,9 @@ Network parameters in transactions
Transactions created under a Corda 4+ node will have the currently valid signed ``NetworkParameters``
file attached to each transaction. This will allow future introspection of states to ascertain what was
the accepted global state of the network at the time they were notarised. Additionally, new signatures must
be working with the current globally accepted parameters. This means older parameters where something
was legal and no longer is cannot be used.
be working with the current globally accepted parameters. The notary signing a transaction will check that
it does indeed reference the current in-force network parameters, meaning that old (and superseded) network
parameters can not be used to create new transactions.
RPC upgrades
++++++++++++