Pharaoh’s Avalanche Contracts and Indexed Pool Data Serve Different Functions
Minting xPHAR burns half of the PHAR used, and direct redemption returns half of the underlying amount.

Pharaoh’s Avalanche contract list and an indexed-data API serve separate developer needs: one identifies protocol contracts, while the other organizes pool activity for monitoring and charting.
Pharaoh is a concentrated-liquidity decentralized exchange on Avalanche C-Chain. The contract list includes addresses for core tokens, factories, routers, quoters, access-control contracts and liquidity contracts. These addresses identify the contracts used for protocol interactions.
For pool analytics, developers can use a network search route that filters results by decentralized exchange identifier. The response includes 24-hour, seven-day and 30-day volume, along with liquidity, transaction counts and fees. A separate endpoint returns open, high, low, close and volume (OHLCV) candles for a pool when queried by its address.
Access depends on the data requested. Without an API key, candle requests are limited to hourly or longer intervals covering the previous 24 hours. Pool transaction data requires a paid plan.
The two resources therefore cover different parts of a developer’s workflow. Contract addresses point to on-chain components, while the indexed API presents pool activity in fields that can be queried and charted.
Pharaoh’s xPHAR conversion process uses different token amounts for minting and redemption. Minting xPHAR burns half of the PHAR used in the conversion, while directly redeeming xPHAR for PHAR returns half of the underlying amount. Software that handles either conversion must account for that difference in token amounts.