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

Hotfix transparent viewkey missing #825

Conversation

fluidvanadium
Copy link
Contributor

includes test that covers

@fluidvanadium
Copy link
Contributor Author

ignore the clippy here. its updated in dev but not worth hotfixing

@fluidvanadium fluidvanadium force-pushed the hotfix_transparent_viewkey_missing branch from 6ed461b to bfb2239 Compare March 7, 2024 20:21
Copy link
Contributor

@juanky201271 juanky201271 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My concern about this is:

  • A user can restore from vk, and after that when the user wants to check the vk, the App shows up an error message?
  • Restore from ufvk & exportufvk would have to be synchronize, right? both with an error message or not, something coherent.

@fluidvanadium
Copy link
Contributor Author

right o. the new version should export the transparentless viewkey

@fluidvanadium
Copy link
Contributor Author

addresses the panic on line 179 of unified.rs

Oscar-Pepper
Oscar-Pepper previously approved these changes Mar 8, 2024
Copy link
Contributor

@Oscar-Pepper Oscar-Pepper left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

great job

@Oscar-Pepper Oscar-Pepper merged commit 0d2d458 into zingolabs:stable Mar 8, 2024
16 checks passed
@juanky201271
Copy link
Contributor

right o. the new version should export the transparentless viewkey

Thanks, I appreciated that.

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 this pull request may close these issues.

3 participants