zeekayandHanzo Dev
232c6fdce7
github.com/luxfi/universe is canonical from here. git.hanzo.ai/lux/universe is unreachable, and this merge carries its lineage over. The rule applied, per area: Workflows: one set, under .hanzo/workflows; .github/workflows is gone. LLM.md, README.md, deploy/README.md: the forge's. GitHub's sections were the ones the forge had already rewritten (the /mainnet/v1/bc path table, the auto-bump flow), not divergent content. Counts brought to what this tree holds; LLM.md records the rules below. deploy/applicationset.yaml: the forge's object (apps.hanzo.ai/v1, destination name lux-cluster) with repoURL https://github.com/luxfi/universe. deploy/*.yaml modified on both sides: a three-way merge, not a whole-file pick. Where both moved the pin, the newer semver wins; at the same semver, the side that pinned a digest (exchange-api 2.3.34 is sha256:3eae48ac, which the registry confirms; GitHub's zoo copy carried 007beb83, the pre-repush bytes). Where both wrote cd.automated, GitHub's false wins: it is the later decision (909d3bd) and the one about the cluster CD now runs on. true stays only on the static sites GitHub verified there. The forge's /v1/bc -> /v1/chain rename and its digests are carried into files whose other hunks came from GitHub (explorer, exchange-api x3, rpc-tip-gate, lux-market). lux-bank/lux-financial: GitHub's v1.5.5 is not in the registry (the newest published tag is v1.5.3), so the pin is v1.5.3 with its digest. A pin never names an image the registry does not have. Static sites (lux-audio, lux-cloud/cloud, lux-credit, lux-fund, lux-lps, lux-network, zoo/zoo-exchange): GitHub's three-object declaration — a staticFiles Middleware, the route that names it, the endpoint-less Service, no image — replaces the forge's pod. A union would put an Ingress and a priority-100 IngressRoute on one host with a pod behind it serving nothing. The forge's last pins, for the record: lux-audio ghcr.io/luxfi/audio:latest@sha256:48265c37c91f lux-cloud ghcr.io/luxfi/cloud-web:v1.5.34@sha256:54a586fbd4d6 lux-credit ghcr.io/lux-apps/credit:36b1c2dffd62 lux-fund ghcr.io/lux-apps/fund:20cb7cb988b3 (amd64 only) lux-lps ghcr.io/luxfi/lps:1.0.2 lux-network ghcr.io/lux-apps/network:latest@sha256:b52dd80f59d7 zoo-exchange ghcr.io/luxfi/exchange:5.149.73@sha256:baefb1903851 Lifted objects (lux-mainnet/{explorer,lux-build,lux-market,rpc-tip-gate}): the forge's file — the claim, routes, middlewares and rbac it lifted out of k8s/ — with GitHub's cd.automated: false. deploy/hanzo/{cloud,commerce-site,iam,lux-bitcoin,lux-coin,lux-finance, lux-industries,lux-market,lux-safe}.yaml, deploy/lux-ns/lux-exchange.yaml, deploy/lux-web/lux-network.yaml: deleted, as GitHub did in2079731. Each Lux site is declared once, as files, in its own namespace; hanzo's own services are hanzo/universe's to declare. What the forge had changed in them, so it is not lost: hanzo/cloud v1.801.476@sha256:0743f907; hanzo/iam IAM_DATABASE_URL from Secret iam-db; lux-safe ghcr.io/luxfi/safe:v2.2.14; lux-exchange 5.149.83@sha256:7c1bd0e9 with a rateLimit Middleware and the hosts app.lux.exchange, trade.lux.exchange, exchange.lux.network, markets.lux.network; lux-web/lux-network at sha 1028f82e. deploy/zoo-mainnet/: removed. Every Zoo workload is declared in zooai/universe. Floating tags: every one carries a digest. lux-market and rpc-tip-gate take the forge's frozen digests back; the rest already had theirs. k8s/lux-*: the forge lifted k8s duplicates into deploy/ values and deleted them. luxd-statefulset x3, lux-mainnet/explorer, lux-testnet/{chain-traffic, exchange-api} stay deleted; what GitHub changed in them (node v1.36.125 pins, exchange-api 2.3.28, the 50Gi claim, a comment) is behind the values files (node 1.36.181, exchange-api 2.3.34, the explorer claim). The gateway configs, luxd-startup ConfigMaps, lux-testnet/explorer and the mainnet kustomization are the forge's: GitHub's content is a subset of them up to /v1/bc -> /v1/chain and /v1/health/liveness -> /v1/health/ops/liveness, and network.yaml, which GitHub's kustomization still lists, no longer exists. scripts/roll_luxd.sh: the forge's quorum-preserving roll (eviction API, one pod at a time, digest + version + every-chain bootstrap, devnet -> testnet -> mainnet) plus GitHub's closing height-and-restart report. The tag is written in the spelling the values files use (bare 1.36.181) and the digest resolved for that spelling; a leading v is accepted and stripped. The push remote is GIT_REMOTE (default origin). Validated: 123 deploy YAMLs parse; 122 values files render against chart app 0.1.11; no floating tag without a digest; every kustomization that built before builds now; pin.sh --verify reads 92 pins, 79 agree, 6 are frozen moving tags whose pointer has since moved (their digests still name real bytes), 6 are registries a luxfi token cannot read, and lux-financial is the one it caught. Co-authored-by: Hanzo Dev <[email protected]>
63 lines
1.4 KiB
YAML
63 lines
1.4 KiB
YAML
# Transaction generator for lux-devnet. Use only funded mnemonic index 0. The
|
|
# former 100-wallet ring slowly consumed each derived account's gas and then
|
|
# reported RESUMED/SKIPPED forever without producing a block.
|
|
args:
|
|
- -config
|
|
- /etc/traffic/chains.json
|
|
- -max-inflight
|
|
- '4'
|
|
component: traffic
|
|
containerName: traffic
|
|
env:
|
|
- name: TRAFFIC_TPS
|
|
value: '0.4'
|
|
- name: TRAFFIC_AUTOSTART
|
|
value: 'true'
|
|
- name: TRAFFIC_LISTEN
|
|
value: :8080
|
|
- name: TRAFFIC_MIN_BALANCE
|
|
value: '1000000000000000000'
|
|
- name: TRAFFIC_WALLETS
|
|
value: '1'
|
|
- name: TRAFFIC_HOP_WEI
|
|
value: '1000000000000000'
|
|
- name: TRAFFIC_KEY
|
|
valueFrom:
|
|
secretKeyRef:
|
|
key: LUX_MNEMONIC
|
|
name: lux-deployer
|
|
image:
|
|
pullPolicy: IfNotPresent
|
|
repository: ghcr.io/luxfi/traffic
|
|
tag: v0.2.18
|
|
partOf: lux
|
|
ports:
|
|
- containerPort: 8080
|
|
name: http
|
|
protocol: TCP
|
|
replicas: 1
|
|
resources:
|
|
limits:
|
|
cpu: 500m
|
|
memory: 256Mi
|
|
requests:
|
|
cpu: 25m
|
|
memory: 64Mi
|
|
selectorLabels:
|
|
app: traffic
|
|
volumeMounts:
|
|
- mountPath: /etc/traffic
|
|
name: chains
|
|
volumes:
|
|
- configMap:
|
|
defaultMode: 420
|
|
name: traffic-chains-tkf97c4hm9
|
|
name: chains
|
|
|
|
# Enforcement switch, read by the lux-fleet ApplicationSet's templatePatch —
|
|
# not by the chart. On while this Application already read Synced, so it
|
|
# applies nothing today; what it adds is selfHeal, which returns a
|
|
# hand-edited object to what is written here. prune stays off.
|
|
cd:
|
|
automated: false
|