zeekay
1b6e86a167
LUX_DECIMALS was 6 in four separate files, each dividing a value the code itself names nanoLux. Nano is 10^-9. Every staking and balance figure the Lux explorer rendered was inflated by 1000. The validators page reported 2,500,000,000,000 LUX staked — against a total supply of ~2T. An impossible number, and it is reached from lux.cloud's own "View on explorer" link: an investor reads 2.5B on the dashboard, clicks through, and sees 2.5T. lux.cloud was right; this was wrong. Verified against live chain state (platform.getCurrentValidators): 500000000000000000 nLUX -> 500,000,000 LUX per validator 2500000000000000000 nLUX -> 2,500,000,000 LUX total across 5 Four copies of one constant, so the bug shipped four times: ui/validators/lux/utils.ts · ui/chains/ChainDetailPage.tsx ui/pages/NetworkOverview.tsx · ui/stats/lux/NetworkStats.tsx Each still owns its own copy; they should share one, which is the follow-up. Typecheck shows no new errors in these files (the existing _app.tsx and *.pw.tsx failures predate this change).
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.