What it is
Osage Exchange is a white-label deployment of @luxfi/exchange — the same canonical exchange app that powers zoo.exchange and the rest of the Lux family. Same SDK, same router, same wagmi plumbing; configured here for the Osage ecosystem.
The whole app, declaratively
The entire Osage Exchange is roughly eighty lines of configuration in apps/web/src/main.tsx. Each concern lives in exactly one place:
- Visual identity —
@osage/brand+@osage/logo. - Chains —
osageMainnetas default, with the canonical Lux family available. - DEX backend —
gatewaymode atdex.lux.network, layering precompile → V3 → V2 → Warp routing per chain. - Regulated provider — Liquidity, for stocks and private securities, with KYC and accreditation enforced at the provider.
- Auth — Hanzo IAM at
iam.osage.id; user-facing portal at osage.id; IAM applicationosage-exchange. - KMS —
kms.osage.id; secrets never touch the client. - Featured tokens — native ecosystem assets and selected partner exposures.
What lists
- Native ecosystem assets —
OSG,GOLD-O(allocated metal claim from Osage Gold),FARM-O(agricultural notes from Osage Farm). - Tokenized stakes in operating companies, after due diligence by Osage Capital.
- A small Liquidity-gated equities surface for accredited partners.
- Block trades and OTC inquiry via Osage Trade.
What does not list
Anonymous tokens. Vehicles whose principal use is regulatory arbitrage. Anything our compliance committee or general counsel will not put a name to.
Source
Public source: osage/exchange. Same shape as zooai/exchange — a thin shim over @luxfi/exchange.