Update faq.mdx

Added Solana and supported networks link, Added Solana DEX support, Added 0xeeee... explanation, changed networks endpoint link

Author: UrsaPolarisRecords

website/src/pages/en/token-api/faq.mdx

@@ -8,7 +8,7 @@ Get fast answers to easily integrate and scale with The Graph's high-performance
 
 ### Which blockchains are supported by the Token API?
 
-Currently, the Token API supports Ethereum, BNB Smart Chain (BSC), Polygon, Optimism, Base, Unichain, Avalanche, and Arbitrum One.
+Currently, the Token API supports Ethereum, BNB Smart Chain (BSC), Polygon, Optimism, Base, Unichain, Avalanche, Solana, and Arbitrum One. A full list of supported networks can be found under the Token API column in [The Graph docs](https://thegraph.com/docs/en/supported-networks/).
 
 ### Does the Token API support NFTs?
 
@@ -36,7 +36,7 @@ The Token API supports historical token balances with the `/historical/balances/
 
 ### What exchanges does the Token API use for token prices?
 
-The Token API currently tracks prices on Uniswap v2 and Uniswap v3, with plans to support additional exchanges in the future.
+The Token API currently tracks prices on Uniswap v2, v3, and v4, along with Jupiter, Raydium, and Pump.fun on Solana, with plans to support additional exchanges in the future.
 
 ### Does the Token API provide a client SDK?
 
@@ -72,6 +72,10 @@ You can find the code for the MCP client in [The Graph's repo](https://github.co
 
 ## Advanced Topics
 
+### I keep seeing a smart contract with the address `0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee`. What is this address?
+
+The address 0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee is a sentinel (placeholder) address used to represent native tokens in EVM smart contracts. Since native tokens (ETH, BNB, AVAX, etc.) exist at the protocol level rather than as smart contracts, DeFi protocols need a placeholder address when their code expects contract addresses for all tokens. This address represents the native token of whatever chain you're on: ETH on Ethereum and its L2s (Base, Arbitrum, Optimism), BNB on BSC, AVAX on Avalanche, FTM on Fantom, and so forth. The repetitive pattern makes it obvious that the address is artificial; it's not a real account anyone controls, just an arbitrarily chosen low-entropy address that developers agreed to use.
+
 ### I'm getting 403/401 errors. What's wrong?
 
 Check that you included the `Authorization: Bearer <jwt>` header with the correct, non-expired token. Common issues include using the API key instead of generating a new JWT, forgetting the "Bearer" prefix, using an incorrect token, or omitting the header entirely. Ensure you copied the JWT exactly as provided by The Graph Market.
@@ -90,7 +94,7 @@ If you notice data inconsistencies, please report the issue on our [Discord](htt
 
 ### How do I specify a network?
 
-You can query available networks with [this link](https://token-api.thegraph.com/#tag/monitoring/GET/networks). A full list of the exact network IDs accepted by The Graph can be found on [The Graph's Networks](https://thegraph.com/docs/en/supported-networks/). Use the optional `network_id` parameter (e.g., `mainnet`, `bsc`, `base`, `arbitrum-one`, `optimism`, `matic`, `unichain`) to target a specific chain. Without this parameter, the API defaults to Ethereum mainnet.
+You can query available networks with [this link](https://token-api.thegraph.com/networks). A full list of the exact network IDs accepted by The Graph can be found on [The Graph's Networks](https://thegraph.com/docs/en/supported-networks/). Use the optional `network_id` parameter (e.g., `mainnet`, `bsc`, `base`, `arbitrum-one`, `optimism`, `matic`, `unichain`) to target a specific chain. Without this parameter, the API defaults to Ethereum mainnet.
 
 ### Why do I only see 10 results? How can I get more data?