Ecosystem services
Candle combines on-chain contracts with specialized ecosystem services. This page describes their roles without implying that every third-party interface has completed a Candle-specific integration.
| Service | Role in Candle |
|---|---|
| HMC | Hood token discovery, pools, trades, candles, holders, wallet holdings, NFTs, transactions, and live market updates |
| Jupiter | Solana routing, quotes, market data, and post-graduation liquidity discovery |
| Meteora | Solana DAMM v2 graduation venue |
| Uniswap v3/v4 | Hood post-graduation liquidity venues |
| Relay | Supported cross-chain route planning and execution |
| Dexscreener and token metadata providers | Supplemental metadata and social-link enrichment for external tokens |
| Axiom, GMGN, and Fomo.family | Target terminal integrations using Candle’s common lifecycle and fixture specification |
Source-of-truth boundaries
Section titled “Source-of-truth boundaries”- Contract and program state is authoritative for market identity, lifecycle, balances, and execution.
- Candle’s API and HMC provide indexed, normalized, and lower-latency views of Hood data.
- Jupiter and Meteora provide Solana liquidity and routing information after graduation.
- Metadata providers can supplement images and social links but cannot establish that a market is a canonical Candle launch.
Integration status language
Section titled “Integration status language”“Supports Robinhood Chain,” “supports Uniswap v4,” or “shows the token” does not necessarily mean a terminal supports the Candle bonding-curve phase.
A terminal should be listed as fully integrated only after it passes the acceptance matrix in Terminals and indexers, including pre-graduation execution, lifecycle transitions, v3/v4 routing, and recovery behavior.