ExternalVendorCode/corda
1
0
Fork 0
mirror of https://github.com/corda/corda.git synced 2024-12-30 09:48:59 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Improve documentation surrounding network parameter updates/flag day (#4652)

Browse Source 
Improve documentation surrounding network parameter updates and flag days
This commit is contained in:
Oliver Knowles 2019-01-28 13:32:50 +00:00 committed by GitHub
parent f04a2e72e0
commit 631f04e348
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
docs/source/network-map.rst
View File

@ -140,19 +140,20 @@ connectivity is required for zone members, required cryptographic algorithms and
Network parameters update process Network parameters update process
--------------------------------- ---------------------------------
In case of the need to change network parameters Corda zone operator will start the update process. There are many reasons Network parameters are controlled by the zone operator of the Corda network that you are a member of. Occasionally, they may need to change
that may lead to this decision: adding a notary, setting new fields that were added to enable smooth network interoperability, these parameters. There are many reasons that can lead to this decision: adding a notary, setting new fields that were added to enable
or a change of the existing compatibility constants is required, for example. smooth network interoperability, or a change of the existing compatibility constants is required, for example.
.. note:: A future release may support the notion of phased roll-out of network parameter changes. .. note:: A future release may support the notion of phased roll-out of network parameter changes.
To synchronize all nodes in the compatibility zone to use the new set of the network parameters two RPC methods are Updating of the parameters by the zone operator is done in two phases:
provided. The process requires human interaction and approval of the change, so node operators can review the 1. Advertise the proposed network parameter update to the entire network.
differences before agreeing to them. 2. Switching the network onto the new parameters - also known as a `flag day`.
When the update is about to happen the network map service starts to advertise the additional information with the usual network map The proposed parameter update will include, along with the new parameters, a human-readable description of the changes as well as the
data. It includes new network parameters hash, description of the change and the update deadline. Nodes query the network map server deadline for accepting the update. The acceptance deadline marks the date and time that the zone operator intends to switch the entire
for the new set of parameters. network onto the new parameters. This will be a reasonable amount of time in the future, giving the node operators time to inspect,
discuss and accept the parameters.
The fact a new set of parameters is being advertised shows up in the node logs with the message The fact a new set of parameters is being advertised shows up in the node logs with the message
"Downloaded new network parameters", and programs connected via RPC can receive ``ParametersUpdateInfo`` by using "Downloaded new network parameters", and programs connected via RPC can receive ``ParametersUpdateInfo`` by using