Fetching shielded balance via SDK nor extension working

[zenodeapp]

Hey,

Whenever I attempt to query a shielded balance for a viewing key via the SDK, I get just a lot of POST request to my rpc endpoint. This just continue to go on. While I don't mind to wait whether it will actually result in something, this will definitely not be feasible for a multiple user front-end.

The extension way gives a:
Error: No results have been found on Vault-error.

Again, this is probably due to the current shielded-sync approach and you guys are likely working at it. But wanted to express this as to see whether it's a me-problem or a common one amongst us all.

ZEN

[zenodeapp]

Close this asap if it's already a known issue. Don't wanna let the issues tab become bloated like the main namada-repository 😅.

[thousandsofthem]

Extension without balances is pretty useless, if i can't see own balance then i can't use shielded transactions. Don't work for me as well

[pnam1609]

Now, SE network have 190k block and spend more than 2 day can shielded sync. So i tried reduce time fetching MASP. This is my PR: #667. And i still working on it

[mateuszjasiuk]

Hello. To give you more context about the issue. The problem is that atm we have to query each block to produce shielded context which takes a long time. For SE, as of now, it means querying 160 000 blocks. If you use interface(namada.me) this won't work as we timeout query function after some time(there was a reason for that which is not really that important to this conversation :)).

What is more:

• if you did not do any shileding/unshielding this means querying 160 000 blocks each time as context is only saved when it detects some change in relation to viewing keys that you provided. This also means that once you add another shielded account you have to query everything from the beginning
• if you made shielding transfer at block 100 000, and once you fetched shielded context, this means that every next shielded context fetch will start from block 100 000
• currently published extension uses Namada SDK in version 0.31.8 which is outdated and some of the functionalities might not work with the SE

Upsides:

• we have a 0.32.0 bump PR which removes the timeout for query_balance
• there was a recent change to the Namada SDK which allows you to pass a block index that is a starting index of the shielded context fetch, which allows to write some improvements, like storing index of last fetched block in frontend or whatnot

[zenodeapp]

Hello. To give you more context about the issue. The problem is that atm we have to query each block to produce shielded context which takes a long time. For SE, as of now, it means querying 160 000 blocks. If you use interface(namada.me) this won't work as we timeout query function after some time(there was a reason for that which is not really that important to this conversation :)).

What is more:

• if you did not do any shileding/unshielding this means querying 160 000 blocks each time as context is only saved when it detects some change in relation to viewing keys that you provided. This also means that once you add another shielded account you have to query everything from the beginning
• if you made shielding transfer at block 100 000, and once you fetched shielded context, this means that every next shielded context fetch will start from block 100 000
• currently published extension uses Namada SDK in version 0.31.8 which is outdated and some of the functionalities might not work with the SE

Upsides:

• we have a 0.32.0 bump PR which removes the timeout for query_balance
• there was a recent change to the Namada SDK which allows you to pass a block index that is a starting index of the shielded context fetch, which allows to write some improvements, like storing index of last fetched block in frontend or whatnot

Hey thanks for this update and thorough description! I'll check this out at the end of this week and see what I can do to get something working with the current state of the SDK!

[jurevans]

@zenodeapp Hello! Just FYI - I'm closing this issue as we're revamping shielded balances right now. Thanks!