Typical log levels are : debug, warn, info. I see logging in the console for operations that appear to be debug/performance related output. For example, in creating a wallet, I get:
sha3^n generation time: 566.120ms
sha3^n generation time: 571.529ms
While this may seem like an significant detail and useful debug logging for performance, I should be able to choose what goes to stdout and stderr, and be able to manage these streams as needed. I'd suggest either scan through the code and comment out debug logging, or add in a log manager to handle logging so that it can be configured by the user through config or environment.
Typical log levels are : debug, warn, info. I see logging in the console for operations that appear to be debug/performance related output. For example, in creating a wallet, I get: sha3^n generation time: 566.120ms sha3^n generation time: 571.529ms
While this may seem like an significant detail and useful debug logging for performance, I should be able to choose what goes to stdout and stderr, and be able to manage these streams as needed. I'd suggest either scan through the code and comment out debug logging, or add in a log manager to handle logging so that it can be configured by the user through config or environment.