zeekayandHanzo Dev
789d95effe
v1.lux.exchange is built against api.lux.network/v1/bc/C/rpc, the path luxd served before v1.36.179. The lux-api rules matched /v1/chain and / only, so the exchange's balance and chain calls have answered 404 since the endpoint moved to the sync node. The sync node is on .148 and serves /v1/bc natively, so the rule passes it through untouched. Moving the node to .181 either adds the reverse rewrite here or rebuilds v1 against /v1/chain; the second is the one path the fleet keeps. Co-authored-by: Hanzo Dev <[email protected]>
Lux Universe — retired
Read-only from here. Canonical: https://git.hanzo.ai/lux/universe
This tip is an ancestor of canonical main, so no commit reachable from this
branch is unique to it — the canonical repo is a strict superset. Nothing was
lost by stopping here.
Two universes for one org is a split brain: a push lands somewhere real, reports
success, and never reaches a cluster, because CD reconciles the other one
(deploy/applicationset.yaml names the canonical URL). One repo per org means
that failure cannot happen.