Disappearing shielded balance

[mateuszjasiuk]

@mateuszjasiuk

I encountered another issue while trying to play with this. For some reason, I lost some shielded NAM—it just vanished after resyncing the MASP.

Here’s what happened:

After shielding 400 NAM, it showed up in the MASP. However, after resyncing the MASP, the shielded NAM disappeared.

I then shielded another 100 NAM, which successfully appeared in the MASP. But after resyncing the MASP again, the 100 NAM also disappeared.

Finally, I shielded 50 NAM, and it successfully showed up in the MASP.

The transaction history shows correct and complete information for all these transactions. Please see the attached images for reference.

I waited 12 hours before reporting this just to be sure its not about time

are you aware of this behavour ? do i have to open an issue for this ?

Originally posted by @msobh13 in #1504

[mateuszjasiuk]

@msobh13
Can you try to go to Settings(Gear Icon) -> Masp and click Invalidate Shielded Context? Also once shielded context is constructed again please try refreshing page, we are still fixing some bugs here and there.

[msobh13]

@mateuszjasiuk i have been doing this since starting of this issue and thats why i gave it some times .. so yes to confirm i have tried this more than 5 times or even more . still same issue

[mateuszjasiuk]

Right, do you know how to query balance using the cli? I would like to check tha both namadillo and cli return different values.
Also, are you testing against campfire testnet?

[msobh13]

now after Invalidate Shielded Context the 50 NAM are gone as well . refreshed the page and waited like 15 mins, same issue

Namadillo Version: 1.4.0 Revision: SDK Version: 0.14.0

viewking key still the same before and after Invalidate Shielded Context . shielded addr still the same as well

attached 2 imges with 2 epoch

[mateuszjasiuk]

I can try to debug it if you give me your viewing key and tell which network are you testing.

[msobh13]

yes i am testing using
https://interface.campfire.tududes.com/ with dfeault indexers value see attached file

i am testing the cli now . and here is the viewing key
zvknam1qdxykae5qqqqpqy3577amz93am2aeskdakuw3e4udhyq3yrd3rvqchtt77f0nea25pe34fwcz6awtzs28kesgke6j6jrcseay3tf3n58uyymauw4uujrv2pdmnyr0qp8s5n3gj8zwz4asvmr057zd9zawdc4s5z8y9efzsuqz7mpn9jlqrtzxcxkhu9m2kd4jqr28fqe8ekql7lyvgshpd2del7tzzlcs9q6deuxvpt7e98c03qjcqqcl5c8xgpy2y7q9qey4mfhfqc57wmck

[msobh13]

even when using cli , still same issue

m@node:~$ namadac balance  --owner test01  --token NAM  --node https://rpc.campfire.tududes.com:443  --chain-id campfire-square.ff09671d333707
WARNING: The resulting balance could be outdated, make sure to run `namadac shielded-sync` before querying the balance to get the most recent value.

Last committed masp epoch: 618
nam: 0
m@node:~$ namadac shielded-sync  --node https://rpc.campfire.tududes.com:443  --chain-id campfire-square.ff09671d333707
==== Shielded sync started using ledger client ====

fetched : 100%|████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 282167/282167 [12:48<00:00, 366.96it/s]
scanned : 100%|████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 264/264 [12:43<00:00, 0.35it/s]
applied : 0it [00:00, ?it/s]

Syncing finished
m@node:~$ namadac balance  --owner test01  --token NAM  --node https://rpc.campfire.tududes.com:443  --chain-id campfire-square.ff09671d333707
WARNING: The resulting balance could be outdated, make sure to run `namadac shielded-sync` before querying the balance to get the most recent value.

Last committed masp epoch: 618
nam: 0

[mateuszjasiuk]

Does this looks correct?

➜  namada git:(main) ✗ target/debug/namada client balance --owner zvknam1qdxykae5qqqqpqy3577amz93am2aeskdakuw3e4udhyq3yrd3rvqchtt77f0ne
a25pe34fwcz6awtzs28kesgke6j6jrcseay3tf3n58uyymauw4uujrv2pdmnyr0qp8s5n3gj8zwz4asvmr057zd9zawdc4s5z8y9efzsuqz7mpn9jlqrtzxcxkhu9m2kd4jqr28
fqe8ekql7lyvgshpd2del7tzzlcs9q6deuxvpt7e98c03qjcqqcl5c8xgpy2y7q9qey4mfhfqc57wmck --token tnam1qy440ynh9fwrx8aewjvvmu38zxqgukgc259fzp6h 
--base-dir .namada/validator-0 --node https://rpc.campfire.tududes.com:443
WARNING: The resulting balance could be outdated, make sure to run `namadac shielded-sync` before querying the balance to get the most 
recent value.

Last committed masp epoch: 619
converting current asset type to latest asset type...
converting current asset type to latest asset type...
tnam1qy440ynh9fwrx8aewjvvmu38zxqgukgc259fzp6h: 541.88

[msobh13]

yes this should be the Shielded balance !.. what was the issue ?

[mateuszjasiuk]

I don't know yet, I could check namadillo if you are willing to share mnemonic.

EDIT:
I think CLI should work fine. You can try couple of things:

• checking if aliases for nam and owner are correct in the wallet.toml
• you can also try to remove shielded* files in the basedir and try shielded sync again

[msobh13]

seed phrase ( its just test account np )

unhappy pact breeze story often bird curious heavy genuine clip pull dose

[mateuszjasiuk]

I was able to see it after clearing the context.

There is a bug that we still have to resolve, though. Do you by any chance have two different accounts with the same alias?

[msobh13]

Do you by any chance have two different accounts with the same alias? Nope

[mateuszjasiuk]

I do not have any more quick ideas for now unfortunately. I will keep you posted.

[msobh13]

Thank you , will just wait for namadillo to be fixed then.

[euharrison]

Not sure if it's helpful, but I'm testing the shielded sync now and the masp indexer is hanging forever

[euharrison]

I cleared the shielded context and the issue was gone 👍