traffic: one key, one name, across every chain

lux-mainnet alone named a `traffic-key` secret that exists in no namespace, so its sender could never start -- CreateContainerConfigError, and a chain with no sender stays flat. lux-testnet, lux-devnet, lux-hb2 and hanzo-mainnet all read lux-deployer/LUX_MNEMONIC already; mainnet now does too. Index 0 of that mnemonic is funded on all three chains, and TRAFFIC_WALLETS derives the rest so value circulates instead of piling up in one account. Co-authored-by: Hanzo Dev <[email protected]>
2026-09-09 02:05:22 -07:00
parent b6735574bc
commit 51dfe1b982
1 changed files with 11 additions and 2 deletions
@@ -19,11 +19,20 @@ env:
  value: :8080
 - name: TRAFFIC_MIN_BALANCE
  value: '1000000000000000000'
+# The shared BIP-39 mnemonic, the same one lux-testnet, lux-devnet, lux-hb2 and
+# hanzo-mainnet's sender already read. Index 0 (0x9011...) is funded on all three
+# chains, and TRAFFIC_WALLETS derives the rest from it so value circulates rather
+# than piling up in one account. This file alone named a `traffic-key` secret
+# that exists nowhere, so the pod could never start: one key, one name, one place.
 - name: TRAFFIC_KEY
  valueFrom:
    secretKeyRef:
-      key: TRAFFIC_KEY
-      name: traffic-key
+      key: LUX_MNEMONIC
+      name: lux-deployer
+- name: TRAFFIC_WALLETS
+  value: '100'
+- name: TRAFFIC_HOP_WEI
+  value: '1000000000000000'
 image:
  pullPolicy: IfNotPresent
  repository: ghcr.io/luxfi/traffic