​

Step-by-Step Tutorial: Managing Atomic Swaps & Nodes via the Fuego TUI

​

Prerequisites & Compilation

​

System Requirements

• Operating System: Linux, macOS, or Windows (WSL2 recommended)
• Go Runtime: v1.24+
• C++ Toolchain: Standard build-essential or clang required for backend node core IPC compilation.

​

Step 1: Clone and Compile

# Clone source repository (ensure recursive submodule initialization)
git clone --recursive https://github.com/fuego-project/xfgo.git
cd xfgo/tui

# Compile the terminal executable target
./build.sh

​

Navigating the Terminal Workspace

# Launch in native Mainnet configuration
./fuego_suite

# Launch with automated Testnet configuration and dedicated routing
./fuego_suite --testnet

​

The Interface Layout

┌────────────────────────────────────────────────────────────────────────┐
│ 🔥 FUEGO TUI [PRIVACY PROTOCOL]      MODE: MAINNET      PEERS: 24/32   │
├────────────────────────────────┬───────────────────────────────────────┤
│ Navigation (Tab / Vim Keys)    │ SYSTEM STATE: Node running — height   │
│ > 1. Start Node                │                                       │
│   2. Stop Node                 │ Primary Address (Prefix: 1075740):    │
│   3. Node Status               │ Fg7x...3k9a                           │
│   4. Start Wallet RPC          │                                       │
│   5. Create Wallet             │ Base Liquidity:                       │
│   6. Get Balance               │   [XFG Reserve]: 1,240.50 XFG         │
│   7. Send Transaction          │   [HEAT Cash]  : 5,000.00 HEAT        │
│   8. Burn2Mint Menu            │                                       │
│   9. Show Logs                 │ Core Deep-Sync: ACTIVE                │
├────────────────────────────────┴───────────────────────────────────────┤
│ LOGS: [INFO] Successfully synced block header 842,900 (Epoch 936)      │
└────────────────────────────────────────────────────────────────────────┘

​

Global Key Bindings

• Tab / Shift+Tab: Cycle active interface panels focus.
• h, j, k, l / Arrow Keys: Standard directional navigation within active menu lists.
• Enter: Confirm selection or trigger action form execution.
• Ctrl+C / q: Gracefully disconnect node RPC sessions and exit to OS shell.

​

Executing Core Protocol Operations

​

Operation 1: Burning XFG to Mint HEAT Cash

1. Use j to highlight 2. Mint HEAT (Burn2Mint) and press Enter.
2. Enter the target amount of base-layer XFG to consume. The system automatically reads the current dynamic Q64.64 PI Controller RedemptionPrice off the blockchain state.
3. Review the output execution preview:
   Consuming        : 100.00 XFG
   Current L1 Price : 0.20 XFG / HEAT
   Expected Output  : 500.00 HEAT (assetId=0x01)
   
4. Press Enter to sign and push the irreversible conversion transaction. Once included in the block, your updated per-asset balance will reflect immediately in the overview pane.

​

Operation 2: Supplying Liquidity to the Hearth AMM

1. Navigate to 3. Hearth L1 AMM Interface.
2. Select the [Add Liquidity] execution tab.
3. Input your desired base asset depth. Because Hearth enforces strict constant-product invariants ($X \times Y = K$), the terminal client dynamically queries the exact required secondary ratio using getAmmQuote RPC calls.
4. Confirm deposit execution. The pool issues equivalent internal L1 LP shares, entitling your address to continuous pro-rata accumulation of the network’s flat 1% swap fees.

​

Operation 3: Conducting Peer-to-Peer Atomic Swaps

​

Step-by-Step Swap Flow:

1. Open the 4. Atomic Swap Engine panel.
2. Select [Initiate Swap Offer] and provide your counterparty’s network routing descriptor (I2P address or direct node multiaddr).
3. Specify the swap parameters (e.g., offering 500.00 XFG for 0.025 BTC).
4. The terminal engine automatically negotiates the cryptographic lock time boundaries and constructs the verification adapter script.
5. Once both parties broadcast their respective initialization locks, monitor the auto-extracting progress bar inside the interface until final output settlement completes.

​

Troubleshooting & Verification

• Symptom: Error: assetId mismatch during output discovery
  • Resolution: Verify that your terminal client binary is built against the v1.10.00 codebase header containing updated CryptoNoteSerialization.cpp multi-asset decoding routines.
• Symptom: High slippage warnings during AMM liquidity provisioning.
  • Resolution: If the global TWAP spot price diverges sharply from your local node’s cache, run 5. Node Diagnostics -> Rebuild Sync Cache to purge stale mempool states.