> For the complete documentation index, see [llms.txt](https://docs.arcv.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arcv.network/0.-quickstart-guides/0.3-how-to-trade-arcv.md). # 0.3 How to Trade $ARCV **Goal:** Identify the correct token and venue, acquire $ARCV with native USDC, and distinguish real transaction evidence from illustrative token telemetry. **Availability:** This documentation does not certify an ARCV launch, token address, or completed graduation. The market swap code supports real execution when valid deployment configuration exists. A displayed contract snippet, token symbol, or synthetic burn feed is not sufficient evidence of a verified token deployment. ## 1. Prepare a funded Arc wallet Add Arc mainnet using chain ID **5042**, native currency **USDC**, and the RPC in the [wallet setup guide](/0.-quickstart-guides/0.1-how-to-annotate.md). Fund the wallet through a supported route that explicitly delivers native USDC on Arc. USDC held on another chain is not automatically available on Arc. Keep enough native USDC for gas in addition to the swap input. The widget's **MAX** calculation reserves funds for estimated gas; it is not a guarantee that every subsequent transaction will fit the same estimate. ## 2. Verify the launch and token Open the project's verified launch record on [faze.fun](https://faze.fun/) when one is published. Compare its token address and chain against the project deployment record and Arc Explorer. Confirm the token's current venue and lifecycle. Do not identify the token by ticker alone or substitute an address from a demonstration card. If no verified launch record is available, stop before signing. Read [fair-launch architecture](/6.-protocol-economics-and-tokenomics/6.1-arcv-token-and-fair-launch.md) for the required token and migration evidence. ## 3. Buy during the bonding-curve phase On the verified Faze token page, connect your wallet, confirm Arc, and select a native USDC purchase. Enter the amount, inspect the quoted token output and price impact, and set a minimum acceptable output through slippage controls. Approve only the transaction for the verified venue and intended native value. Wait for a successful receipt and reconcile the acquired token balance. A wallet confirmation or broadcast hash alone does not establish a completed purchase. Curve prices change with trading activity. A quote is not a fixed execution promise. If graduation occurs before execution, refresh the token's venue and obtain a new quote instead of reusing the old transaction. ## 4. Use the post-graduation market terminal After verified migration, open [the ARCV market terminal](https://arcv.network/market) and select the token/DEX view. 1. Click **Connect Wallet** in the swap widget. Its real wallet connection is distinct from a prototype account balance elsewhere in the interface. 2. If prompted, switch to **Arc Network** and verify the account. 3. Enter native USDC input or use **MAX**. Review the slippage setting, normally 1.0%, and the quoted minimum output. 4. Confirm the detected route is the graduated DEX venue. A forced route that conflicts with the token lifecycle must be corrected before proceeding. 5. Submit the swap and review the wallet's destination and native value. Follow confirmation, broadcast, and receipt status. 6. Open the transaction on [Arc Explorer](https://explorer.arc.io/) and verify successful execution and received tokens. The integration uses the Faze SDK to construct the active route. Uniswap v4 execution goes through the appropriate Universal Router commands; it is not a generic v3 `exactInputSingle` call. A missing-token or router-configuration error must be resolved with verified deployment data, not bypassed. The current native-input widget is a **USDC-to-$ARCV buy flow**. For token sales, use a verified venue that supports selling and inspect any token approval it requests. A reverse trade is not implied by the presence of a buy widget. ## 5. Track actual buybacks and burns The current `/market` burn feed and supply metrics are synthetic demonstrations. They must not be treated as live evidence of buybacks funded by 5% of enterprise GMV. The target economic policy allocates half of a 10% settlement fee to buybacks, equal to 5% of accepted enterprise settlement volume. That policy is not implemented in the present registry. See [the revenue engine](/6.-protocol-economics-and-tokenomics/6.2-protocol-revenue-engine.md). For a real activity record, follow the settlement allocation, executed purchase, and token-removal transaction. Verify quantities and receipts at defined blocks. A transfer to a dead address can leave total supply unchanged; report it separately from a true supply-reducing burn. Buybacks do not guarantee a token price floor or an exit price. ## If execution does not complete For insufficient funds, reduce input and retain gas. For a stale quote or venue change, refresh routing and re-quote. If a transaction remains pending, inspect the wallet and explorer before retrying to avoid duplicate purchases. A reverted receipt means the trade failed even if the interface previously showed broadcasting. --- # 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://docs.arcv.network/0.-quickstart-guides/0.3-how-to-trade-arcv.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.