lux/universe
2
0
Fork 0
Code Issues Pull Requests Releases Activity

Brand explorer pages say what their RPC is, now that zoo and hanzo answer

Browse Source 
Co-authored-by: Hanzo Dev <[email protected]>
This commit is contained in:
zeekay
2026-09-23 00:28:43 -07:00
co-authored by Hanzo Dev
parent 5079e447d3
commit 9137becf73
3 changed files with 6 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files
deploy/lux-mainnet/explore-fe-hanzo.yaml
+2 -8
View File
@@ -84,14 +84,8 @@ configMaps:
NEXT_PUBLIC_NETWORK_CURRENCY_NAME: HANZO
NEXT_PUBLIC_NETWORK_CURRENCY_SYMBOL: HANZO
NEXT_PUBLIC_NETWORK_CURRENCY_DECIMALS: '18'
# This chain's own RPC, and not Lux's. All four brands named
# api.lux.network/v1/chain/c/rpc while declaring their own chain id and
# ticker, so each page served Lux C-Chain blocks relabelled: zoo, pars and
# spc all showed block 59, miner 0xf66b0259..., as ZOO, PARS and SPC.
# Presenting another chain's transactions as your own is worse than
# presenting none. None of these four answer yet -- the chains are not up --
# so the page shows nothing, which is the truth, and starts working the day
# the chain does without another edit here.
# This chain's own RPC, never another brand's: the page shows only the
# chain it names.
NEXT_PUBLIC_NETWORK_RPC_URL: https://api.hanzo.network/v1/chain/c/rpc
NEXT_PUBLIC_API_HOST: api-explore.lux.network
NEXT_PUBLIC_API_PROTOCOL: https
deploy/lux-mainnet/explore-fe-pars.yaml
+2 -8
View File
@@ -79,14 +79,8 @@ configMaps:
NEXT_PUBLIC_NETWORK_CURRENCY_NAME: PARS
NEXT_PUBLIC_NETWORK_CURRENCY_SYMBOL: PARS
NEXT_PUBLIC_NETWORK_CURRENCY_DECIMALS: '18'
# This chain's own RPC, and not Lux's. All four brands named
# api.lux.network/v1/chain/c/rpc while declaring their own chain id and
# ticker, so each page served Lux C-Chain blocks relabelled: zoo, pars and
# spc all showed block 59, miner 0xf66b0259..., as ZOO, PARS and SPC.
# Presenting another chain's transactions as your own is worse than
# presenting none. None of these four answer yet -- the chains are not up --
# so the page shows nothing, which is the truth, and starts working the day
# the chain does without another edit here.
# This chain's own RPC, never another brand's: the page shows only the
# chain it names, and Pars has no node yet, so it shows nothing.
NEXT_PUBLIC_NETWORK_RPC_URL: https://api.pars.network/v1/chain/pars
NEXT_PUBLIC_API_HOST: api-explore.lux.network
NEXT_PUBLIC_API_PROTOCOL: https
deploy/lux-mainnet/explore-fe-zoo.yaml
+2 -8
View File
@@ -84,14 +84,8 @@ configMaps:
NEXT_PUBLIC_NETWORK_CURRENCY_NAME: ZOO
NEXT_PUBLIC_NETWORK_CURRENCY_SYMBOL: ZOO
NEXT_PUBLIC_NETWORK_CURRENCY_DECIMALS: '18'
# This chain's own RPC, and not Lux's. All four brands named
# api.lux.network/v1/chain/c/rpc while declaring their own chain id and
# ticker, so each page served Lux C-Chain blocks relabelled: zoo, pars and
# spc all showed block 59, miner 0xf66b0259..., as ZOO, PARS and SPC.
# Presenting another chain's transactions as your own is worse than
# presenting none. None of these four answer yet -- the chains are not up --
# so the page shows nothing, which is the truth, and starts working the day
# the chain does without another edit here.
# This chain's own RPC, never another brand's: the page shows only the
# chain it names.
NEXT_PUBLIC_NETWORK_RPC_URL: https://api.zoo.network/v1/chain/c/rpc
NEXT_PUBLIC_API_HOST: api-explore.lux.network
NEXT_PUBLIC_API_PROTOCOL: https