Topics by category

Short definitions for technical terms that show up in our blog posts.

A-ZBy category

Bitcoin

  • AssumeUTXO

    A Bitcoin Core feature that lets a new node start from a hashed UTXO snapshot instead of rebuilding the set from genesis.

  • BIP 157

    A Bitcoin peer-to-peer extension that lets light clients fetch compact block filters from full nodes, scanning the chain without leaking addresses.

  • BIP 158

    The compact block filter format for Bitcoin. A small Golomb-coded set built per block that light clients can test locally to find relevant transactions.

  • BIP 324

    An encrypted, authenticated transport for the Bitcoin peer-to-peer protocol, replacing the older plaintext format.

  • BIP 329

    A standard JSON Lines format for wallet labels, including private notes for transactions, addresses, public keys, and UTXOs, so they stay portable across wallets.

  • BIP 353

    Human-readable Bitcoin payment instructions in DNSSEC-signed TXT records, letting a wallet resolve `name@domain` to an address or BOLT 12 offer.

  • DLC

    Discreet Log Contracts are Bitcoin contracts whose settlement depends on a signed statement from an oracle, without the oracle seeing the contract or holding any funds.

  • Erlay

    A bandwidth-efficient Bitcoin relay protocol where peers compare compact transaction summaries instead of flooding every transaction to every peer.

  • Mempool

    The set of valid but unconfirmed transactions each full node keeps in memory, from which miners and fee estimators pull candidates.

  • Miniscript

    A structured language for Bitcoin scripts that is easy to analyze, compose, and sign with a generic wallet.

  • OP_CTV

    A proposed Bitcoin opcode that lets a transaction commit in advance to how its coins will be spent.

  • Output descriptors

    A compact text format that describes exactly how a wallet derives its addresses and scripts from its keys, so any compatible wallet can import it.

  • PSBT

    Partially Signed Bitcoin Transaction: a standard format for transactions that are still being constructed or signed, used by wallets and coordinators.

  • SegWit

    Segregated Witness: a 2017 Bitcoin soft fork that fixed transaction malleability, expanded block capacity, and made Lightning possible.

  • Silent Payments

    A way to receive Bitcoin to a reusable static address without reusing on-chain addresses.

  • Taproot

    The 2021 Bitcoin soft fork that introduced Schnorr signatures, a new output type, and a new script system, all under a single on-chain footprint.

  • UTXO

    Bitcoin's accounting model: a wallet's balance is the sum of every output addressed to it that has not yet been spent.

Lightning

  • Blinded paths

    A Lightning feature where the receiver supplies a partial route with encrypted hop identities, so the sender never learns what the destination is.

  • BOLT 11

    The legacy Lightning invoice format where the sender scans a bech32 string to pay a fixed amount to a fixed pubkey before it expires.

  • BOLT 12

    A Lightning specification for reusable payment offers that replace single-use invoices.

  • Channel splicing

    Resizing a Lightning channel without closing it by adding or removing funds in a single on-chain transaction.

  • Eltoo

    A proposed Lightning channel update protocol that lets the latest channel state replace earlier ones without penalty transactions.

  • Gossip

    The Lightning Network's peer-to-peer protocol for announcing channels and routing policies, so every node can build a view of the public graph.

  • HTLC

    A conditional Bitcoin payment that settles when the receiver reveals a preimage and refunds after a timeout, making it Lightning's routing primitive.

  • LDK

    A Rust library for embedding a Lightning node inside a wallet or other application.

Privacy

  • CoinJoin

    A collaborative Bitcoin transaction that pools inputs from multiple participants to defeat the common input ownership heuristic.

  • Coinswap

    Atomic multi-hop swaps that move coins through intermediate keys so the spender of an input cannot be linked to the receiver of the final output.

  • Onion routing

    A privacy technique that relays traffic through a chain of intermediate nodes wrapped in layered encryption, so no single hop can link the sender to the destination. The technique behind Tor.

  • Payjoin

    A cooperative Bitcoin transaction where the receiver also contributes an input, making it harder to tell who paid whom and improving on-chain privacy.

Ecash

  • Ecash

    Digital bearer tokens issued by a mint using blind signatures, so that spending and redeeming cannot be linked to the original withdrawal.

  • Fedimint

    A federated Chaumian ecash system where a group of guardians jointly custody the underlying bitcoin.

Mining

  • Stratum V2

    A next-generation Bitcoin mining protocol that lets individual miners build their own block templates.

Nostr

  • Blossom

    A small HTTP protocol for storing files (blobs) on servers, addressed by their SHA-256 hash and authenticated with Nostr keys.

  • NIP-05

    A Nostr spec that maps human-readable identifiers like `name@domain.com` to public keys via a JSON file hosted on the domain.

  • NIP-29

    A Nostr spec for relay-based groups. The hosting relay owns the membership list, the moderation log, and the stream of group messages.

  • NIP-32

    A Nostr spec for labels: signed events that attach a tag to another event, a pubkey, a relay, or a topic, for client-side moderation and filtering.

  • NIP-44

    Nostr's current encryption standard for direct messages and other private content, designed to hide the message and its length from everyone but the recipient.

  • NIP-96

    An HTTP API for file storage servers that Nostr clients can upload to and then reference by URL from events, without bloating relays.

  • NIPs

    Nostr Implementation Possibilities: the numbered specifications that define how clients and relays behave.

  • Nostr

    A simple, open protocol where users sign events with their own keys and publish them to relays anyone can run, enabling censorship-resistant social networking with no single owner.

  • Nostr Wallet Connect

    A Nostr protocol that lets a client send and receive Lightning payments through a user-controlled wallet, communicating over relays.

  • Outbox model

    A Nostr client pattern where each user publishes their own relay list, so other clients know where to read their notes and deliver mentions.

  • Private DMs

    The current standard for private direct messages on Nostr, using gift wrap to hide sender, receiver, and metadata from relays.

  • Relays

    The small servers that store and forward signed events on Nostr.

  • Remote signing

    A Nostr protocol for signing events with a key that lives on a different device or service than the client composing the event.

  • Web of Trust

    Reputation as a graph rather than an authority-managed list. On Nostr, scoring the social graph turns it into a per-user filter for events.

  • Zaps

    A way to send bitcoin to a Nostr post over Lightning, where the payment appears publicly beneath the note for everyone to see.

Scaling

  • Ark

    A second-layer Bitcoin protocol that uses a shared UTXO and a coordinator to let users transact off-chain without opening channels.