-
Notifications
You must be signed in to change notification settings - Fork 215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
configuration to load multiple smeshers from disk #5089
Comments
Aren't NodeID and public key the same? I still think we should add NodeID to logs where it makes sense; e.g. if a certain identity published an ATX or voted in a specific way. I agree for general logs that are not tied to an identity we can drop NodeID in the logs. |
NodeID is already present in each logger name, for example:
We could keep it similar if each identity had its dedicated logger for a given protocol. |
I'm not a big fan of putting the node id into the logger name. It will get lost if one creates a sub-logger with |
AFAIK, both append postfix to the existing name. |
This has been completed with #5592 |
please see #5085 for interface that must be implemented by every protocol that requires access to signing key.
storing keys
store keys in separately configurable directory, defaults to {datadir}/keys/. each smesher is stored in a file with public key in hexary encoding. on startup we have to read all public keys and calll
Register
method on every protocol that supports it.refactoring / migration from old
right now "node_id" is added to every log line, we want to drop that. instead print info log with public key that was loaded from disk.
generating key
node itself can generate only one key when smeshing starts. other keys are either generated manually by user, or using dynamic configuration as will be discussed in a follow up.
The text was updated successfully, but these errors were encountered: