3 Commits

Include renames

Author	SHA1	Message	Date
zeekayandHanzo Dev	0ec516da30	fix(explore/manifest): federation names use '<Brand> Network', never 'Subnet' ... generate-well-known.js regenerates public/.well-known/explore.json from the chain registry at build time, so the v1.1.4 hand-edit of the output file was overwritten by the generator (which still appended ' Subnet'). Fix the generator — the single source of truth — so the shipped manifest actually uses 'Network' (Lux nomenclature; no 'Subnet'). Regenerated file is in sync (wellknown:check passes). Pars id follows the registry (7070) to keep the manifest consistent with its source; the 7070-vs-live-494949 question is tracked separately in LLM.md. Co-authored-by: Hanzo Dev <[email protected]>	2026-07-14 07:00:23 -07:00
zeekay	1ff5ac4bf3	brand: audit, rip non-lux references, add .well-known/explore.json ... Per the no-crossover rule, explorer source contains only Lux brand data. Per-chain identity (subnet logo, chain name) preserved as network metadata. Removed: - .env.example.{hanzo,zoo,pars} — non-Lux brand build recipes - Dockerfile.liquidity — regulated US securities brand, must not appear in OSS - Third-party-domain hostnames from chainRegistry.ts (explore.zoo.ngo etc.) - Non-Lux hostname suffixes from lib/white-label.ts (.hanzo.ai, .zoo.network, etc.) - "" mention from lib/requestHost.ts comment Kept (chain identity on Lux primary network): - ZOO/HANZO/SPC/PARS_BRANDING constants in chainRegistry.ts - explore-{org}.lux.network hostnames (Lux-served subnet explorers) - DeFi terms ( Provider, add) — generic finance vocab Added: - public/.well-known/explore.json — federation manifest - scripts/generate-well-known.js — regenerates manifest from chain registry - Wired into npm build / build:next scripts - BRAND-AUDIT.md — survey + decisions	2026-05-29 14:30:23 -07:00
zeekay	3813d03918	feat: explorer FE — stateless SSR, chain selector, localnet, registry cleanup	2026-03-01 18:00:00 -08:00