[Critical Frontend Bug] Namada Keychain + Namadillo UI mismatch: ~11% of staked NAM missing from namadillo staking/unstaking interface but present on explorer

[BlackWolf1321]

What happened?

Hi Namada Team,

I've encountered a critical frontend data-fetching bug where the Namadillo interface (app.namada.net) fails to display a significant portion of my staked NAM when using the Namada Keychain extension, preventing management of those funds.

Problem Description

· Blockchain state (source of truth): Correctly shows full delegation amounts across all validators for my address via explorer.

· Namadillo UI + Namada Keychain: The namadillo staking / unstaking interface displays only ~89% of my total staked balance.

· Impact: Approximately 11% of my total staked NAM is invisible/unmanageable through the primary namadillo interface—effectively locked from user control despite being properly staked/delagated on-chain.

Expected Behavior

The UI should reflect 100% of on-chain delegations, matching explorer data.

Technical Evidence (sent Gavin a dm on discord)

· Public address for verification

· Explorer confirmation: Full delegation breakdown visible at explorer link I dmed to Gavin

· Wallet: Namada Keychain browser extension latest

· UI screenshot available in Gavin's discord Dm or upon request showing the discrepancy between explorer totals and interface display.

Severity Assessment

High/Critical - This is a funds access and user sovereignty issue affecting users of the native Namada Keychain wallet.

A substantial portion of user stakes cannot be unstaked, redelegated, or managed through the official interface, creating functional illiquidity without proper unbonding initiation.

Steps to Reproduce

stake to a lot of different validators at once and it may glitch out mine froze today i noticed after adding more stakes to multiple validators

Relevant log output

Debug Information

## Navigator
------------------
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36
Screen Resolution: 1920px x 959px / DPI: 1
Sat Dec 27 2025 23:55:16 GMT+0000 (Greenwich Mean Time)

## Version Info
------------------
Namadillo Version: 1.33.0
SDK Version: 0.22.0
Keychain Version: 0.9.0
Indexer Version: 4.1.0
Masp Indexer Version: 1.4.7

## MASP Status
------------------
MASP Indexer URL: undefined
Last Shielded Sync: Sat Dec 27 2025 23:59:25 GMT+0000 (Greenwich Mean Time)
Is Shielded Sync complete? Yes

## Indexer Status
------------------
Indexer URL: 
Epoch: 1555
Block height: 4824722
Crawler Info: [{"name":"chain","timestamp":1766879964,"lastProcessedBlockHeight":4824722},{"name":"governance","timestamp":1766879963,"lastProcessedBlockHeight":null},{"name":"parameters","timestamp":1766879963,"lastProcessedBlockHeight":null},{"name":"pos","timestamp":1766879964,"lastProcessedBlockHeight":null},{"name":"rewards","timestamp":1766879963,"lastProcessedBlockHeight":null},{"name":"transactions","timestamp":1766879961,"lastProcessedBlockHeight":4824722}]

## Other Info
------------------
RPC Url: undefined
Account type: mnemonic

[h3ll0ofr1end]

Hello Team,

We identified an issue in the data retrieval flow that could result in incomplete results being returned in the “My Validators” view under certain conditions.
A candidate fix is ready, implementing proper pagination handling in the affected module, and currently running in production at https://namadillo.5elementsnodes.com/

Please let us know when to proceed with a PR.
@mateuszjasiuk

[mateuszjasiuk]

@h3ll0ofr1end I'm not involved in development anymore. Pinging @jurevans