> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fx.meme/llms.txt
> Use this file to discover all available pages before exploring further.

# Frequently asked questions

> Straight answers about currency pairs, token launches, fees, and $FX.

<AccordionGroup>
  <Accordion title="What does “launch into EUR/USD” mean?">
    It means creating two markets for the same token: TOKEN/EURC and TOKEN/USDC. Those markets connect through an existing EURC/USDC pool. The result is a triangle of exchange relationships. See [how FX works](/how-fx-works).
  </Accordion>

  <Accordion title="Does the token track the EUR/USD exchange rate?">
    The currency pair defines the market structure. It does not create a peg, currency reserve claim, or automatic exchange-rate tracking product. The token's price emerges from trading in its markets.
  </Accordion>

  <Accordion title="Are there two versions of the token?">
    Both quote-currency pools trade the same ERC-20 token. A euro-side purchase and a dollar-side purchase acquire the same asset.
  </Accordion>

  <Accordion title="Does each launch create another EURC/USDC pool?">
    An FX launch creates its two token pools and connects them through approved external currency liquidity. The currency pool can serve multiple launches and other market participants.
  </Accordion>

  <Accordion title="Can I launch against just one currency?">
    Yes. Single-currency launches create one token pool and support optional creator and holder fees. Their baseline economics differ from FX-pair markets. See [launch a token](/guides/launch).
  </Accordion>

  <Accordion title="Why can a buy have a very large fee at launch?">
    The configured opening policy applies a temporary surcharge to buys. In the deployed R6 policy, it starts at 99% of the post-normal-fee quote remainder and expires after five seconds of chain time. See the [opening window](/economics/opening-window) for the exact schedule.
  </Accordion>

  <Accordion title="Is an indirect route always better?">
    Compare the final quoted output for the same input. An indirect route may access a better price, but it also adds currency-pool fees, price impact, and execution costs. See [trading and routing](/guides/trade).
  </Accordion>

  <Accordion title="Do token holders receive part of every FX trade?">
    Holder rewards are an optional fee-funded feature of ordinary single-currency launches. FX-pair markets and the dedicated official \$FX market have holder rewards disabled. See [creator and holder fees](/economics/rewards).
  </Accordion>

  <Accordion title="What does the 90/10 split apply to?">
    Eligible protocol revenue after realization in USDC. Ordinary creator claims, holder rewards, and LP principal remain separate. Of eligible receipts, 90% is reserved for \$FX market purchases and 10% goes to operations.
  </Accordion>

  <Accordion title="Does buy and burn reduce totalSupply?">
    Acquired FX is sent to the configured dead address. The token's ERC-20 `totalSupply` remains unchanged. See [FX and protocol revenue](/economics/fx-token) for the accounting.
  </Accordion>

  <Accordion title="Can the owner withdraw the reserved buyback money?">
    The design provides no administrative exit for the reserved budget. Execution still depends on the registered token, market liquidity, and the installed policy. Owner pause controls can affect when execution is available.
  </Accordion>

  <Accordion title="Where are the deployed contracts and public app?">
    The [deployed contracts](/developers/contracts) page lists the Arc mainnet addresses and release manifest. The public app and indexed market API are not hosted yet. Check [release status](/reference/release-status) for the launch gate, currency configuration, and official FX registration.
  </Accordion>

  <Accordion title="Can I launch a token right now?">
    The contracts are deployed, but the mainnet registry currently has new launches paused. The gate applies to both ordinary launches and the dedicated official-FX launch. See [release status](/reference/release-status) for the latest verified state.
  </Accordion>
</AccordionGroup>