FAQ

FAQ

Short answers; follow the links for depth.

Are there any fees? No platform fees — platform_fee_sat is hard-wired to 0. You pay only the on-chain mining fees for your own swap transactions.

Who holds my coins during a swap? You do. The engine holds your seed and keys locally, signs everything itself, and auto-refunds via a timelock if the counterparty walks. No board, relay, or counterparty ever custodies your funds. See Security Model.

Do I need to run my own nodes? For now, yes — the engine drives a real node (or Electrum backend) per coin. You must have at least two coins live before Satchel lets you trade. A full send/receive wallet without your own node arrives with the planned nodeless build. See Configuring Coins.

Does this run on mainnet? Yes. Both v1 (HTLC) and v2 (Taproot/MuSig2 adaptor) run on mainnet, reviewed and audited. You alone hold your keys — safeguard your recovery phrase.

Which coins are supported? The first pair is BTCX ↔ BTC. Litecoin (LTC) is the first added third coin. More coins can be added via coins.toml without recompiling — see Configuring Coins.

What are the default ports? pactd JSON-RPC listens on 127.0.0.1:9737; a Corkboard listens on 127.0.0.1:9780 by default. The RPC is loopback-only and refuses non-loopback addresses.

Is my activity private? Coordination messages are sealed to the recipient (PACTSEALED1; gift-wrapped on Nostr), so boards and relays see only ciphertext. Offers themselves are public and signed by design. There is no plaintext downgrade. See Transports.

How do I add a coin? Drop a [[coin]] block (and an icon) into coins.toml next to the executable — no recompile. Satchel reads it for connection defaults and the engine reads it for chain params. Walkthrough in Configuring Coins.

Where do my keys live? In the engine (pactd), on your machine only — derived from your BIP39 seed. Satchel stores no seed or passphrase. An encrypted seed is unlocked into engine memory per session. See Security Model.

Can I build my own front-end / integrate the engine? Yes — pactd is a plain JSON-RPC 2.0 daemon and Satchel is just one client of it. Drive it with pact-cli or any HTTP client; the full method surface is in the JSON-RPC API page and the Pact Developer Handbook (https://github.com/PoC-Consortium/satchel/tree/master/docs/handbook-pact).