#still not showing
blazing kindle
going to need some screenshots and info on which namadillo urls you have tried this on.
there may be some response time from our end atm
viscid saddle
tx hash of IBC shield: 914FA9420741D8B757A98205E7DC23047CCE57CE20E5E666AB08DAD86C482A8B
blazing kindle
tx hash of IBC shield: 914FA9420741D8B757A98205E7DC23047CCE57CE20E5E666AB08DAD86...
is that a noble hash?
blazing kindle
do you have several namada wallets/accounts? could you have shielded into one of your other account pairs?
blazing kindle
as I think possibly that history tx is taken from your noble tx history (ie connected keplr wallet) though not 100% on that
blazing kindle
I thought about that cause I do
maybe go through all of them to make sure you are not looking at the wrong one
when you switch the active account in the namada extension with namadillo open, the active account in namadillo changes automatically and resyncs
blazing kindle
will need to look a bit more into this and maybe ping a few others. can't do anything more about it right now but will get back.
viscid saddle
thanks
viscid saddle
I'm trying to use the namada CLI tools now to see if the balance is there. I importd the shielded viewing key and amd doing namadac shielded-sync but it only get as far as 37% fetched
$ namadac shielded-sync
==== Shielded sync started using ledger client ====
fetched : 37%|█████████████████████████████████████████████████████▅ | 1400416/3768606 [00:57<01:36, 24442.15it/s]
scanned : 100%|██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 10326/10326 [00:57<00:00, 180.22it/s]
applied : 0it [00:00, ?it/s]
viscid saddle
I restarted my computer and now it isn't showoing the IBC shield transfer anymore
This is just FYI. Get to it when you can
viscid saddle
Whenever you get around, I can supply you with the viewing key in case you want to check if the USDC address has any funds. namadac keeps halting at 37% on my node.
I'm done for the night
blazing kindle
$ namadac shielded-sync
==== Shielded sync started using ledger client ====
fet...
you can try using a masp indexer, it's a bit wonky with the syntax but lmk if you want to try
hey, I see in mainnet channel it's been noted many masp indexers are stuck on a certain block height, I'm guessing our culprit is there and your funds are actually in wallet - will follow up asap.
if you feel adventurous, you could try and set manually one of the masp indexers said to be working here: #🚀-mainnet-operations message
blazing kindle
indexer urls at namada.community under ecosystem and infra
viscid saddle
Used Denodes from here: https://docs.google.com/spreadsheets/d/1wTBd5qpk5Y-TnQM-C08vSyJ2P_9NxeErskt290hM2mI/edit?gid=874284933#gid=874284933
that was the issue
Thanks for your patience
although i just notice. I have no idea why it says I have 13K NAM
Should only be 4k
blazing kindle
someone else said denodes displayed a bunch of random balances
don't trust it atm
blazing kindle
you can try one of the other two mentioned above, but tbh I think the masp indexers still alive may have issues of their own
viscid saddle
Okay. Is there documentation on running an indexer. I work with freQniK from MathNodes, he is a validator on Namada and we wouldn't mind running some infra for Namada in the future. We are actually in talks with a group to setup a relayer between Sentinel and Namada
anyway. thanks again. I'll look around while things get fixed
blazing kindle
Okay. Is there documentation on running an indexer. I work with freQniK from Mat...
this seems to be a bug in the indexer which a community member has already provided a fix for
running your own indexer wouldn't make any difference
that being said, running your own indexer should not be that hard, I believe docu is in the respective repos under namada-net on github
blazing kindle
hey? think it's been fixed now, please confirm (namadillo.app or 5elements)
viscid saddle
can confirm