zeekayandHanzo Dev
930aedef05
zoo.exchange was pointing every cross-chain RPC at
api.zoo.exchange/ext/bc/{C,hanzo,pars}/rpc. /ext is gone from the
gateways (404) and api.zoo.exchange sends no CORS headers, so a browser
on zoo.exchange could not have read a response even at 200. Each org
answers on its own gateway at /v1/bc/C/rpc:
api.lux.network -> 0x17871 (96369)
api.hanzo.network -> 0x9063 (36963)
api.pars.network -> 0x78d65 (494949)
configmap-brand.yaml is newly tracked: it is the verbatim live
zoo-exchange-brand (mounted at /public/brand.json) with all 15 /ext
URLs rewritten the same way. The overlay had also drifted from the
cluster on image and volumes; it now renders exactly what runs.
api.avax.network keeps /ext — that is Avalanche's API and their path.
k8s/lux-mainnet: lux-frontend-{mainnet,zoo,hanzo,spc,pars} and their
frontend-config-* ConfigMaps have no counterpart in the cluster
(explore-fe-* replaced them) and were in no kustomization, so nothing
could have applied them except by hand — at which point they would
resurrect five orphan ConfigMaps carrying /mainnet/ext/ URLs. Removed
with the orphans they defined. indexer-config-mainnet stays.
Co-authored-by: Hanzo Dev <[email protected]>
18 lines
337 B
YAML
18 lines
337 B
YAML
---
|
|
# ConfigMap: Shared indexer configuration - Mainnet
|
|
apiVersion: v1
|
|
kind: ConfigMap
|
|
metadata:
|
|
name: indexer-config-mainnet
|
|
namespace: lux-mainnet
|
|
labels:
|
|
app: lux-indexer
|
|
network: mainnet
|
|
data:
|
|
CHAIN_TYPE: "cchain"
|
|
HTTP_PORT: "4000"
|
|
POLL_INTERVAL: "15s"
|
|
CHAIN_ID: "96369"
|
|
COIN_NAME: "LUX"
|
|
COIN_SYMBOL: "LUX"
|