Namadillo UI possible bug

[buoyant garden]

Mate, please restate your problem a bit more precisely. What errors are you getting? Screenshots would be helpful

It's christmas, so expect a bit more response time than usual

[kind badge]

Right I've sent screenshots to gavins dm as he is the only guy that's trusted in announcement channel

I'm getting no errors but when I sign in to namadillo via keychain I can only see 89% of my tokens staked

I can only see 30 of my staked validators being registered by namadillo

I have 4 missing validators that I can see on the valopers block explorer that shows correct balances and validators

Why will it not show on namadillo because I can't control the 11% staked to the missing validators until namadillo registers them

@buoyant garden I'm going to forward all the stuff I sent Gavin to your dm

@buoyant garden sent all info,block explorer link and screenshots you requested are all in your dm

[buoyant garden]

mate, we don't do support in dms, and gavin certainly does not do support. please post you screenshots here

[kind badge]

The screenshots I sent have balances to be compared which I wish to keep private and not hash out in a public chat for security reasons which is why I suggested dm.

To put simply publicly so you can understand

1. Valopers Explorer shows my full 34 validators delegated and correct amounts (I've redacted screnshots with amounts for security)

2. Namadillo shows/counts only 30 validators

3. The 4 missing are: Tdrsys,coverlet, anodofzen,prodelegators

TdrSys staked and visible ( showing on-chain explorer) → but 0 NAM shown in Namadillo

· coverlet — staked and visible (on-chain explorer) → but 0 NAM shown in Namadillo

anodeofzen - staked and visible (on chain explorer - but 0 NAM shown in Namadillo

Pro Delagators - staked and visible (on chain explorer) but 0 NAM shown in namadillo.

Pattern: 34 delegated can see on block explorer but only 30 validators/amounts visible on namadillo.

Impact: ~11% of my stake inaccessible for management as can only do through namadillo (cannot use explorer to unstake) can only read 30 of my validators when explorer says I have 34.

Is there a 30 validator management limit for namadillo and if so is there a workaround/how do I unlock the validators that namidillo can't see/ isn't showing but valopers explorer can see / isnt showing ?

[buoyant garden]

I saw the posts you tried to make that were rejected labeled "eargent bug" and similar. I have not been able to verify if this UI bug is present, but if so, it is as you say only an UI bug in Namadillo, and not an issue with the stakes on-chain. What are you wanting to do with those stakes?

Obviously it needs to be fixed, but not sure it will have high priority with the things going on with the protocol atm. If you need to perform operations, cli is always possible as a last resort.

Namadillo UI possible bug

[kind badge]

Thanks for responding.

At present I don't need to do anything with the stakes

However in future I may need to redelegate stakes or undelegate move NAM for defi / bridge / LP / shielding purposes.

Id say the bug is of critical importance as 11% of my staked NAM is unmanageable/invisible on UI in Namadillo (due to the 4 validators missing from namadillo only 30 being counted/displayed/manageable in UI).

Questions:

1. Can you confirm if there is 30-validator UI limit or it should be higher, if so why are people allowed to delegate more than 30 validators if the UI can't handle it?

2. When will this be fixed? It blocks critical DeFi ops.

3. CLI commands to list all delegations and redelegate would help for sure, but are less than ideal.

Also a few ideas that could make situations like this more workable..

· as far as I know there is no backup/alternative GUI or block explorer to manage delegations in case of namadillo UI bug (this would help exactly for situations like this as CLI should not be necessary)

This also creates involuntary lock-up of assets

At present this UI is key infrastructure for power ecosystem users.

Do you have any ETA?

[buoyant garden]

1. it's not critical, in the proper understanding of the term.
2. as I said I can't confirm or verify anything, but I wouldn't be surprised if such bugs could exist (again, they're display bugs not affecting the state of you actual stake on-chain)
3. If you have submitted a github issue, that should be enough for it to be picked up by devs.
4. you have cli as an option to engage with this stake at will.
5. no eta on fix. as I said a lot going on with protocol atm, and I expect a lot of things are on hold rn while they get resolved (see latest bonfire and validator circle)
6. If you were actually needing to do something here, we would obviously help you with the cli commands if time-critical for you. the commands are fairly trivial.

[kind badge]

For anyone in the community who is building a backup interface for management would be a smart move as namadillo UI is a single point of failure until we have backup explorers/interfaces

[buoyant garden]

also, re alternate interfaces, you could try omniflix, but I'm not sure how well it's maintained atm. I don't know of any alternate interfaces being developed

tagging @dark anchor if he has more to add (or correct me) but don't necessarily expect a response from him.

[kind badge]

I understand the distinction between UI and on-chain state.

However, calling this 'just a display bug' minimizes its real impact:

1. It's a critical UX failure – Users cannot manage 11% of their staked assets through the primary interface

2. There's no functional backup – Unlike other chains, Namada has no alternative GUI or block explorer for delegation management

3. CLI is not a solution for most users – It excludes non-technical users and creates a single point of failure

This isn't about my immediate needs – it's about Namada's readiness for mainstream DeFi adoption which is everything.

If power users can't reliably manage staked assets, how will the protocol scale?

Since there's no ETA, please share the CLI commands now so I at least have a workaround while waiting indefinitely.

Also, can you confirm whether the GitHub issue has been triaged?

[buoyant garden]

I'm not wanting to be dismissive of the issue being a problem btw, but I also want you to have realistic expectations here.

[kind badge]

I understand brother I'm in it for the long haul and I just want to see this chain win

I can really see it's potential to plug privacy in anywhere

Ironing out important things like this sets the wheels in motion

[buoyant garden]

I have not come across this issue before, so pretty sure it's not widespread. If it's due to number of validators staked, I can't speculate, but first time I've heard of this being an issue.

And yes, there is a backup which works - CLI.

Bottom line is, I don't believe this is in any way a critical issue, and I'm fairly sure it would not be treated as such. (In a normal environment it would probably be grabbed rather quickly, but atm things are not in a normal operational environment and we should not expect things to be "as usual" rn)

(again for further context, see remarks in latest validator circle and community bonfire)

[kind badge]

All good now I think the only solution is to unstake the 11% from the invisible validators that aren't showing on namadillo via CLI as there is no eta on a fix

[buoyant garden]

You are free to do so. However it really does not make any difference if you do that now via CLI or at the time when you would otherwise unstake.. (there is nothing "wrong" with your stakes..)

Also, it's not accurate that most users can't manage 11% of their stake - in your particular case it's (probably) not possible. Again I'm not sure why that is, but certain it's not the case for most users' stakes

You could try another Namadillo instance like 5elements or emberstake and see if that makes any difference (would be interested to know).

assuming you are using namadillo.app atm?

[kind badge]

Just to be clear: it's not about '11% of my stake' forget the number it's about 4 validators (which make up the 11%) being completely missing (unmanageable,uncounted) from the namadillo UI due to what appears to be a 30-validator display limit.

This will likely affect any user delegating to more than 30 validators as the ecosystem grows.

[buoyant garden]

Yes, I understand

Not saying it shouldn't get fixed, but also saying it very likely won't get prio atm.

i've flagged this for devs just for good measure

[kind badge]

However I can see all the 34 validated and staked with correct numbers on the namada valopers explorer

All a dev needs to do is go into the namadillo UI code and increase the limit that's in there so it displays all validators

The explorer UI has no issue whatsoever but unfortunately can't manage through explorer

[buoyant garden]

the explorer and namadillo are two very different things

[kind badge]

Thank you for listening and acknowledging the bug, the question is do I remove manually with CLI or do I wait for a fix

I will probably leave staked for months lol

[buoyant garden]

my recommendation: no need to do anything with cli until you would otherwise

nfa lol

like there is literally no reason to invoke cli before you have to

[kind badge]

So in other words you guys are aware and it will get fixed eventually

And by the time I need to access it CLI won't be necessary because you guys will prob fix it within weeks/months?

[buoyant garden]

mate, I have no concrete info beyond what i've said above. and I don't believe this to be a known issue before you brought it up.

[kind badge]

Got it. I'll leave the stakes as is and wait for the UI fix.

If when the time comes that I need to rebalance or exit and the bug still hasn't been fixed, I'll reach out for CLI commands then.

Appreciate the clarity.

[worthy pier]

Try to restake 4 or 5 validator to one and make it below 30 for now ?

[crisp cosmos]

Hey @kind badge, can you try with https://namadillo.5elementsnodes.com/ and let me know if you are able to see all your delegation? 🤞

[kind badge]

It works man can see it all, your version is superior

Thank you!

[crisp cosmos]

Great, I’ll open a PR to address this globally. Thanks for the feedback.