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

# Supported pairs

> Chains available through swapXFG / SwapDaemon.

## Model

swapXFG uses a **chain client** registry rather than one binary per pair forever. Client modules under `src/SwapDaemon/` include (among others): Bitcoin, Bitcoin Cash, Ethereum and EVM-family chains, Solana, Monero, Litecoin, Dash, Doge, and additional staging clients.

Availability depends on **your build flags and config** (`fuego_swapd` / suite config). Always check the running daemon’s supported chains and RPC help.

## Common pairs (product intent)

| Side A | Side B              | Notes                     |
| ------ | ------------------- | ------------------------- |
| XFG    | BTC / BCH / LTC / … | UTXO family clients       |
| XFG    | ETH / other EVM     | Ethereum-style clients    |
| XFG    | SOL                 | Solana client             |
| XFG    | XMR                 | Monero / adaptor patterns |

Exact production-ready set changes with releases — do not treat a four-row table as exhaustive forever.

## On-chain vs cross-chain

| Venue       | Assets                | Fee model                                                                |
| ----------- | --------------------- | ------------------------------------------------------------------------ |
| **Hearth**  | XFG ↔ HEAT            | 1% Hearth fee (`HEARTH_FEE_BPS`)                                         |
| **swapXFG** | XFG ↔ external chains | 2% atomic fee (1% initiation + 1% claim, `SWAP_FEE_RATE_BPS`) → 69/11/20 |

These are the **only two protocol earnings streams**. Mint premium is 0 bps; the 0.1% CD creation fee is a donation to @fuegoxfg, not protocol revenue.

## Running SwapDaemon

```bash theme={null}
# Example shape — see binary --help for your build
./fuego_swapd --config fuego_swapd.json
```

Requires a synced Fuego node and appropriate counterparty endpoints for the chains you enable.

## Aliases

Where Fire Alias resolution is enabled, you may address peers by alias; the daemon resolves to a full address before initiate.