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

feat(scanner): Read and store keys from config at zebra startup #7946

Closed
1 task
Tracked by #7728
oxarbitrage opened this issue Nov 15, 2023 · 1 comment · Fixed by #7989
Closed
1 task
Tracked by #7728

feat(scanner): Read and store keys from config at zebra startup #7946

oxarbitrage opened this issue Nov 15, 2023 · 1 comment · Fixed by #7989
Assignees
Labels
A-blockchain-scanner Area: Blockchain scanner of shielded transactions

Comments

@oxarbitrage
Copy link
Contributor

After we have a key storage and the keys in the config file we need to read them and add them to the database at zebra startup.

Tasks:

  • Create a Storage instance and add the config keys to it.

Blocked on #7941 and #7904

@oxarbitrage oxarbitrage added S-blocked Status: Blocked on other tasks P-Low ❄️ A-blockchain-scanner Area: Blockchain scanner of shielded transactions labels Nov 15, 2023
@mpguerra mpguerra added this to Zebra Nov 15, 2023
@github-project-automation github-project-automation bot moved this to 🆕 New in Zebra Nov 15, 2023
@mpguerra
Copy link
Contributor

Hey team! Please add your planning poker estimate with Zenhub @arya2 @oxarbitrage @teor2345 @upbqdn

@oxarbitrage oxarbitrage added P-Medium ⚡ and removed S-blocked Status: Blocked on other tasks P-Low ❄️ labels Nov 21, 2023
@mergify mergify bot closed this as completed in #7989 Nov 27, 2023
@github-project-automation github-project-automation bot moved this from 🆕 New to ✅ Done in Zebra Nov 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-blockchain-scanner Area: Blockchain scanner of shielded transactions
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants