Great update as usual. A small interrogation though:
Currently vault config file uses a network config from routing which is a reexport of quic-p2p config which contains a certificate. Then certificate of each of our peers is provided in its NodeInfo structure.
So, what does this mean?
-
peer certificates will not be available to safe_vault anymore
-
or they will be still available, but there will no code using it
I ask this question because a network name was managed in the past to avoid accidental insertion of a vault in the wrong network. Such a name is not managed anymore, but could be stored in the certificate. Another use case could be the opportunity for vaults to store complementary data in this certificate, like a vault name.