publish.yml computed and pushed a version tag on ubuntu-latest; the two
sync-*-branches jobs auto-merged dev into staging, polygon and vpn on
ubuntu-latest, a branch model that came with the fork and that this repo does
not use. The image build is untouched — docker.yml on lux-build and
release-matrix.yml on the luxfi-* pools both stay.
publish.yml computed and pushed a version tag on ubuntu-latest; the two
sync-*-branches jobs auto-merged dev into staging, polygon and vpn on
ubuntu-latest, a branch model that came with the fork and that this repo does
not use. The image build is untouched — docker.yml on lux-build and
release-matrix.yml on the luxfi-* pools both stay.
publish.yml computed and pushed a version tag on ubuntu-latest; the two
sync-*-branches jobs auto-merged dev into staging, polygon and vpn on
ubuntu-latest, a branch model that came with the fork and that this repo does
not use. The image build is untouched — docker.yml on lux-build and
release-matrix.yml on the luxfi-* pools both stay.
The marketplace shipped with no telemetry of any kind — no pageviews, no
sessions, no errors — so there was no way to say whether anyone uses it, or
which collection they came for. It is one of seven Lux surfaces going dark in
the same way, and all seven report through @hanzo/event, which posts to our own
door at api.hanzo.ai and to nobody else. A marketplace's traffic is not a thing
to hand to a third party, so no tag manager and no vendor script.
The provider wraps the client tree at the root, which is what makes every route
counted from one place. It sits outside the dynamically loaded wallet and
account providers on purpose: that chunk carries wagmi, IAM and the gui engine,
and a visitor whose wallet never arrives is exactly the visitor worth hearing
about. The provider counts the first load and usePageview counts every
navigation after it, so a single-page app stops looking like one visit that
never moves.
The ingest key is publishable — it attributes a write and can read nothing, so
it belongs in the bundle the way a public address does. An env override lets a
deploy swap it; the literal is what makes the site report today, since the
image is built with no arguments.
Co-authored-by: Hanzo Dev <[email protected]>
Every docker.yml run in this repo has died at 0s with "workflow file issue"
and zero jobs created, through two different reusable targets
(hanzoai/.github, then luxfi/.github). The YAML was never the problem.
luxfi/market is a PUBLIC repository; luxfi/.github and hanzoai/.github are
both PRIVATE. GitHub will not resolve a private reusable workflow for a
public caller and fails the run before any job starts. Positive control:
luxfi/finance is private, and the byte-identical call starts and builds.
workflow_dispatch cannot be used to probe this — the dispatch API answers
422 "Actions has been disabled for this user" — so the tag push is the only
trigger, and the only signal, available.
So the build is inline: buildx on the luxfi ARC scale set (runs-on takes the
SET NAME as its label), GITHUB_TOKEN login to ghcr.io, one linux/amd64 image
pushed as :<tag-version> and :latest. That unblocks shipping the /genesis
live read, which has been stuck behind this since 1.0.31 on 2026-06-25.
Co-authored-by: Hanzo Dev <[email protected]>
/genesis reads totalMinted() and totalLuxLocked() live and says so when the
contract does not answer. That landed in 9b7c25f. It has never reached a
browser: a page-load trace of https://app.lux.market/genesis right now still
renders the hard-coded tier table —
Genesis Permanently Locked 1,000,000,000 LUX Max Supply: 10
Validator Permanently Locked 100,000,000 LUX Max Supply: 100
Mini Permanently Locked 10,000,000 LUX Max Supply: 1,000
Nano Permanently Locked 1,000,000 LUX Max Supply: 10,000
— 40B LUX of "permanently locked" behind 0x004287c4..76c6, which has NO CODE:
eth_getCode on https://api.lux.network/v1/bc/C/rpc returns "0x" at block
1098195, positive controls WLUX 0x4888E4a2.. -> 3462 hex chars and Multicall3
0xd25F88CB.. -> 2592.
The live pods run ghcr.io/luxfi/market:1.0.31-amd64, built 2026-06-25. Tags
v1.0.32 through v1.1.4 produced no image at all: docker.yml carried a
top-level `permissions:` block alongside `secrets: inherit` on a `uses:`,
which fails the run at 0s with "workflow file issue" before any job starts —
and it targeted `["self-hosted","linux","amd64"]`, a label array that names
hanzoai-org scale sets not visible from luxfi. Both fixed by using the shape
that is actually building luxfi/finance: same-org reusable, no permissions
block, ARC scale-set name as a scalar label.
- next.config.ts -> next.config.mjs: Next 15's TS config loader calls
ts.sys.fileExists off the app's own typescript, which TypeScript 7 does not
export, so `next build` died before the first request. A config file that
annotates one object literal does not need types.
- next 15.5.0 -> 15.5.22, @luxfi/ui 7.4.9 -> 7.4.10 (patch only).
Co-authored-by: Hanzo Dev <[email protected]>
TypeScript 7 is the native Go compiler; the npm package is a thin shim
that resolves a platform-specific native binary.
Safe here because the build does not emit through tsc — the bundler does,
so tsc is typecheck-only and the built artifact is unaffected. Gated on a
measured comparison of both compilers against this same config: TS7
introduces no errors TS 5.9 did not already report.
typescript now ^7.0.2
Co-authored-by: Hanzo Dev <[email protected]>
CHAIN_INFO carried a `color` per chain — five hexes lifted wholesale from
GitHub's dark-syntax palette: #7ee787 (entity green), #d2a8ff (entity),
#ffa657 (variable — the literal tan the owner called out), #ff7b72 (keyword),
plus a cyan #55ccff for Lux itself. They were painted as inline
`style={{ color }}` in seven places on a surface whose every other pixel is
achromatic, and an inline hex is unreachable by white-label-by-hostname no
matter what value it holds.
Deleted rather than re-tokenised: the field existed to make five chains
distinguishable and the chain NAME already does that. The active chip in the
header was `text-black` over that hex, which stopped meeting contrast the
moment the fill stopped being a light pastel — it is the accent pair
(bg-primary/text-primary-foreground) now, which flips correctly with the mode.
@luxfi/ui 7.4.5 -> 7.4.9, which is also what un-breaks this app: two physical
copies of @tanstack/react-query left it rendering "Application error: a
client-side exception has occurred" with "No QueryClient set, use
QueryClientProvider to set one" in the console, on every route.
After: warm 0%, tinted-neutral 0.009%, mean chroma 0.448 at 1440x900 and
390x844, light and dark.
Co-authored-by: Hanzo Dev <[email protected]>
The header offered "Sign in with lux.id" and the IdP sent the user back to
https://lux.market/auth/callback — a route that did not exist, so the login
could START and never FINISH. Next answered 404 and the code was dropped.
Same fix as the duplication above it: `@luxfi/ui/[email protected]` owns the flow, so
the route is `<AuthCallback/>` and providers.tsx is `<AuthProvider>` instead of
a verbatim copy of lux/mpc/dashboard's `configureIam` + `startLogin` + `logout`.
The market has nothing of its own to do with a fresh session.
`tsc --noEmit` clean.
Co-authored-by: Hanzo Dev <[email protected]>
TypeScript 7 reports TS2882 for a stylesheet side-effect import with no type
declaration; TS 5.x accepted them silently. Bundlers resolve stylesheets through
their own loaders, so the import never reaches the TypeScript module resolver —
this declares them legitimate rather than giving them a shape.
MEASURED, not assumed: this repo reports TS2882 under tsc 7 without the file and
zero with it. Repos where a framework already ships ambient CSS declarations
(Next's next-env.d.ts) were left alone — the declaration is inert there and was
not added.
Co-authored-by: Hanzo Dev <[email protected]>
Ten files imported `lucide-react` directly. The vintage happened to match what
@luxfi/ui resolves today, but a direct dependency is a second place the version
can move, and it has moved before — the surfaces ranged over 0.312, 0.474, 0.577,
1.26 and 1.27, which are different drawings under the same names. `Search` at
0.312 and `Search` at 1.27 are not the same glyph.
So the dependency goes and the import path becomes `@luxfi/ui/icons`, which is
Lucide as @hanzo/gui standardises on it. One package resolves the set, for every
Lux surface, and drift stops being expressible here.
Import-path change only — `git diff src` is ten single-line edits. `next build`
is clean, 6 routes prerendered.
Not screenshotted: this surface does not currently render past hydration. It
throws "No QueryClient set, use QueryClientProvider to set one" from wagmi, in
50f5b65 (refactor(market): one chrome — a wallet is not an account), which this
change does not touch. Same error, same 127-byte body, with these ten edits
reverted.
Co-authored-by: Hanzo Dev <[email protected]>
lux.market had a header of its own: its own sticky bar, its own link styling, a
nav with no phone presentation at all, and a Connect button standing in for an
account menu the surface did not have. Two identities meet here and they are not
the same thing — the WALLET signs a listing, the ACCOUNT is who you are and
which org you act in — and only the first existed.
The chrome is now `AppNav` from @luxfi/ui: brand, org switcher, links, settings
and the user menu, identical to the MPC dashboard and the bootnode console, with
the links collapsing into the same gui Sheet the switchers use. The chain
selector and the wallet button stay, in the nav's free slot, because those are
this surface's own controls and not chrome.
Identity comes from IdentityProvider (IAM); brand, theme, issuer and IAM client
come from the Host header, so lux.market and a zoo-branded market are one image.
The gui engine's bundler wiring comes from `withLuxUi`, not a hand-rolled
transpile list.
`next build` passes: 6 static routes exported.
Co-authored-by: Hanzo Dev <[email protected]>
The page rendered four hard-coded tiers claiming 10x1B + 100x100M +
1000x10M + 10000x1M LUX "permanently locked", plus per-tier "10x/5x/2x/1x
rewards". None of it came from anywhere:
- The collection 0x004287c47efc912fec391979154454a8017a76c6 has NO CODE at
head. Measured on https://api.lux.network/v1/bc/C/rpc at block 1098191:
eth_getCode -> "0x", totalSupply() -> "0x" (revert). Positive control
WLUX 0x4888e4a2.. -> 3462 hex chars and a live totalSupply.
- The supplies contradicted the tokenomics reference: NFT-COLLECTION.md
has Genesis Validator count 100 (not 10) and records that the
Validator/Mini/Nano hierarchy is "tokenomics-designed but not issued".
- GenesisNFTs.sol has no reward-multiplier concept at all. The 10x/5x/2x/1x
figures were invented outright.
Now the page calls totalMinted() and totalLuxLocked() — both real reads,
GenesisNFTs.sol:829 and :214 — and renders whatever chain returns. When the
call reverts, as it does today, it says supply and bonded LUX are
unavailable and names the address, rather than substituting a number.
Also drops src/lib/wagmi.ts: a second createConfig that nothing imported,
shadowing the live one in app/providers.tsx.
Co-authored-by: Hanzo Dev <[email protected]>
lux.market drew Lucide at 0.511 while the console drew it at 1.27 and lux.vote
at 0.312. Same set, three vintages — and Lucide redrew a lot between 0.3x and
1.x, so the same named glyph came out a different shape depending on which
surface you were looking at. One vintage now, matching the console and matching
the geometry the explorer's sprite is generated from.
All eleven glyphs the marketplace uses (ArrowRight, Check, ChevronDown,
ChevronRight, ChevronUp, Circle, ExternalLink, LogOut, Search, Wallet, X) exist
under the same names in 1.27; `next build` exports all six routes clean.
Co-authored-by: Hanzo Dev <[email protected]>
app.lux.market rendered "No NFT collections found on Lux yet" unconditionally:
src/hooks/useNFTData.ts and src/lib/explorer.ts returned {items:[]} literals, so
no request was ever made. The URLs they would have used were dead anyway.
Measured against live mainnet 96369 and fixed:
- lib/chains.ts: EXPLORER_API pointed at https://explore.lux.network/api/v2 —
404 (that host serves the Next.js frontend, not an API). The live read API is
the unified indexer at https://api-explore.lux.network/v1/indexer/<slug>,
slugs from its own /v1/explorer/admin/chains. CORS is `*`.
- lib/chains.ts: all five rpcUrls 404'd (`/mainnet/ext/bc/...`). Public form is
`/v1/bc/C/rpc`; the four reachable ones now verified via eth_chainId. SPC has
no public RPC and is marked as such.
- lib/chains.ts: Pars was chainId 17471; it is 494949 (eth_chainId 0x78d65).
- lib/chains.ts: CHAIN_INFO gained `color`, read by three pages that had been
typing it as a missing property.
- lib/explorer.ts: real typed fetchers, one data-access layer. The indexer
ignores `?type=`, so the ERC-721/ERC-1155 filter is applied client-side.
- hooks/useNFTData.ts: thin react-query wrappers over those fetchers.
- app/activity: dropped its private copy of the fetch (used `tx_hash`; the API
field is `transaction_hash`) in favour of the shared hook.
- ActivityRow: derives the explorer URL from the chain object instead of string
surgery on the API base.
- contracts.ts: MARKET_ABI was `[]`. Filled from the real interface at
standard/contracts/nft/Market.sol:37-48. ERC721_ABI gained the `approve` entry
ListingForm calls.
- ListingForm/OfferForm addressed `contracts.markets`; the field is `market`.
- OfferForm sent paymentToken=address(0) plus native `value`. makeOffer is
non-payable and reverts on address(0) (Market.sol:418) — every offer would
have reverted. Now denominated in WLUX, verified on-chain (1730 bytes, 18dp).
- next.config.ts: ignoreBuildErrors was hiding all 40 of the above type errors.
Turned off; `pnpm build` is green with checking on.
CONTRACTS stays empty: Market.sol is deployed on no Lux chain. The recorded
mainnet address (addresses.json markets/Markets 0xefba7dbf…) has no code — so
list/buy/offer remain unreachable by design until it is redeployed.
Co-authored-by: Hanzo Dev <[email protected]>
Replaces non-canonical scale-set / org-prefixed labels with the
existing labels every arcd host registers with. Matches evo for
amd64 and spark for arm64. No new labels added.
Was using canonical workflow defaults (hanzoai-scoped labels) which
do not dispatch for luxfi org. Switched to round-robin pool labels:
runner-amd64: luxfi-amd64 (evo)
runner-arm64: luxfi-arm64 (spark + dbc, round-robin)
runner-deploy: lux-deploy-linux-amd64 (DO ARC pool)
Project already had pnpm-lock.yaml; yarn.lock was stale. Pinning the
packageManager field locks the local toolchain to pnpm so commit
hooks and CI agree.
- Replace inline chain/contract/hook implementations with @luxfi/* imports
- All 6 lib/hook files now thin re-exports from shared packages
- Standalone market at github.com/luxfi/market (removed from exchange monorepo)
zeekay
