Decentralization of configuration parameters - Phase 2

[jpraynaud]

Why

We need to decentralize the configuration parameters of the Mithril network (protocol parameters and certification parameters - signed entity types and their specific configuration parameters e.g. cardano_transactions_signing_config). In a first phase , we want to implement a full synchronization of the network based on the leader aggregator, and in a second phase have the configuration stored on the Cardano chain.

What

Implement the Phase 2 of the decentralization plan of the configuration parameters for Mithril networks.

How

• Implement the Chain reader for the MithrilNetworkConfigurationProvider trait
• Wire in the nodes dependency injection
• ⚠️ Update the signer configurations (could be breaking change / how can we use the same signing key for era and all other information stored on chain)
• Create a new /signer_registrations route in the aggregator that supersedes the /epoch-settings route
• Deprecate aggregator routes previously used by the REST client implementation
• Deprecate the REST client and Local parameters implementations