⚡ The Lightning + Nostr Glossary: Every Term You Need to Know 🟣

Yo fam! 👋

Bitcoin is evolving FAST, and two technologies are changing the game right now:

⚡ Lightning Network - Instant, near-free Bitcoin payments

🟣 Nostr - Censorship-resistant social and communication protocol

Together, they're building the infrastructure for a world where your money AND your messages travel without ANY gatekeeper's permission. No banks. No Big Tech. Just pure peer-to-peer freedom.

This glossary covers every major term you'll encounter in the Lightning + Nostr ecosystem. Zero developer experience required!

Every term follows this format:

What it is - Plain English definition
Think of it like - Real-world analogy you already understand
Why it matters - Why you should actually care
Watch out for - Common traps or misconceptions (when relevant)

Let's dive in! 🚀

PART 1 — THE LIGHTNING NETWORK ⚡

Bitcoin at the Speed of the Internet

The Lightning Network is a "second layer" built on top of Bitcoin that enables near-instant, near-free payments without recording every transaction on the main blockchain.

The key concept: Lightning works by opening a private "payment channel" between two parties, and transactions happen off-chain until one of them wants to settle to Bitcoin proper. Think of it like running a tab at a bar all night and settling up at the end.

💧 Inbound Liquidity

What it is: The amount of Bitcoin that other people have available to send TO YOU through your Lightning channel — your capacity to receive payments.

Think of it like: The number of lanes on the highway leading INTO your city. If there are no lanes, no one can get in — even if they want to.

Why it matters: If you have ZERO inbound liquidity, you literally cannot receive any Lightning payments. Period. For anyone running a merchant node, a creator tip page, or any "Zappable" content, this is the FIRST thing that needs to be set up.

Watch out for: ⚠️ New Lightning nodes start with ZERO inbound liquidity. You have to actively acquire it — either by spending Bitcoin first (which flips liquidity to your side) or by leasing a channel from a service provider.

💸 Outbound Liquidity

What it is: The amount of Bitcoin you currently have available to send through your Lightning channel — your capacity to make payments.

Think of it like: The balance in your checking account. If it hits zero, your card gets declined — even if you have money in savings elsewhere.

Why it matters: If your outbound liquidity runs dry, you can't pay anyone on Lightning until you refill the channel. Apps built on Lightning need to monitor this and alert users before it becomes a problem.

Watch out for: ⚖️ Outbound and inbound liquidity are a SEESAW. Every payment you send increases your inbound, and every payment you receive increases your outbound. Managing both is the core operational challenge of running a Lightning node.

🏪 Channel Leasing

What it is: A service where a well-connected Lightning node operator opens a channel to your node in exchange for an upfront fee — giving you instant inbound liquidity without having to wait for organic channel partners.

Think of it like: Renting shelf space in a busy store. You pay the store owner a fee, and in return, customers can now find and buy your product — without you having to build your own store first.

Why it matters: It's the FASTEST solution for getting a new Lightning node operational. Instead of waiting weeks for inbound liquidity to build organically, you pay a one-time leasing fee and can receive payments immediately. 🎯

Watch out for: ⏰ Leases are time-limited. When the lease expires, the channel may close and you lose that inbound capacity unless you renew. Factor the ongoing leasing cost into your node's economics.

🔧 Splicing

What it is: A protocol upgrade that lets you add or remove Bitcoin from a Lightning channel without closing and reopening it — the channel stays live and operational during the entire process.

Think of it like: Being able to refuel your car while it's still moving on the highway, instead of having to pull over, shut the engine off, refuel, and restart. 🚗⛽

Why it matters: Before splicing, resizing a channel meant paying TWO sets of on-chain Bitcoin transaction fees (close + reopen) and being offline during the process. Splicing cuts that to ONE transaction and keeps the channel active throughout, making Lightning dramatically cheaper and easier to manage.

Watch out for: 🆕 Splicing is a newer feature — not all Lightning node software supported it at launch. Check that your node implementation supports it before expecting seamless resizing.

🔒 HTLCs (Hashed Time Locked Contracts)

What it is: The "smart contract" mechanism that allows Lightning payments to safely hop across multiple nodes to reach their destination — with a mathematical guarantee that the payment is either fully delivered or fully refunded.

Think of it like: A chain of locked boxes. Each box can only be opened with a specific key. The payment travels from box to box; once the final recipient opens their box (revealing the key), every box in the chain unlocks simultaneously and everyone gets paid — or the chain times out and every box returns its contents. 📦🔑

Why it matters: HTLCs are what make multi-hop Lightning payments TRUSTLESS. You don't need to trust any of the intermediate nodes your payment passes through — the math ensures they can't steal the funds in transit.

Watch out for: If a payment gets "stuck" — committed but not yet resolved — it means the time lock hasn't expired yet and the funds are temporarily frozen. This is rare, but when it happens the user must wait for the timelock to expire before the funds are released back to them.

🎯 PTLCs (Point Time Locked Contracts)

What it is: The next evolution of HTLCs — instead of using a shared hash to lock payments across a route, PTLCs use cryptographic "points" (public keys) that make each hop of a payment unlinkable from the others, dramatically improving privacy.

Think of it like: HTLCs are like a chain of doors that all use the SAME key — if anyone sees the key, they can identify the whole route. PTLCs are like a chain of doors where each one uses a completely DIFFERENT key, so no single person can tell where the payment started or ended. 🚪🔑

Why it matters: With HTLCs, a routing node that processes your payment can theoretically correlate your transaction across the network by watching for the same hash. PTLCs eliminate this correlation attack — your payment path becomes private even to the nodes that route it. 🕵️

Watch out for: PTLCs require Taproot support on Bitcoin (activated in 2021) and upgrades across the entire Lightning protocol stack. They're rolling out in 2025–2026 and aren't yet universal.

📜 BOLTs (Basis of Lightning Technology)

What it is: The official technical rulebooks that define how the Lightning Network works — covering everything from how two nodes connect, to how payments are routed, to what a payment invoice looks like.

Think of it like: The RFC standards that defined how email works. Anyone who wants to build an email client follows the same specs so that Gmail can send to Outlook, Hotmail, and ProtonMail. BOLTs do the same for Lightning — so an LND node can pay a CLN node can pay a Phoenix wallet, seamlessly. 📧

Why it matters: BOLTs are what prevent Lightning from fragmenting into isolated, incompatible networks. BOLT 12 ("Offers") is the most important recent upgrade — it enables reusable, static payment links instead of single-use invoices, making subscription billing and recurring payments possible on Lightning.

Watch out for: BOLTs are a floor, not a ceiling. Individual node implementations (LND, CLN, Eclair) sometimes add features ahead of the BOLT spec — which means not every feature works cross-implementation yet.

PART 2 — NOSTR 🟣

The Uncensorable Social Layer

Nostr is an open protocol (not a company, not an app) that lets anyone publish and receive messages using nothing but a cryptographic key pair — no username, no phone number, no email required.

Think of it as: A decentralized Twitter/X where no single entity can ban you, shadow-ban you, or delete your posts.

When you combine Nostr with Lightning, you get social media that can also send and receive money natively. 💰🤝

📋 NIPs (Nostr Implementation Possibilities)

What it is: The community-authored technical specifications that define how Nostr features work — the Nostr equivalent of Ethereum's EIPs or Bitcoin's BIPs.

Think of it like: Building codes for an open-source city. Anyone can propose a new building standard (NIP), the community debates it, and if it's accepted, all builders follow it so that every building is compatible with every other. 🏗️

Why it matters: NIPs are how Nostr grows without a central authority. Every feature — from how profiles work, to how payments are attached to posts, to how group chats are encrypted — is defined by a NIP. Knowing which NIPs matter tells you what any Nostr client is capable of.

Watch out for: ⚠️ Not every Nostr client supports every NIP. If you're trying to use a specific feature (like private group chats or Lightning payments), check that both the sender's and recipient's apps support the relevant NIPs.

📝 Events (Nostr Primitives)

What it is: The atomic unit of all Nostr activity — every post, profile update, follow, tip, and deletion on Nostr is an "event," which is a small JSON package containing the author's public key, a timestamp, the content, and a cryptographic signature.

Think of it like: A signed, timestamped sticky note. You write your message, sign your name, stick a timestamp on it, and hand copies to multiple bulletin boards (relays) simultaneously. Anyone can verify it's genuinely from you — and no single board can destroy all copies. 📌✍️

Why it matters: Because every event is cryptographically signed, there's no way to fake a post from someone else, and there's no central server that can delete your content — it exists on every relay that received it.

Watch out for: 🚨 Deletion on Nostr is NOT guaranteed. You can publish a "delete request" event, but relays are not obligated to honor it. Consider everything you post on Nostr to be PERMANENT.

🏷️ Kinds (Nostr)

What it is: The numeric category tag on every Nostr event that tells clients and relays what type of data the event contains — Kind 1 is a regular post, Kind 0 is a profile update, Kind 9734 is a tip request, and so on.

Think of it like: The subject line in an email, except it's a number instead of words. Email clients filter by subject lines; Nostr clients filter by Kind numbers to know which events to display in which part of the app. 📬

Why it matters: Kinds are what allow a single Nostr protocol to power wildly different apps — a social media feed, a marketplace, a tipping system, and a group chat can all coexist because each uses different Kinds that apps sort automatically.

Watch out for: Because the Kind system is open and extensible, not every client will know what to do with every Kind. A new app may use a custom Kind that older clients simply ignore — which is a feature (forwards compatibility), not a bug. ✅

⚡💜 Zaps (NIP-57)

What it is: The Nostr-native system for attaching Lightning Bitcoin micropayments to any post, profile, or piece of content — letting anyone send a tip to a creator with a single click, with cryptographic proof of payment posted back to the network.

Think of it like: Twitter's "Like" button, except instead of giving the creator a dopamine hit, it gives them actual Bitcoin. And instead of just a heart icon, it generates a publicly verifiable receipt that proves the payment happened. 💰❤️

Why it matters: Zaps are what turn Nostr from a "decentralized Twitter" into a genuine "value-for-value" economy. Creators get paid directly by their audience — NO ad revenue, NO subscription middleman, NO platform taking a cut. Every post becomes a potential revenue stream. 🚀

Watch out for: To receive Zaps, you need to have a Lightning Address set up in your Nostr profile (see LUD-16 below). Without one, people can't Zap you even if they want to. 🔌

📧⚡ LUD-16 / Lightning Address

What it is: A human-readable payment identifier that looks exactly like an email address (e.g., [email protected]) but is actually a shortcut that automatically generates a Lightning payment invoice when someone sends to it.

Think of it like: An email address that receives money instead of messages. Instead of giving someone a long, unreadable Lightning invoice string every time they want to pay you, you give them your Lightning Address once and it handles invoice generation automatically, forever. 📬💸

Why it matters: Lightning Addresses solve the UX problem of Lightning payments. Without them, you'd need to generate a new invoice for every single payment — which is impractical for tipping, storefronts, or any situation where many different people might want to pay you at once.

Watch out for: Your Lightning Address is only as reliable as the wallet or service hosting it. If the provider goes offline, your address stops working. For serious use, self-host or use a reliable service. 🔧

🔗 LNURL-pay

What it is: The underlying protocol that powers Lightning Addresses and other "pull payment" flows — it allows a website or wallet to dynamically generate a Lightning invoice on request, rather than requiring a pre-generated static invoice.

Think of it like: The plumbing behind a vending machine. When you select a product, the machine dynamically calculates the price and dispenses the right item — you don't need to hand it a pre-written check. LNURL-pay is that behind-the-scenes calculation engine. 🏪⚙️

Why it matters: LNURL-pay is what makes Lightning practical for commerce. Without it, every Lightning payment would require manual invoice creation and sharing — like writing a personal check for every purchase. With it, payment flows become as smooth as a credit card tap. 💳✨

Watch out for: LNURL-pay relies on a web server responding to the payment request in real time. If the server is down when someone tries to pay, the payment fails — even though the payer is willing and has the funds. ⚠️

PART 3 — HOW PAYMENTS & APPS CONNECT 🔌

The Bridges Between Your Wallet, Your Keys, and the Internet

This section covers the protocols and tools that connect Lightning wallets to Nostr apps, websites, and services — without requiring you to hand over your private keys or trust a third party with your funds.

🟣⚡ NWC — Nostr Wallet Connect (NIP-47)

What it is: A protocol that lets any app or website trigger payments from your Lightning wallet using an encrypted Nostr connection — without the app ever having custody of your funds or access to your private keys.

Think of it like: Authorizing your bank's app to initiate payments, but it's YOUR bank, not a fintech startup, holding the money. The app can tell your wallet "pay this invoice," but only your wallet actually holds and sends the Bitcoin. 🏦🔐

Why it matters: NWC is the payment API of the decentralized internet. Any app — a Nostr client, a podcast player, a game — can offer one-tap Lightning payments by connecting to your wallet through NWC, instead of asking you to build a wallet into their app or give them your keys.

Watch out for: 🎯 NWC connections can have budgets and permissions attached. SET SPENDING LIMITS on any NWC connection you create, especially for apps you're not 100% sure about. A budget cap means even if an app is compromised, it can only spend up to your set limit.

🌐⚡ WebLN

What it is: A browser standard that lets websites interact with your Lightning wallet through a browser extension (like Alby), similar to how MetaMask lets websites interact with your Ethereum wallet — enabling one-click Lightning payments directly on web pages.

Think of it like: Apple Pay for Lightning. Instead of being redirected to a payment page or scanning a QR code, you click a button on a website and your wallet extension handles the rest — all without leaving the page. 🍎💳

Why it matters: WebLN is what makes Lightning commerce feel like normal internet shopping. Developers can add webln.sendPayment(invoice) to any webpage and instantly support Bitcoin micropayments — tipping, purchases, paywalls, subscriptions — with a single line of code. 💻✨

Watch out for: WebLN only works in browsers with a supporting extension installed (like Alby). Mobile web users typically need a separate NWC-connected wallet app instead, since browser extensions aren't available on iOS/Android. 📱

🔐 Amber (Nostr Event Signer)

What it is: An Android app that acts as a secure vault for your Nostr private key — other Nostr apps ask Amber for permission to sign events on your behalf, so your private key never has to be stored inside the app you're actually using.

Think of it like: A notary public you keep on your phone. Whenever any document (Nostr event) needs your signature, apps hand it to the notary, the notary shows you what you're signing and asks for approval, then sends back the signed document — the notary never gives your signature stamp to the other app. 📝🛡️

Why it matters: The biggest security risk in Nostr is storing your private key inside every app you use — if any one of those apps is hacked or has a bug, your key is compromised. Amber centralizes key management in one secure place and removes it from everywhere else.

Watch out for: 🤖 Currently Android-only. iOS users need to use alternative signing solutions (like external hardware signers or web-based nsecbunkers). If you switch devices, ensure you've properly backed up your Nostr key before relying on Amber.

🤖💰 DVMs — Data Vending Machines (NIP-90)

What it is: A decentralized marketplace where you can request computational tasks — like AI image generation, speech-to-text transcription, or data analysis — and pay for the results instantly using a Lightning Zap.

Think of it like: A vending machine that dispenses data instead of snacks. You put in a request (and some Bitcoin), and out comes your result — whether that's a translated article, a generated image, or a processed audio file — from whoever in the network decides to fulfill your request. 🎰🤖

Why it matters: DVMs create a pay-as-you-go market for AI and computation that doesn't require a corporate subscription. Instead of paying OpenAI $20/month for access, you pay fractions of a cent per task, directly to whoever runs the compute — NO account, NO subscription, NO personal data required. 🚀

Watch out for: ⚠️ Because anyone can offer DVM services, quality varies. A low bid might get fulfilled by a less powerful provider. For important tasks, check the provider's reputation or set a higher maximum bid to attract better results.

🌸 Blossom (Decentralized Media Storage)

What it is: A protocol for storing images, videos, and other files on decentralized media servers using your Nostr identity — files are identified by a unique fingerprint (hash) rather than a URL, so they can be retrieved from any server that has a copy.

Think of it like: Google Drive, except instead of one company owning all your files, your photos and videos are spread across multiple independent servers — and any of them can serve your file if the others go down, because they're all identified by the same fingerprint. 📸☁️

Why it matters: Normal Nostr posts store text only. Any media attached to a post (images, video, audio) has to live somewhere — and if it lives on a centralized server, that server can take it down. Blossom ensures your media is as censorship-resistant as your posts. 🛡️

Watch out for: 🆕 Blossom is newer than core Nostr and isn't universally supported yet. Your media may not display correctly in all clients. If a server goes offline and no other server has a copy, the file is gone — spreading your content across multiple Blossom servers is the safe approach.

PART 4 — BUILDER TOOLS 🛠️

For Those Who Want to Go Deeper

You don't need to understand these to use Lightning or Nostr — but knowing they exist helps you understand what's possible and why certain apps work the way they do. These are the core developer kits that everything else is built on.

⚡🦀 LDK — Lightning Dev Kit

What it is: A modular, embeddable Lightning Network engine written in Rust that developers can drop directly into a mobile app or custom service — giving them full control over the Lightning experience without running a separate node daemon.

Think of it like: A car engine you can install in any vehicle you want to build, rather than having to buy the whole car from a manufacturer. You design the chassis and the dashboard; LDK powers everything under the hood. 🚗🔧

Why it matters: LDK is how Lightning gets embedded into consumer wallets on your phone. Apps like Phoenix and Mutiny Wallet use LDK-based architecture to offer self-custodial Lightning without requiring users to run a separate server. It's also how "JIT channels" work — where a channel is opened and funded at the same moment you receive your first payment. 📱⚡

Watch out for: LDK gives developers maximum flexibility but also maximum responsibility. Unlike running a managed node (like Voltage.cloud), developers using LDK own the security model. A bug in the integration layer can be costly. ⚠️

🟠🦀 BDK — Bitcoin Dev Kit

What it is: A modular Bitcoin wallet library that handles all the "base layer" Bitcoin operations — generating addresses, selecting which coins to spend, constructing and signing transactions, and syncing with the blockchain.

Think of it like: The financial accounting software running behind a bank teller's screen. The teller (the app) takes your request; BDK is what actually calculates balances, builds the transaction, and submits it to the network correctly. 🏦💻

Why it matters: BDK is the on-chain foundation that Lightning sits on top of. To open a Lightning channel, you first need to fund it with an on-chain Bitcoin transaction — BDK is what builds and manages that transaction. In the LDK ecosystem, BDK is the standard choice for this "base layer wallet" role. 🔗

Watch out for: BDK is a library, not a finished product. You won't interact with BDK directly as a user — but understanding that it exists explains why well-built Lightning wallets handle on-chain Bitcoin transactions cleanly and efficiently. ✅

🟣💻 NDK — Nostr Dev Kit

What it is: A TypeScript framework that gives developers high-level tools for building Nostr applications — handling relay connections, event subscriptions, caching, and social graph management without writing low-level networking code.

Think of it like: React for Nostr. React gives web developers ready-made building blocks for user interfaces so they don't have to code every button from scratch. NDK does the same for Nostr — developers get ready-made tools for subscriptions, relay management, and data syncing. ⚛️🛠️

Why it matters: NDK is why the Nostr app ecosystem has grown so quickly. Developers can build a functional Nostr client in DAYS instead of months because NDK abstracts away the complex relay logic. Most of the popular Nostr web apps you'll encounter are built on NDK. 🚀

Watch out for: Because NDK is so widely used, bugs in NDK can affect many apps simultaneously. When Nostr clients behave strangely in coordinated ways (like all having the same relay connection issue), NDK is often the common thread. 🔗

🔐⚡ VLS — Validating Lightning Signer

What it is: A security architecture that physically separates your Lightning node's "brain" (the routing and channel management software) from its "signing authority" (the component that authorizes transactions) — so that even if your node is hacked, the attacker cannot move funds.

Think of it like: A nuclear launch system that requires two separate keys turned simultaneously in different rooms. The node software can see all your channels and routing activity, but it can't actually spend any Bitcoin without a separate, isolated signer approving every transaction against a set of security rules. 🚀🔑🔑

Why it matters: Standard Lightning nodes keep signing keys and channel logic in the same process — meaning a single point of compromise can drain your node. VLS is the solution for high-value nodes (exchanges, institutional custody, large routing nodes) where losing funds to a hack is unacceptable. 🏦🛡️

Watch out for: VLS is an advanced security layer designed for serious deployments, not personal wallets. If you're running a small personal Lightning node, the operational complexity of VLS is overkill. It becomes relevant when you're running a node with significant Bitcoin under management or serving as a routing hub. ⚠️

📚 How to Use This Glossary

If you're new to Lightning: ⚡ Start with Part 1. Understand inbound and outbound liquidity COLD — they're the concepts that bite new Lightning users most often. The rest of Part 1 gives you the vocabulary to follow any technical Lightning conversation.

If you want to understand Nostr + Zaps: 🟣 Part 2 is your map. "Events," "Kinds," and "Zaps" are the three concepts that explain 90% of how Nostr works. Everything else in Part 2 is supporting infrastructure around those core ideas.

If you're evaluating Lightning-native apps or wallets: 🔌 Part 3 is the decision-making toolkit. Knowing whether an app uses NWC versus custodial payment handling tells you how much you actually control your funds.

If you're thinking about building something: 🛠️ Part 4 gives you the lay of the land. LDK + BDK is the Bitcoin/Lightning stack. NDK is the Nostr stack. VLS is the security layer for serious deployments. These are the four lego bricks everything gets built from.

💬 Questions?

Drop them in the comments! If there's a term you've seen in the Lightning or Nostr space that isn't here, reply with it and we'll add it. 👇

This is a living document — we'll update it as the Lightning + Nostr ecosystem continues to evolve through 2026. 🌱

DeFi University | Community Resource | February 2026 🎓✨

7:01

3 comments