zeekayandHanzo Dev
e53f9cd22f
chainId reconciliation (registry = live chains = genesis LP-018 map, one way): - Pars mainnet 7070 -> 494949 (live api.pars.network eth_chainId=0x78d65, net_version=494949); Pars testnet 7071 -> 494950, devnet 7072 -> 494951 (matches genesis configs/lp182_chain_id_map.go 4949xx scheme). - Lux devnet 96370 -> 96367 (live api.lux-dev.network reports 96367). - chainRegistry.spec.ts now asserts Pars 494949 (was stale-7070 assert). - Also fixed: configmap-mainnet Pars NETWORK_ID, configmap-testnet Pars NETWORK_ID, branded_build.sh, tools/send_test_txs.py, well-known/explore.json (regenerated from the fixed registry). RPC /ext/bc/<alias>/rpc -> /v1/bc/C/rpc (gateway canonical; each sovereign L1 serves its own C-Chain at /v1/bc/C/rpc). Verified returning blocks before switch: Lux/Zoo/Hanzo/Pars mainnet + Lux testnet. Kept on /ext (their /v1 not up yet): Lux devnet, brand testnets, local-node compose/test-tool URLs. P-chain proxy now dials /v1/bc/P. useChainHeights + luxnet/instance no longer strip /ext/bc/C/rpc; they use the env RPC URL / origin directly so C-chain height + luxnet SDK work under /v1. 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.