Skip to main content

Bitcoin & On-Chain

The smallest unit of Bitcoin, equal to 0.00000001 BTC. All amounts in KaleidoSwap are denominated in satoshis.
One-thousandth of a satoshi, used for precise calculations in Lightning Network payments (not enforceable on-chain).
A discrete chunk of Bitcoin that can be spent. RGB assets are anchored to specific UTXOs on the Bitcoin blockchain.
When a Bitcoin transaction is included in a block on the blockchain. More confirmations mean higher security against reorganization.
The pool of unconfirmed Bitcoin transactions waiting to be included in the next block.
The cost per byte to include a transaction in a Bitcoin block, typically measured in satoshis per virtual byte (sat/vB).
A Bitcoin blockchain index service that wallets query for addresses, UTXOs, and transaction history instead of scanning the chain themselves. KaleidoSwap uses an Esplora endpoint for the node-less RGB-L1 account and for Liquid; a default is provided and you can supply your own.
A separate Bitcoin network used for testing, where coins have no real value.
A newer test network with more predictable block times, used for development and testing.
A custom Bitcoin Signet with fast, predictable blocks and no competition for block space, used as the main public test network for KaleidoSwap. Selectable when creating an account.
Regression test mode allowing developers to create local private Bitcoin networks for testing.

Lightning Network

A Layer 2 payment protocol built on Bitcoin enabling instant, low-cost transactions through off-chain payment channels.
A bidirectional payment channel between two Lightning nodes allowing multiple transactions without touching the blockchain until the channel is closed.
The total amount of Bitcoin (and potentially RGB assets) locked in a payment channel, determining the maximum transaction size.
The amount of funds others can send to you through a channel. Determined by your channel partner’s balance.
The amount of funds you can send through a channel. Determined by your balance in the channel.
The standard Lightning Network invoice format for requesting payments. Contains payment amount, recipient, and other metadata.
A human-readable payment identifier that looks like an email address (user@domain.com) and resolves to a Lightning invoice behind the scenes. Accepted as a withdrawal destination in the KaleidoSwap Extension.
A set of protocols that let a Lightning wallet fetch payment details from a URL, enabling reusable payment links, withdrawals, and authentication. Supported by the Extension and exposed to DApps through WebLN.
A Lightning payment method allowing spontaneous payments without requiring an invoice, used for pushing assets or funds.
A conditional payment mechanism ensuring atomic transactions across Lightning channels using cryptographic hashes and time locks.
The preimage is the secret that unlocks an HTLC; the payment hash is its hash, published in the invoice or swap. Revealing the preimage claims the payment, which is what makes an atomic swap atomic — both legs settle with the same secret, or neither does. KaleidoSwap returns a payment_hash when a swap is initiated.
The process of finding a path through the Lightning Network to deliver a payment from sender to receiver.
Two ways to settle a channel on-chain. In a cooperative close both peers agree and sign the final state, which is cheap and confirms quickly. In a force close one side publishes the latest state unilaterally — used when the peer is unreachable or the channel is stuck — and funds stay time-locked until the delay expires. Recovering from a channel backup force-closes the channels it contains.

LSP & Liquidity

A service provider that offers Lightning infrastructure, liquidity, and channel management services to users.
A set of standardized protocols for Lightning Service Providers, defining how they interact with clients.
The first LSP specification defining channel opening and liquidity services. KaleidoSwap implements LSPS1 for RGB-enabled channels.
A request from a client to an LSP to open a Lightning channel with specific parameters like capacity and asset allocation.
The LSPS1 object that tracks a channel request through its lifecycle: created, paid, opened. Each order has an ID you can fetch, pay, or submit a rate decision against — kaleido channel order create | get | pay | decide in the CLI, and the Buy Channel tab in the Desktop App.
An actor that continuously quotes both sides of a trading pair and supplies the liquidity swaps execute against. The KaleidoSwap LSP bootstraps this role today; external market makers join from 2027. Not to be confused with the maker of an individual swap, defined under Trading & Market.

Bitcoin Layers & Assets

A digital asset created using the RGB protocol. RGB assets are client-validated smart contracts that leverage Bitcoin’s security while maintaining scalability and privacy through off-chain validation.
A Lightning node that understands RGB assets, so channels can carry BTC and RGB tokens at once. It holds your keys, manages channels, and validates contracts locally. The Desktop App connects to one for every wallet, channel, and payment operation; in the Extension it is an optional, experimental account. See node hosting.
Non-Inflatable Asset — the RGB interface for fixed-supply fungible tokens, similar to ERC-20 on Ethereum. Used for creating and managing divisible assets like stablecoins or utility tokens. This is the asset type KaleidoSwap trades today.
Inflatable Fungible Asset — the RGB interface for fungible tokens whose supply can be expanded or replaced by the issuer (mint/burn). Supported by KaleidoSwap.
Unique Digital Asset — the RGB interface for non-fungible tokens (NFTs), comparable to ERC-721. Used for unique digital assets and collectibles. Supported by KaleidoSwap.
Collectible Fungible Asset — the RGB interface for collectibles with rich media and metadata. Supported by KaleidoSwap.
A unique identifier for an RGB asset, typically in the format rgb:xxxxxx-xxxxxx-xxxxxx. Each asset has a globally unique ID derived from its genesis transaction.
A core RGB concept where asset state and transaction history are validated by clients rather than being stored on the blockchain. This provides enhanced privacy and scalability.
A Bitcoin UTXO that carries RGB asset state alongside its sats. You need at least one available colored UTXO to receive or trade RGB assets on-chain; the Desktop App can create one for you during a deposit if you have a BTC balance. A UTXO with no asset state attached is sometimes called a vanilla UTXO.
A receiving commitment that lets a sender transfer an RGB asset to you without learning which UTXO it lands on. It replaces the address in on-chain RGB transfers, so an RGB withdrawal asks for a blinded UTXO where a BTC withdrawal asks for an address.
The payment request format for RGB transfers, starting with rgb:. It encodes the asset, the amount, and the blinded receive commitment. The node-less RGB-L1 account creates blinded invoices automatically; with RLN connected you can also receive RGB over Lightning.
A relay service that passes RGB consignments between sender and recipient, since RGB transfer data travels off-chain and never touches the blockchain. Configured alongside the node endpoint in the Desktop App and in the Extension’s RGB-L1 settings.
A data package containing all necessary information to validate an RGB asset transfer, including proofs, history, and state transitions.
The blueprint defining an RGB asset’s properties, state transitions, and validation rules. Different interfaces (NIA, IFA, UDA, CFA — formerly RGB20/21/25) enable different asset types.
A Bitcoin layer for BTC and native assets with Lightning send and receive. In the KaleidoSwap Extension it is a self-custodial account derived from your recovery phrase, and it also powers Flashnet swaps and the cross-chain bridge.
A liquidity network on Spark. KaleidoSwap uses Flashnet routes as a swap venue, and Flashnet Orchestra as the routing service behind the cross-chain bridge.
A Bitcoin layer based on the Ark design, where funds are held as VTXOs (virtual UTXOs) rather than on-chain outputs. Moving in and out is called boarding and offboarding. Supported as an account in the Extension, with an optional rotating-address mode.
The unit of value in Arkade. Funds are held as virtual outputs that move off-chain rather than as on-chain UTXOs, which is what makes Arkade transfers instant and cheap. A VTXO has a lifecycle: it is created when you board, maintained while the account is in use, and settled on-chain when you offboard. The Extension exposes VTXO and lifecycle settings under Settings > Arkade.
A Bitcoin sidechain with confidential transactions, home to L-BTC and issued assets such as USDt. Supported in the Extension as a node-less, self-custodial account on mainnet by default.
Liquid Bitcoin — BTC held on the Liquid network, backed one-to-one by bitcoin locked on the mainchain. It is the base asset of the Liquid account in the Extension, alongside issued assets such as USDt, and is counted separately from your Spark, Arkade, Bitcoin L1, and Lightning balances.

Trading & Market

A trustless exchange of one asset for another that either completes entirely or fails entirely, with no possibility of partial execution.
A combination of two assets that can be traded against each other, e.g., BTC/USDT.
The first asset in a trading pair - what you’re buying or selling.
The second asset in a trading pair - what you’re paying with or receiving.
The number of decimal places an asset supports. For example, USDT typically has 6 decimals of precision.
A request to get a price quote for swapping between two assets. Quotes are valid for a limited time.
The party providing liquidity by creating a swap offer that others can accept.
The party consuming liquidity by accepting an existing swap offer.
The difference between expected price and actual execution price, typically due to market movement or liquidity constraints. You can set a maximum acceptable slippage per trade; the swap fails rather than executing at a worse rate.
A source of quotes and liquidity a client can execute a swap against. The Extension can use KaleidoSwap maker pairs when RLN is connected, and Spark/Flashnet routes when Spark pools are available. At least one venue must be available to swap; venues are optional for basic wallet features.
Moving funds between a Bitcoin layer and an external chain — in the Extension, between your Spark account and networks such as Ethereum, Base, Solana, or Tron. Distinct from a swap, which exchanges one asset for another inside your wallet. Atomic swaps between Bitcoin Layers need no bridge at all. See Bridge.
The current state of an atomic swap: Waiting, Pending, Succeeded, Expired, or Failed.

Swap Terms

The words the Swap SDK and the Maker API use.
The on-chain output that holds one side of a swap. It can be spent in two ways: claimed with the swap’s preimage, or refunded to the sender after the timeout.
A Lightning invoice whose payment stays pending until someone reveals the preimage. Until then the payer’s funds are locked, not sent; if the preimage never comes, the payment is released back.
The three swap shapes of the Boltz protocol. Submarine: on-chain funds pay a Lightning invoice. Reverse: a Lightning payment becomes on-chain funds. Chain: on-chain funds on one chain become on-chain funds on another.
The two ways out of a lockup. The receiver claims it with the preimage before the timeout; the sender refunds it after the timeout if nobody claimed.
The block height at which a lockup’s refund path opens. Claims must confirm before it.
A claim or refund that you and the maker sign together with MuSig2, a scheme that merges two signatures into one. It is cheaper than the script path, and a cooperative refund does not wait for the timeout.
Spending a lockup alone, through its script: with the preimage and your signature for a claim, or your signature after the timeout for a refund. It never depends on the maker.
The Taproot scripts (claim leaf and refund leaf) a lockup commits to. Your client rebuilds it from its own key and checks it against the maker’s address before funding.
A pair card is the maker’s terms for one route: limits, fees, and rate. Its hash (sent back as pairHash when you create a swap) makes the maker reject the swap if those terms changed since you showed them.
A secret credential the maker returns once, when a swap is created. It authorizes accepting a re-quote and cooperative refunds for that swap. Store it with the swap.
A Partially Signed Elements Transaction, Liquid’s equivalent of a PSBT. L-USDT claims and refunds use one that your wallet funds with L-BTC for the fee before the SDK finalizes it.
rgb-lib is the wallet library that holds and validates RGB assets. Coloring a transaction means attaching an RGB asset transfer to it; the Swap SDK builds the Bitcoin side and your rgb-lib wallet colors it.
The request-for-quote route the maker serves for Lightning ↔ Arkade swaps. Within Arkade, the lock is a VHTLC, Arkade’s version of a hash time-locked contract.
A custom Bitcoin signet with 30-second blocks, used as KaleidoSwap’s test network. Its addresses look like testnet addresses, but it is a separate chain: use Mutinynet wallets, faucets, and explorers with it.

Wallet, Keys & Security

The 12 or 24-word phrase that restores your entire wallet, also called a mnemonic or seed phrase. One recovery phrase derives every account: in the Extension it controls Spark, Arkade, Liquid, and RGB-L1 plus the default Nostr identity. Anyone who has it controls your funds, so keep it offline and never share it.
The public portion of a cryptographic key pair, safe to share. Used to receive payments and verify signatures.
The secret portion of a cryptographic key pair, never to be shared. Used to sign transactions and prove ownership.
A scheme for generating multiple keys from a single recovery phrase in a deterministic way.
A wallet that can view balances and transactions but cannot sign or send transactions.
A backup file containing essential data to recover Lightning channel funds in case of data loss.
An encrypted cloud backup of RGB state for the node-less RGB-L1 account, written automatically on every receive alongside a local file backup. On re-import, onboarding offers to restore from it — never without your explicit consent. RLN state is recovered from the node’s own backup material instead.

Connectivity & Identity

A web app that talks to your wallet through injected browser providers instead of asking for keys. The KaleidoSwap Extension exposes WebLN, WebBTC, and Nostr providers to pages you approve, and prompts you for anything sensitive. See DApp connectivity.
The standard browser provider for Lightning, injected at window.webln. Lets an approved page request invoices, payments, message signing, keysend, and LNURL handling.
The companion browser provider for on-chain Bitcoin, injected at window.webbtc, for address and transaction requests from approved pages.
An open protocol for signed messages relayed between servers, used for identity and social apps. The Extension derives a Nostr identity from your recovery phrase, or imports one you already have.
The two halves of a Nostr identity: npub1… is your public key, safe to share; nsec1… is your private key. Anyone holding your nsec can sign events and act as you — never share it.
The standard for in-page Nostr signing, injected at window.nostr. An approved page can request your public key, have events signed, and encrypt or decrypt direct messages without ever seeing your key.
Remote signing for Nostr apps that cannot use an in-page provider. The Extension generates a bunker:// connection string you paste into the app; signing requests then travel over relays and are approved in the extension.
NIP-47 — a way to let an external app control a wallet over Nostr relays, paired with a nostr+walletconnect:// string or QR code and constrained by amount-aware budgets. Also used to reach a remote RGB Lightning Node so the node itself stays private.
A Lightning payment published as a Nostr event, typically as a tip on a note. Zaps made through NWC are validated and correlated with wallet activity.

KaleidoSwap Platform

A Lightning Service Provider that supports RGB assets in payment channels, enabling instant RGB asset transfers over Lightning.
Which rail a side of a swap settles on. Each swap leg names an asset_id and a layer, so one trade can cross rails — BTC_LN to RGB_LN, for example. Market quotes accept BTC_LN, RGB_LN, and BTC_L1 (BTC_ONCHAIN is a legacy alias).
A compact string encoding all parameters of a swap transaction, used for coordinating atomic swaps between parties.
The method used to finalize an asset transfer - either LIGHTNING (instant via payment channels) or ONCHAIN (via Bitcoin transactions).
The process of transferring RGB assets through Lightning channels using keysend after a channel is opened.
When market rates change significantly during order processing, users can choose to accept the new rate or request a refund.
The SDK surfaces KaleidoSwap clients are built on. The Swap SDK (@kaleidorg/swap-sdk, kaleidorg_swap_sdk) adds non-custodial swaps against the maker to any wallet or app, in TypeScript, Python, React Native, and Rust; see the SDK docs. @kaleidorg/wallet-engine provides wallet primitives across protocols (TypeScript). The Node SDK (kaleido-sdk) drives an RGB Lightning Node and powers the CLI; see Node SDK. Third-party integrations use the same interfaces our own apps do.
An autonomous, non-custodial Bitcoin L2 agent that manages a Lightning and RGB portfolio, rebalances with atomic swaps, and buys channel liquidity on its own. Keys stay in the local wallet and RGB Lightning Node, and every trade settles as an atomic HTLC swap. See KaleidoAgent.
The reasoning and tool-calling engine behind agentic KaleidoSwap wallets. The model runs on your device, or on a desktop you explicitly pair, and drives Spark, RGB Lightning, Arkade, and Liquid from one tool contract by chat or voice. See KaleidoMind.
This glossary is continuously updated. If you encounter unfamiliar terms not listed here, please let us know via our support channels.