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
[2.6][T4] Core unable to decrypt passphrase #3269
Comments
Thanks for opening this issue! A maintainer will review this in the next few days and explicitly select labels so you know what's going on. If no reviewer appears after a week, a reminder will be sent out. |
Hi @biolypl , Thanks for reporting this issue. We have tested internally and the only way we can reproduce the Just to double confirm, is it possible to stop your forger process, configure your bip38 forger and start the forger process again please? Let us know the results, thanks! |
Hello, The only interesting thing I can add here is the situation after reinstall, set bip38 encryption, start forger (still no delegates loaded), stop forger, configure forger without encryption and forger starts with:
Where the delegates.json file is:
So I don't get why it runs 2 delegates. |
Should've been fixed in the latest devnet release from last week. Reopen if the issue still occurs when using the correct password. |
This issue has been closed. If you wish to re-open it please provide additional information. |
Expected Behavior
Command
ark forger:start
should decrypt the passphrase and run the forging plugin.Current Behavior
The command starts forging plugin with none delegate.
INFO : Loaded 1 inactive delegate:
Possible Solution
Steps to Reproduce (for bugs)
ark config:forger
Context
The issue hits me on fresh installed node (but synced). The encryption is correct (the same bip38 string in delegates.json as on my other nodes). Forging with plain text passphrase works on the node.
Your Environment
The text was updated successfully, but these errors were encountered: