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

Not able to sync a viewing key that's not imported? #2876

Closed
zenodeapp opened this issue Mar 10, 2024 · 3 comments
Closed

Not able to sync a viewing key that's not imported? #2876

zenodeapp opened this issue Mar 10, 2024 · 3 comments
Labels

Comments

@zenodeapp
Copy link
Contributor

zenodeapp commented Mar 10, 2024

I really don't like to create so many issues.
But this comes from #2711, where I go through potential MASP improvements and have to treat the following as a separate issue.

Is the "issue" below a bug or expected behavior (or third, I screwed something up and it should've worked 😂?). If it's intended not to work, then it would save lots of time to not allow the sync in the first place.

[...] By the way, I tried to sync a viewing key I did not own in the CLI. This went through the whole chain, but as soon as I again ran the sync it started all over again! Isn't it possible to perform a shielded sync for a not imported viewing key? Asking this for trying to manoeuvre through the building of the IBC app. [...]

Originally posted by @zenodeapp in #2711 (comment)

@phy-chain
Copy link

Given the way the shielded context works, I would assume that this is normal. You can as many spending/view keys to your shielded context I think ? So if you sync for a specific key, the sync goes through the whole history, and gather data for that key, then add it to the context.

@cwgoes
Copy link
Contributor

cwgoes commented May 24, 2024

cc @batconjurer Is this particular issue fixed by your shielded sync work?

@cwgoes cwgoes added the client label May 24, 2024
@batconjurer
Copy link
Member

cc @batconjurer Is this particular issue fixed by your shielded sync work?

yes

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

5 participants