> For the complete documentation index, see [llms.txt](https://takes.gitbook.io/takes-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://takes.gitbook.io/takes-docs/trade.md). # Trade and move USDC Open **Trade** to buy or sell pool shares, or move USDC between supported networks. Connect the wallet you want to use. The asset pickers show both the asset and its network. ## Buy or sell pool shares To buy, select USDC under **From** and the pool shares under **To**. To sell, select the pool shares under From and USDC under To. Selecting a pool pairs it with USDC on that pool's network. The swap control reverses the pair. Enter the amount, review the estimated output and fee details, then confirm the required wallet prompts. These are the same asynchronous requests as [Buy](/takes-docs/holders/mint-tokens.md#buy-pool-shares) and [Sell](/takes-docs/holders/redeem-tokens.md#sell-pool-shares) from Portfolio or a pool page, with the same approval, limits, settlement, cancellation, and claim rules. Buying does not fix the share quantity; selling does not fix the sale price at submission. Pool shares trade against USDC on their own network. To use USDC held on another network, move it first, then submit the buy request. There is no direct pool-to-pool trade or combined cross-network purchase. ## Move USDC between networks A USDC transfer moves funds to the **same wallet** on another network using Circle CCTP. It does not buy shares or deposit into a pool. Unlike automatic pool payouts, receiving this transfer requires a destination-chain wallet transaction. Keep enough of each network's [gas token](/takes-docs/reference/supported-networks.md#networks) on **both** networks before starting. Network gas is separate from the Circle transfer fee. On Arc, Max keeps an estimated USDC gas reserve. 1. Select USDC on the source network under **From** and USDC on a different destination network under **To**. 2. Enter **Amount to move (USDC)**. Review Estimated USDC received, the Circle fee, and its maximum cap. Choose **Move USDC** to save the reviewed transfer. It opens in the transaction tracker at the bottom right, and the form clears so you can start another. 3. Switch to the source network when asked. Choose **Approve USDC** if needed and confirm approval, then choose **Send USDC** and confirm the source transaction. Approval alone does not send funds. 4. Wait for source-chain finality and Circle attestation. You can close the page and return with the same wallet in the same browser. 5. When ready, switch to the destination network, choose **Receive USDC**, and confirm the transaction. When USDC arrives, choose **Dismiss** in the tracker to remove the finished transfer. Sending burns USDC on the source chain so it can be issued on the destination. **After the burn, the transfer cannot be cancelled.** Before sending, **Cancel transfer** is available when no source transaction is pending or has an unresolved wallet outcome. ## Resume or check a transfer Transfer progress is saved in this browser for your wallet and network environment. Open the transaction tracker at the bottom right to continue any saved transfer. Several transfers can be in progress at once; each one keeps its own steps. Keep the browser's saved data until delivery finishes. Expand transaction details for approval, send, and receive hashes. A receipt timeout does not prove failure. Use Check status when offered; if finality, attestation, or delivery checks fail, choose **Retry transfer status**. If the wallet outcome is unknown, inspect wallet activity and the existing hash before sending again. The app checks whether USDC was already received before preparing another receive transaction. For a delay, keep the source and destination networks, wallet address, transaction hashes, and visible error. See [Troubleshooting](/takes-docs/reference/troubleshooting.md#troubleshooting). --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://takes.gitbook.io/takes-docs/trade.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.