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

Adapt Sedge to handle the current keystore format used by Charon #20

Open
3 tasks
boulder225 opened this issue May 21, 2024 · 1 comment
Open
3 tasks
Assignees
Labels

Comments

@boulder225
Copy link

boulder225 commented May 21, 2024

🎯 Problem to be solved

Sedge expects a specific keystore directory structure to import keys, which is different from the structure used by Charon. See: NethermindEth#368

It appears that the import process is working fine, but the provided keystore directory structure is not correct

🛠️ Proposed solution

  • Manually test the key import process by restructuring the keystore directory to match Sedge's expected format
  • If the manual test is successful, update Sedge to handle the current keystore format used by Charon
  • Alternatively, if the manual test fails, investigate and address any underlying issues with the key import process
@boulder225
Copy link
Author

Please add your planning poker estimate with Zenhub @sugh01

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants