Files
zeekay 51460827d4 Merge the forge's lux/universe into GitHub's, the one main from here
The two mains shared no history, so this is a per-file three-way merge:
for each file the 65 forge-only commits touched (by patch-id), the base is
the newest version both histories held. 105 files merged or took one side
cleanly, 48 were already identical, and the 45 true conflicts and 31
modify/delete pairs were resolved by what runs on the cluster:

- The forge wins where it is live: explorer 1.5.56 (digest 45db11ff) and
  its archive readers, explore-fe-hanzo's ConfigMap env (AI coin,
  /v1/indexer/hanzo, /v1/chain/hanzo/rpc), exchange-api reading
  luxd-archive, and explore-fe-{lux,zoo}-testnet, pinned to what they run
  (v2.8.5-lux / v2.8.4-lux).
- GitHub wins where it is live: explore-fe-lux v2.8.5-lux, explore-fe-zoo
  v2.8.4-lux, bankd v1.0.18, lux-build's routes.
- The forge's retirement of workloads that run nowhere stands: lux-mainnet
  dex, lux-hb2, lux-market, traffic, wallet-web; the lux-testnet frontends,
  indexer, exchange and gateways; lux-operator. deploy/lux-testnet/luxd.yaml
  stays, since roll_luxd.sh reads it.
- GitHub's deletions stand: lux-finance and lux-financial (static sites
  now), the k8s/ operator manifests, .hanzo/workflows/cicd.yml.
- Paths are /v1/chain/C/rpc where the forge had written /v1/chain/c. All
  four spellings answer; this one is the documented form. The forge's
  /{network}/v1 doc lines are dropped: a network is a host, and the prefix
  404s.

Dry-run against the running objects (server-side, as CD applies), the
merged explorer shows no change where GitHub's showed 152 lines, and no
other live workload moves further from what runs. Every deploy/*/*.yaml
renders with charts/app; price.yaml, which failed on GitHub, now renders.

Claude-Session: https://claude.ai/code/session_01TzirYkGmD88w4GipqivUtV
2026-09-23 20:20:03 -07:00

220 lines
7.6 KiB
YAML

# Lux Ecosystem Network Registry
# CONFIDENTIAL — ~/work/lux/universe (private, not public OSS)
# Source of truth for all network/chain/coin mappings
# Last updated: 2026-03-24
# ═══════════════════════════════════════════════════════════════════════
# Lux Network (L0 Primary Network)
# ═══════════════════════════════════════════════════════════════════════
lux:
name: "Lux Network"
type: primary
network_ids: { mainnet: 1, testnet: 2, devnet: 3 }
coin: LUX
website: lux.network
exchange: lux.exchange
explorer: explore.lux.network
api: api.lux.network
# Primary Network chains (built into every node)
chains:
c-chain:
name: "C-Chain"
vm: cchainvm (EVM)
chain_ids: { mainnet: 96369, testnet: 96368, devnet: 96367 }
purpose: "EVM smart contracts, DeFi"
x-chain:
name: "X-Chain"
vm: xvm (DAG)
purpose: "Asset transfers, UTXO"
p-chain:
name: "P-Chain"
vm: platformvm
purpose: "Validators, staking, app chain EVM provisioning"
d-chain:
name: "D-Chain"
vm: dexvm
purpose: "Native DEX chain (orderbook + AMM)"
status: built, not yet deployed
b-chain:
name: "B-Chain"
vm: bridgevm
purpose: "Decentralized cross-chain bridge with MPC threshold signing"
status: built, not yet deployed
t-chain:
name: "T-Chain"
vm: thresholdvm
purpose: "MPC as a service for all Lux chains"
status: built, not yet deployed
k-chain:
name: "K-Chain"
vm: keyvm
purpose: "Distributed key management"
status: built, not yet deployed
q-chain:
name: "Q-Chain"
vm: quantumvm
purpose: "Post-quantum cryptographic operations"
status: built, not yet deployed
o-chain:
name: "O-Chain"
vm: oraclevm
purpose: "Decentralized oracle data feeds"
status: built, not yet deployed
g-chain:
name: "G-Chain"
vm: graphvm
purpose: "Graph queries and indexing"
status: built, not yet deployed
i-chain:
name: "I-Chain"
vm: identityvm
purpose: "Decentralized identity (DID)"
status: built, not yet deployed
z-chain:
name: "Z-Chain"
vm: zkvm
purpose: "Zero-knowledge proof verification"
status: built, not yet deployed
r-chain:
name: "R-Chain"
vm: relayvm
purpose: "Cross-chain message relay"
status: built, not yet deployed
# ═══════════════════════════════════════════════════════════════════════
# Application Chain EVM Networks
# ═══════════════════════════════════════════════════════════════════════
zoo:
name: "Zoo Network"
type: chain
coin: ZOO
website: zoo.network
exchange: zoo.exchange
explorer: explore.zoo.network
org: zoo-labs (501c3 foundation)
chains:
zoo-evm:
name: "Zoo EVM"
vm: evm
chain_ids: { mainnet: 200200, testnet: 200201, devnet: 200202 }
purpose: "Decentralized AI research, DeAI, DeSci"
hanzo:
name: "Hanzo Network"
type: chain
coin: AI # NOT "HANZO" — coin is AI
website: hanzo.ai
exchange: lux.exchange # trades on Lux DEX
explorer: explore.hanzo.network
org: hanzo-ai (Techstars '17)
chains:
hanzo-evm:
name: "Hanzo EVM"
vm: evm
chain_ids: { mainnet: 36963, testnet: 36962, devnet: 36964 }
purpose: "AI compute infrastructure, LLM inference, agent framework"
spc:
name: "SPC Network"
type: chain
coin: SPC
website: sparklepony.club
exchange: lux.exchange # trades on Lux DEX
explorer: explore-spc.lux.network
chains:
spc-evm:
name: "SPC EVM"
vm: evm
chain_ids: { mainnet: 36911, testnet: 36910, devnet: 36912 }
pars:
name: "Pars Network"
type: chain
coin: PARS
website: pars.network
exchange: pars.market # own white-label DEX
explorer: explore.pars.network
org: pars
chains:
pars-evm:
name: "Pars EVM"
vm: evm
chain_ids: { mainnet: 494949, testnet: 494950, devnet: 494951 }
purpose: "General purpose EVM"
pars-session:
name: "Pars Session Chain"
purpose: "Session management"
status: planned
# Tenant app chain EVMs are configured by the tenant operator (e.g. <tenant>-operator),
# not declared in upstream NETWORKS.yaml. Each tenant ships its own
# NETWORKS.yaml inside its own ops repo.
# ═══════════════════════════════════════════════════════════════════════
# Exchange Deployments (same codebase, different config)
# ═══════════════════════════════════════════════════════════════════════
exchanges:
lux.exchange:
primary_chain: lux (C-Chain)
chains: [lux, zoo, hanzo, spc, pars, ethereum, polygon, arbitrum, base, optimism, bnb, avalanche]
amm: [v2, v3, v4]
features: [swap, limit, pools, positions, explore, auctions, portfolio, buy, send]
zoo.exchange:
primary_chain: zoo (Zoo EVM)
chains: [zoo, lux]
fork_of: lux.exchange (white-label)
pars.market:
primary_chain: pars (Pars EVM)
chains: [pars, lux]
fork_of: lux.exchange (white-label)
# Tenant exchange entries are configured per tenant in their own ops repo.
# ═══════════════════════════════════════════════════════════════════════
# MPC Topology
# ═══════════════════════════════════════════════════════════════════════
mpc:
production:
nodes: 5
threshold: 3
namespace: lux-mpc
protocols: [CGGMP21, FROST, BLS, SR25519, LSS]
chains_supported:
secp256k1: [BTC, ETH, LUX, XRPL, all EVM]
ed25519: [SOL, TON]
sr25519: [DOT, KSM]
bls12-381: [LUX consensus, ETH beacon]
frost_taproot: [BTC taproot]
# ═══════════════════════════════════════════════════════════════════════
# Infrastructure (lux-k8s cluster)
# ═══════════════════════════════════════════════════════════════════════
infrastructure:
cluster: lux-k8s
namespaces:
lux-mainnet: 5 luxd validators
lux-testnet: 5 luxd validators
lux-devnet: 5 luxd validators
lux-gateway: Gateway API gateway
lux-explorer: "Lux Explorer (single Go binary: indexer+GraphQL+SPA) — 5 chains"
lux-bridge: Bridge UI + API + MPC nodes
lux-mpc: MPC dashboard + API + 5 MPC nodes
lux-kms: KMS (2 replicas)
lux-system: Traefik ingress + operator