Market Routing & Liquidity
Current market infrastructure in the ƒxyz stack, with older exchange-engine work treated as archive context.
This section used to describe the project as a full exchange venue. That is no longer the right reader-facing framing.
The current live product focuses on:
- market data
- corridor and pair exploration
- route finding
- arbitrage analysis
- token and currency intelligence
Current Live Surfaces
| Route | Purpose |
|---|---|
/markets | Market overview and top-level routing/navigation surface |
/currencies | Consolidated currency overview |
/currencies/fiat-fx | FX pairs, history, and path analysis |
/currencies/stablecoins | Stablecoin monitoring and protocol context |
/currencies/cbdc | CBDC project and issuer surface |
/currencies/commodities | Commodity and tokenized-asset context |
/markets/trade | Route finder / interface surface |
/markets/p2p-arbitrage | Higher-tier arbitrage simulator and scanning surface |
/markets/algorithms | Algorithm-level explanation and references |
Internal Infrastructure
The repo still contains market-engine code and historical matching-engine work under packages/trading, but the live app is better understood as routing and market infrastructure, not a public exchange venue.
That distinction matters because:
- the user-facing product centers on route intelligence and cross-surface market context
- historical Lagrange-era exchange work remains important as archive context
- regulatory language should stay precise and conservative
Historical Context
Some exchange-engine and FIX-era work survives in:
Those pages should be read as historical lineage, not as a description of the current public product surface.
If you see older docs talking about a full venue, classic exchange UI, or older market-engine language, treat that as legacy architecture context unless it is confirmed by the current app routes and current code.