zeekayandHanzo Dev
8901706f59
Three UI-correctness fixes surfaced by visual inspection of explore.lux.network: - DetailedInfo (block/tx/address detail pages): every field label + value rendered white-on-white because the grid inherited the @luxfi/ui Tamagui `t_dark` theme color while the page is in light mode. The two most-used drill-downs were unreadable. Anchor the container to --color-text-primary and labels to --color-text-secondary so text follows the app color mode instead of the stray Tamagui theme. - StatsWidget (home metric cards): the value had no explicit color and inherited the same Tamagui white -> near-invisible "Total blocks / transactions / addresses". Anchor to --color-text-primary. - Validators dashboard + Network Overview: dropped the "Connected" (0/5) and "Avg Uptime" (0.0%) widgets/columns. platform.getCurrentValidators reports connected=null and uptime=0 for every validator on the public RPC (the API node does not track peer uptime), so those numbers were fabricated-looking zeros. Only chain-verifiable metrics (count, stake, delegation fee, delegators) remain -- real data, no fake numbers. Co-authored-by: Hanzo Dev <[email protected]>
DEPRECATED — see ~/work/lux/explorer/
The standalone Next.js frontend in this repo is no longer deployed. Its build output is embedded directly into the Lux Explorer Go binary (
ghcr.io/luxfi/explorer:1.2.1) viago:embed. Run that single binary in production.This repo is preserved as the source of the embedded SPA assets. Updates to the UI ship via a rebuild of the explorer image, not by deploying this Next.js app separately.
Canonical deploy:
~/work/lux/explorer/(Go binary, single process, indexer + GraphQL + SPA, port 8090).
Lux Explore frontend (legacy)
Frontend application for Lux Network blockchain explorer
Running and configuring the app
App is distributed as a docker image. Here you can find information about the package and its recent releases.
You can configure your app by passing necessary environment variables when starting the container. See full list of ENVs and their description here.
docker run -p 3000:3000 --env-file <path-to-your-env-file> ghcr.io/blockscout/frontend:latest
Alternatively, you can build your own docker image and run your app from that. Please follow this guide.
For more information on migrating from the previous frontend, please see the frontend migration docs.
Contributing
See our Contribution guide for pull request protocol. We expect contributors to follow our code of conduct when submitting code or comments.
Resources
- App ENVs list
- Contribution guide
- Making a custom build
- Frontend migration guide
- Manual deployment guide with backend and microservices
License
This project is licensed under the GNU General Public License v3.0. See the LICENSE file for details.