You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Neuron now only writes simple and privacy-friendly messages in the log files, such as version information, launch time, and syncing status. While this is good for privacy, it makes solving certain problems, particularly IO problems (like issue #103 mentioned), more challenging. If the maintainer team could access the exchange data when IO issues occur, it would be very helpful in addressing these issues.
Share Unsent Transaction for Debugging
I'm sure crypto fundamentalists don't want their social media accounts to be associated with blockchain accounts, and this logger will do so with minimal exposure to the designated person, the official maintainer
The logger MUST:
NEVER write any private keys
For debug only
Content encrypted
sequenceDiagram
participant maintainer as Maintainers
participant admin as Admin
participant client as Client
admin ->> client: Official public key
client -->> client: Failed signing and log unsent raw tx
client->> maintainer: Email
maintainer -->> admin: Request for decrypting
admin -->> maintainer: Partially decrypt for debugging
Loading
The text was updated successfully, but these errors were encountered:
Neuron now only writes simple and privacy-friendly messages in the log files, such as version information, launch time, and syncing status. While this is good for privacy, it makes solving certain problems, particularly IO problems (like issue #103 mentioned), more challenging. If the maintainer team could access the exchange data when IO issues occur, it would be very helpful in addressing these issues.
Share Unsent Transaction for Debugging
I'm sure crypto fundamentalists don't want their social media accounts to be associated with blockchain accounts, and this logger will do so with minimal exposure to the designated person, the official maintainer
The logger MUST:
The text was updated successfully, but these errors were encountered: