zeekayandHanzo Dev
c888672b59
The manifest credited luxfi/chains/dexvm for the D-Chain plugin. That proxy is deleted; the slot is filled by luxfi/dex cmd/dexd, which the node image builds into it directly. Note the CR is Pending and its binaryUrl (ghcr.io/luxfi/dexvm:v0.1.0) is a 404 — as is every sibling chain manifest here, which all point at ghcr.io/luxfi/<vm> while luxfi/chains publishes to ghcr.io/luxfi/chains/<vm>. That template is a separate question; this only stops the comment pointing at deleted source. Co-authored-by: Hanzo Dev <[email protected]>
23 lines
642 B
YAML
23 lines
642 B
YAML
---
|
|
# D-Chain — DEX (order book + perps + AMM).
|
|
# VMID: "dexvm". Plugin from luxfi/dex cmd/dexd — the matcher VM that runs the
|
|
# order book inside consensus. NOT from luxfi/chains: that module's D-Chain proxy
|
|
# was deleted, and the node image builds cmd/dexd straight into this slot.
|
|
apiVersion: lux.network/v1alpha1
|
|
kind: LuxChain
|
|
metadata:
|
|
name: d-chain
|
|
namespace: lux-mainnet
|
|
labels:
|
|
app.kubernetes.io/part-of: lux-network
|
|
lux.network/network: mainnet
|
|
lux.network/chain: d-chain
|
|
spec:
|
|
networkRef: luxd
|
|
alias: D
|
|
vm:
|
|
vmType: dexvm
|
|
binaryUrl: "ghcr.io/luxfi/dexvm:v0.1.0"
|
|
chainConfig:
|
|
cgo: false
|