-
Notifications
You must be signed in to change notification settings - Fork 283
Move keys out of configuration #2824
Copy link
Copy link
Open
Labels
RefactorImprovement to overall code qualityImprovement to overall code qualityconfig-changesChanges in configuration and start up of the IrohaChanges in configuration and start up of the Irohairoha2-devThe re-implementation of a BFT hyperledger in RUSTThe re-implementation of a BFT hyperledger in RUST
Description
Metadata
Metadata
Assignees
Labels
RefactorImprovement to overall code qualityImprovement to overall code qualityconfig-changesChanges in configuration and start up of the IrohaChanges in configuration and start up of the Irohairoha2-devThe re-implementation of a BFT hyperledger in RUSTThe re-implementation of a BFT hyperledger in RUST
Type
Projects
Status
Backlog
As discussed on a call with @appetrosyan and @Erigara, we want to move towards configuration which would not keep track of any configuration parameters that are common to all the network, such as consensus parameters and so on, but instead would bootstrap those via some stand-in process and maybe IPC.
A similar logic should apply to keys: they are not configuration parameters per se, but important credentials that should rather be initialized once during the lifetime of a peer, thus also obsoleting the need for the keep-in-sync routine for keys done in
Configuration'sfinish().