Files
zeekayandHanzo Dev 7417193940 A chain answers under one segment, and the fleet asks for it there
luxd moved chain APIs from /v1/bc/<alias> to /v1/chain/<alias> and deleted the
old prefix, and health moved onto typed ops at /v1/health/ops/*. Both landed in
node 1.36.181. Nothing here could move before that image existed, and the image
cannot roll out while the manifests still ask for addresses it no longer serves,
so the pin and the paths move in one commit.

What moved:
  image    1.36.171 -> 1.36.181, digest with it, on devnet/testnet/mainnet
  internal exchange-api, lux-hb2, rpc-tip-gate, the luxd startup script
  probes   /v1/health/liveness -> /v1/health/ops/liveness (bare /v1/health,
           which the local compose healthcheck used, no longer routes at all)
  public   the devnet and testnet gateway routes

Comments that RECORD an observation keep their original spelling: a note saying
/v1/bc/zoo/rpc returned 404 on a given date is a fact about that date, and
rewriting it would make the record false. Only live addresses moved.

1.36.181 also carries chains v1.7.38, so the deployed node has the zkvm
content-derived transaction identity.

Co-authored-by: Hanzo Dev <[email protected]>
2026-08-30 16:17:20 -07:00

30 lines
1001 B
YAML

---
# Hanzo L2 — primary-network-validating L2 on the Lux primary network.
# Its blockchain already lives on the Lux P-Chain (blockchainID
# RHuUsLWW5u6rmMSNKxgkWzXjDxx7fThi8Emw42HpMJTrVZNKd), created via
# CreateChainTx and validated by the existing luxd validator fleet
# (no separate validator set). EVM chainId 36963 (0x9063). Uses the
# shared Lux EVM VM (same vmID as C-Chain), alias "hanzo" → /v1/chain/hanzo/rpc.
#
# This Chain CR is a tracking/registration record so the bootnode /
# lux.cloud fleet dashboard lists Hanzo alongside the primary-network
# chains. It does not (re)create the chain — the P-Chain tx already did.
apiVersion: lux.cloud/v1
kind: Chain
metadata:
name: hanzo-chain
namespace: lux-mainnet
labels:
app.kubernetes.io/part-of: lux-network
lux.network/chain: hanzo-chain
lux.network/network: mainnet
lux.cloud/family: hanzo
lux.cloud/layer: l2
spec:
alias: hanzo
networkRef: luxd
vm:
vmType: evm
chainConfig:
cgo: false