Skip to content
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

Debug Ledger Issues #418

Closed
homura opened this issue Jul 31, 2024 · 0 comments · Fixed by nervosnetwork/neuron#3212
Closed

Debug Ledger Issues #418

homura opened this issue Jul 31, 2024 · 0 comments · Fixed by nervosnetwork/neuron#3212

Comments

@homura
Copy link

homura commented Jul 31, 2024

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:

  1. NEVER write any private keys
  2. For debug only
  3. 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant