Namadillo Status Indicator conflates RPC and Indexer status

[Rigorously]

The Status Indicator label says "Fully synced" when the RPC node is caught up, but the height and epoch are taken from the Namada Indexer, which can be inactive or catching up while the RPC is still running and caught up.

[euharrison]

Hi @Rigorously , thanks for your report :)

Do you mind sharing the RPC url and the Indexer url that you used on this test?

I'm trying to simulate it using a local chain and faking an Indexer url using the same RPC url (because both has the /health endpoint returning 200) but the Status Indicator is red with the message Error syncing

[Rigorously]

This was observed with Housefire.

https://interface.knowable.run
https://indexer.knowable.run:443
https://rpc.knowable.run:443

Knowable's indexer was lagging behind, while their RPC was up-to-date. That caused transactions to succeed, but the interface would not update due to the stale status of the indexer. See also the report on Discord starting here: https://discord.com/channels/833618405537218590/1197556681366831134/1292088500677509150

[euharrison]

Thanks for the details

I believe we'll need to query epoch from both endpoints, the indexer and the rpc, then compare them to confirm if they are fully synced