Textile FX

Appearance

How to become a filler ​

Fillers are the market makers of Textile FX. They keep live buy and sell prices on a corridor, traders fill against those quotes, and the filler earns the spread they configured. See Quoting the order book for the mechanics.

You don't need to write code for this. Stitch, the open-source filler bot, does the whole job out of the box. You download the desktop app (menu bar / tray, no Docker), fund a wallet, set your spreads and limits in the browser panel, and press Start.

What you need ​

  • USDT inventory on the corridor's network. This is your working capital: it buys the counter-asset (cNGN, wARS, wBRL, XAUt) at your prices.
  • An exit for the counter-asset. Every buy-side fill leaves you holding the non-USD side. You need your own off-ramp or hedge for it; the protocol doesn't do this for you.
  • A dedicated hot wallet for the bot, holding your trading inventory plus a little native token for gas. Never your treasury key.
  • A machine that stays on: your own computer is fine while you try things out; for quoting around the clock, use a small server or one of the other install options below.
  • A price feed for the corridor: a simple HTTP endpoint returning the current price. Compare more than one source; your quotes are only as good as your feed.
  • Onboarding details from Textile: API and contract addresses for your corridor, plus testnet access to practice on. Write to contact@textilecredit.com.

Setting up Stitch ​

Two recommended ways to run Stitch, depending on need: the desktop app on the machine in front of you, or the Docker panel on a server. Desktop works on macOS, Windows, and Linux — a light menu-bar / tray controller that starts a local panel in your browser, with no Docker and no terminal.

  1. Download the app for your platform:
  2. Create your bot. On first launch the app asks you to pick a panel password (entered twice; only a hash is stored) and opens the panel in your browser. Pick your corridor, paste your bot wallet's private key, and press Create. Stitch writes the configuration and stores the key where only your user can read it. To log in again later, open the panel from the menu / tray and enter the password you set.
  3. Approve, test, go live. In Tools → Approve allowances, press Approve allowances once so Permit2 can pull the tokens you quote (a small gas fee; orders from an unapproved wallet post but never fill). Turn on Dry run to see exactly what it would quote without posting anything. When it looks right, press Start with a small liquidity cap, watch it for a day, then raise your limits.

Quit Stitch from the menu / tray to stop the local panel. For quoting around the clock, use a Docker / server install below on a machine that stays on.

Other ways to run it ​

  • With an AI coding agent: install the stitch skill in Claude Code or Codex, or paste the install prompt from the repo README. The agent installs the Stitch web UI (local password or server Tailscale) and opens it; you finish bot setup in the browser.
  • Docker: prebuilt image on GHCR. Pass the config and key as mounted files or environment variables.
  • Linux server: installer script plus a systemd service.
  • Manual install, for operators who live in a terminal: macOS or Windows, plus every release with checksums.

Whichever path you pick, the sequence is the same: keep the wallet key in a separate key file (never in the config), run stitch approve once, dry-run first, then go live small. After any config change, restart the bot; it reads the config at startup.

How you earn ​

Your spread is whatever you configure: quote 10 basis points off mid and you earn roughly that on every fill, while the taker pays a small per-chain protocol fee on top (1 bps on BSC and Celo, 5 bps on Ethereum). Stitch only posts orders your wallet can actually cover, so your funds move only when a trader fills you.

Next ​