modified native tokens with native endpoints

Author: jhjhjh94

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

@@ -343,13 +343,16 @@ Reach out on [Discord](https://discord.gg/graphprotocol) in the [Token API](http
 
 ## Advanced Topics
 
-### I keep seeing a smart contract with addresses like `0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee` and `0x000000000000000000000000000000000000`. What is this?
+### I keep seeing a smart contract with addresses like `0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee` and `0x0000000000000000000000000000000000000000`. What is this?
 
-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 Mainnet and its L2s (Base Mainnet, Arbitrum One, Optimism Mainnet), BNB on BSC Mainnet, AVAX on Avalanche C-Chain, and so forth.
+The address `0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee` is a sentinel (placeholder) used in some EVM contracts to represent the chain's native token (ETH, BNB, AVAX, etc.) when the code expects a contract address. It stands for the native token of the chain you're on: ETH on Ethereum/Mainnet L2s, BNB on BSC, AVAX on Avalanche C-Chain, and so on.
 
-The address `0x0000000000000000000000000000000000000000` was introduced in Uniswap v4 for the same purpose.
+`0x0000000000000000000000000000000000000000` is another placeholder introduced in Uniswap v4 for the same purpose. These repetitive patterns make it clear they're not real accounts—just conventional low-entropy addresses developers agreed to use.
 
-Because these addresses have an obvious repetitive pattern, they are clearly not randomly generated, as are other blockchain addresses. These accounts are not real accounts, just arbitrarily chosen low-entropy addresses that developers agreed to use.
+**Use native endpoints instead of placeholders:** When you need native token data, call the dedicated endpoints rather than relying on the sentinel addresses. For example:
+- `/v1/evm/balances/native` for EVM native balances
+- `/v1/svm/balances/native` for Solana (SVM) native balances
+- `/v1/tvm/transfers/native` for Tron (TVM) native transfers
 
 ### I'm getting 403/401 errors. What's wrong?