My Pools

Daemon Soberano · Bitcoin L1

You hold the keys. The pool is yours.

Anyone, anywhere can run a liquidity pool on Bitcoin: real coins, in your own wallet, on your own machine — earning you a fee on every swap. Kray Space is just the signpost that routes traders to you. Your pool runs via the kray-pool-agent daemon: private keys never leave your computer, the daemon independently verifies on-chain reserves before signing every swap, and Kray Space re-checks every PSBT against ~25 immutable rules.

Why this matters → See pool anatomy →

Owner address

In plain words

Imagine you own a small currency exchange booth. You put Bitcoin on one side of the counter and your Rune on the other. Travelers stop by and trade one for the other, and every trade pays you a small fee.

Now imagine that booth lives inside your own house, the cash never leaves your hands, and kray.space is just the street sign pointing travelers to your door. That is a User Pool. Nobody — not even Kray Space — can touch your money. You can close the booth any time by turning it off.

What is a User Pool? (the precise version)

A User Pool is a Bitcoin/Runes liquidity pool where you hold the private keys, on your own computer, in your own wallet. Kray Space lists your pool on the swap page so anyone can trade with it — but Kray Space never sees, holds, or touches your keys. The liquidity is real coins sitting at a real Bitcoin address that only you control — verifiable on-chain by anyone.

The bridge between your wallet and the public swap UI is a small open-source program called kray-pool-agent (the “Daemon Soberano”). It runs on your laptop or server and signs swap transactions only when they obey strict rules.

How a swap actually works

Buyer requests a quote Someone on /swap clicks BUY. Kray Space looks up your pool, builds an unsigned PSBT, and asks your daemon for permission via WebSocket.

Daemon verifies on-chain reality Your daemon ignores what the server claims and fetches real reserves from mempool.space and ordinals.com. It then checks the PSBT against AMM math, fee caps, sighash flags, Runestone integrity, and ~20 other rules.

Daemon signs locally Only if every check passes does the daemon sign with your Taproot key. The signed PSBT is sent back via WebSocket — your private key never leaves the daemon process.

Server re-verifies (the neutral judge) Kray Space applies the same ~25 immutable rules to your daemon's signed PSBT. If the daemon was modified or hostile, the server rejects it. The buyer never sees a malicious PSBT.

Buyer signs and broadcasts The buyer's wallet adds their signature. Server runs a final phantom-signature check, then broadcasts to Bitcoin. Atomic — neither side can be cheated.

What's protected

Private keysAES-256-GCM + Scrypt at rest, never sent over network.

SIGHASH attacksOnly SIGHASH_DEFAULT / SIGHASH_ALL accepted on pool inputs.

Reserve manipulationDaemon fetches reserves on-chain, doesn't trust the server.

Fee drainHard cap 1000 sat/vB + relative cap 5% of swap value.

Cenotaph rune burnPointer/edict range and unknown-tag checks reject burn-inducing PSBTs.

Mempool griefingnLockTime ≤ height + 100 blocks, nSequence ≥ 0xFFFFFFFD.

Phantom signaturesSchnorr/ECDSA validation before broadcast (BIP-66 + bitcoinjs).

Race conditionsUNIQUE pubkey index in DB; sign requests serialized per pool.

Historical attacks → blocked

Known Attack	Defense
Kray `2b0ea40c` (SIGHASH_SINGLE\|ANYONECANPAY)	Rejected
Atomicals “0-yuan” (zero-value drain)	Rejected
Cenotaph rune burn (out-of-range pointer/edict)	Rejected
Inflated-reserve spoof (server lies about pool balance)	Rejected
Phantom signatures (r=0 / s=0)	Rejected
OP_RETURN burn drain (value > 0)	Rejected
Mempool griefing (far-future locktime)	Rejected

25/25 attack vectors verified by the simulation suite at scripts/simulate-user-pool-attacks.js.

Install — one command

macOS / Linux / Windows (via WSL). Takes about 5 minutes total. Open your terminal (macOS: press ⌘ + Space, type “Terminal”) and paste:

curl -fsSL https://www.kray.space/pool.sh | bash

The installer checks that Node.js 20+ is present (offers to install it if not), downloads the open-source agent from GitHub, and sets up the kray-pool-agent command. It never asks for keys or funds — you can read the script before running it.

Then: 3 steps to go live

# 1. Create your pool (interactive wizard, ~2 min) kray-pool-agent setup # → Choose a password (12+ chars) # → Enter pool name, your owner bc1p address # → Pick Single-rune (BTC + 1 rune) or Multi-rune # → Set your fee % (e.g. 0.3) # → WRITE DOWN the 12 words it shows you! (your mnemonic) # → It prints a bc1p... pool address # 2. Fund the pool address with BTC + your Rune (wait 1 confirmation) # The ratio of BTC:Rune you send sets the initial price. # 3. Go live kray-pool-agent start # → Enter your password → pool goes ONLINE on /swap

Prefer to install manually? (git clone)

git clone https://github.com/tomkray/kray-pool-agent cd kray-pool-agent npm install npm link # exposes the `kray-pool-agent` command

Two wallets, two jobs — keep them separate

During setup the agent creates a brand-new wallet that exists only for your pool. You never deposit into your personal wallet, and you never put personal funds into the pool wallet. Each one has exactly one job:

Your owner walletYour everyday wallet (KrayWallet). It signs management actions — pause, fees, pairs — and that's all. It never holds pool funds, and the pool never touches it.

The pool walletFresh 12-word wallet generated on your machine during setup. It holds the pool's BTC + Runes and signs swaps. Stored on disk encrypted (AES-256-GCM + Scrypt) — unlocked only in memory while the daemon runs.

The 12 words the setup shows you are full ownership of the pool funds. Write them on paper, keep them offline, never photograph or paste them anywhere. The password only unlocks the encrypted file on your machine — the 12 words recover everything even if the machine burns down.

Funding the pool — how to send, what it means

After setup prints your pool address (bc1p…), send it two things from any wallet you like: some BTC and some of your Rune. Wait for 1 confirmation. That's the whole deposit — those coins sitting at that address are the pool. Anyone can verify them on-chain.

The ratio you deposit sets the starting price. Example: deposit 0.01 BTC (丰 1,000,000 sats) + 100,000 RUNE → the pool opens at 丰 10 sats per RUNE. From there the AMM curve moves the price with every swap, and each swap pays your fee straight into the pool — your liquidity grows on-chain.

Tip: send the Rune in a single clean UTXO (the /tools page has Split/Transfer helpers if you need to organize UTXOs first).

Your exit is always yours — withdrawing

The pool address is a standard Taproot address (BIP86, derivation m/86'/0'/0'/0/0 — the first address of any modern wallet). To close shop:

Stop the daemon (Ctrl+C) — pool goes offline, no more swaps.
Restore the 12 words in any Taproot wallet — KrayWallet, Sparrow, Unisat…
Your BTC + Runes are right there, at the first address. Send them wherever you want.

No permission needed, no lock-ups, no withdrawal function that can be frozen. Kray Space cannot stop you from leaving — it never had your keys.

Where should it run?

Your pool is online while the daemon is running. Close the laptop, pool goes offline (safely — funds never move) and disappears from /swap until you start it again. Three common setups:

Your computerPerfect for trying it out. Pool is online while the terminal window is open.

Raspberry Pi (~$50)Sips less power than a light bulb, runs 24/7 at home. The sovereign favorite.

Small VPS (~$5/mo)Always online in a datacenter. Keys live encrypted on the server — use a dedicated pool wallet.

Day-to-day operation

Once kray-pool-agent start is running, your pool appears on the public /swap page with an online dot. Anyone can swap against it. Every swap is logged in this dashboard — including any rejected ones (so you'll see attacks if they happen, with the rule that blocked them).

To pause the pool, just kill the daemon (Ctrl+C) — Kray Space marks it offline within 30 seconds and stops routing swaps to you. Restart to resume.

Auditing the code yourself

Both halves of the system are open-source and minimal:

kray-pool-agent/src/core/verifier.js — the immutable rules the daemon enforces
kray-space/src/defi/poolAgentVerifier.js — the same rules re-applied by the server
kray-space/scripts/simulate-user-pool-attacks.js — runnable attack suite (25 cases)

Full security doc → Source on GitHub