mirror of
https://github.com/luxfi/explore.git
synced 2026-09-24 00:28:18 +00:00
zeekayandHanzo Dev
521e47ab47
/validators reported "0 validators / 0 LUX staked" about a network running five with 2,500,000,000 LUX bonded. Measured now against the live P-Chain: POST https://api.lux.network/ext/bc/P platform.getCurrentValidators -> 5 validators, sum(weight) 2500000000000000000 nLUX = 2,500,000,000 LUX (P-chain figures are nLUX, 1e9 — and the rows carry `weight`, not `stakeAmount`, which is why the reader already falls back.) useCurrentValidators returns a ZEROED ValidatorStats when the query fails, and a zeroed stat is indistinguishable from a chain with no validators. NetworkOverview and NetworkStats each guarded against that with their own copy of `!isError && validatorCount > 0`; ValidatorsPage and ValidatorsDashboard had no guard at all, so they rendered the zeros — "Validators (0)", "Delegators (0)", "0 LUX Total Stake" — as if measured. The question "did the read answer?" now has exactly one answer, computed where the read happens: the hook exports `isKnown`. The two ad-hoc copies are gone and the two unguarded surfaces use it, showing an em dash and naming the method that did not answer. Also restores module resolution. 258bd1a48 dropped `baseUrl: "."` from tsconfig on the grounds that `paths` already covered it — but `paths` was `{}`, so baseUrl alone was resolving every absolute import in the repo ("configs/app", "lib/api/pchain", "ui/..."). Without it tsc could not resolve a single one. `"*": ["./*"]` is the same rule in the form TS7 accepts: tsc goes from thousands of TS2307 to 1. Co-authored-by: Hanzo Dev <[email protected]>