A Liquidity Tree is not a single standardized textbook structure—it’s a conceptual model used in trading systems, market microstructure, and smart order routing.
What it represents
A liquidity tree organizes available liquidity across venues, price levels, and instruments into a hierarchical structure.
Think:
- Root → Total available liquidity
- Branches → Exchanges / dark pools / brokers
- Leaves → Price levels + order sizes
⸻
Intuition
Imagine you’re trying to execute a large order (say buy 1M shares):
You don’t just hit one exchange—you:
- Split across venues
- Consider depth at each price level
- Optimize for slippage and fees
A liquidity tree models that decision space.
⸻
Example Structure
Total Liquidity
/ | \
NYSE NASDAQ Dark Pools
/ \ / \ |
100@10 200@10.1 150@10 100@10.05 500@10.02
Each leaf = (quantity @ price)⸻
Where it’s used
- Smart Order Routing (SOR)
- Execution algorithms (VWAP, TWAP, POV)
- Market making systems
- Liquidity aggregation engines
⸻
Why “tree”?
Because:
- You aggregate liquidity bottom-up
- You traverse top-down to decide execution
- You can prune branches (e.g., ignore expensive venues)
⸻
Key properties
- Hierarchical aggregation
- Multi-dimensional (price, venue, latency, fees)
- Dynamic (updates in real time)
- Often implemented with:
- heaps
- trees
- graph overlays (more realistic in modern systems)
⸻
Important nuance
In real trading systems:
A “Liquidity Tree” is often an internal abstraction, not a literal tree data structure.
Modern implementations are closer to:
- event-driven graphs
- priority queues
- order book snapshots + overlays