> For the complete documentation index, see [llms.txt](https://developers.bead.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.bead.xyz/faqs-and-troubleshooting/environment-and-testing/usdc-network-fees-and-cost-considerations.md). # USDC network fees and cost considerations USDC exists on multiple blockchain networks. Network fees vary significantly by network, so your testing and production experience can look very different depending on which network a wallet is using. ### What Bead supports today We support USDC on these networks only: * Base network * Solana network We do not support USDC on Ethereum mainnet at this time. ### Why Ethereum mainnet can be expensive Ethereum mainnet fees can fluctuate heavily due to network congestion. Even simple USDC transfers can be meaningfully more expensive than Base or Solana. ### Base network fees Base fees are typically very low. For the smoothest experience on Base USDC, we recommend Coinbase Wallet. Depending on the wallet experience, fees can sometimes appear free if gas is abstracted or covered, but otherwise there may still be a small network fee. ### Solana network fees Solana fees are typically negligible and often well under a penny for standard transactions. I use Phantom for USDC on Solana, but any wallet that supports Solana will work. ### BEP20 and other networks BEP20 refers to BNB Smart Chain. We have discussed support for this network, but we do not support it yet. On our roadmap, the next stablecoin we plan to add is USDT. ### Practical guidance * If a user is paying with USDC, they must have a sufficient USDC balance on the supported network they are using. * If you are optimizing for lower fees, Base and Solana are the supported options today. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://developers.bead.xyz/faqs-and-troubleshooting/environment-and-testing/usdc-network-fees-and-cost-considerations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.