Builder's Guide
  • Welcome to the Builder's Guide to the LND Galaxy!
  • The Lightning Network
    • Overview
    • Payment Channels
      • Lifecycle of a Payment Channel
      • Watchtowers
      • Understanding Sweeping
      • Etymology
    • The Gossip Network
      • Identifying Good Peers on the Lightning Network
    • Pathfinding
      • Finding routes in the Lightning Network
      • Channel Fees
      • Multipath Payments (MPP)
    • Lightning Network Invoices
      • Understanding Lightning Invoices
    • Making Payments
      • The Payment Cycle
      • Timelocks
      • ⭐Hashed Timelock Contract (HTLC)
      • Payment Etymology
      • ⭐What Makes a Good Routing Node
      • Understanding Submarine Swaps
      • Instant Submarine Swaps
    • Liquidity
      • ⭐Understanding Liquidity
      • Managing Liquidity on the Lightning Network
      • Liquidity Management for Lightning Merchants
      • How to Get Inbound Capacity on the Lightning Network
      • Lightning Service Provider
    • L402: Lightning HTTP 402 Protocol
      • Macaroons
      • L402
      • 📋Protocol Specification
      • Implementations and Links
    • Taproot Assets
      • Taproot Assets Protocol
      • Taproot Assets on Lightning
      • Edge Nodes
      • Taproot Assets Trustless Swap
      • FAQ
      • Glossary
  • Lightning Network Tools
    • LND
      • 🛠️Get Started
      • lnd.conf
      • First Steps With LND
      • Wallet Management
      • Sending Payments
      • Atomic Multi-path Payments (AMP)
      • Receiving Payments
      • Unconfirmed Bitcoin Transactions
      • Channel Fees
      • Inbound Channel Fees
      • Macaroons
      • Configuring Watchtowers
      • Pathfinding
      • Blinded Paths
      • Key Import
      • Secure Your Lightning Network Node
      • Configuration of a Routing Node
      • Quick Tor Setup
      • Configuring Tor
      • Enable ‘Neutrino mode’ in Bitcoin Core
      • Send Messages With Keysend
      • Partially Signed Bitcoin Transactions
      • Bulk onchain actions with PSBTs
      • Sweeper
      • Debugging LND
      • Fuzzing LND
      • LND API documentation
      • Channel Acceptor
      • RPC Middleware Interceptor
      • HTLC Interceptor
      • NAT Traversal
      • Recovery: Planning for Failure
      • Migrating LND
      • Disaster recovery
      • Contribute to LND
    • Lightning Terminal
      • What is Lightning Terminal?
      • 🛠️Get litd
      • Run litd
      • Integrating litd
      • Demo: Litd Speed Run
      • Connect to Terminal
      • Recommended Channels
      • Rankings
      • Health Checks
      • Liquidity Report
      • Opening Lightning Network Channels
      • Managing Channel Liquidity
      • Autofees
      • AutoOpen
      • LND Accounts
      • Loop and Lightning Terminal
      • Loop Fees
      • Pool and Lightning Terminal
      • Command Line Interface
      • Troubleshooting
      • Lightning Node Connect: Under the hood
      • LNC Node Package
      • LITD API Documentation
      • Privacy and Security
      • Privacy Policy
      • Terms of Use
    • Loop
      • 🛠️Get Started
      • The Loop CLI
      • Autoloop
      • Static Loop In Addresses
      • Instant Loop Outs
      • Peer with Loop
      • Loop API Documentation
    • Pool
      • Overview
      • Quickstart
      • 🛠️Installation
      • First Steps
      • Accounts
      • Orders and Asks
      • Sidecar Channels
      • Zero-confirmation Channels
      • Channel Leases
      • Batch Execution
      • Account Recovery
      • Pool API Documentation
      • FAQs
    • Taproot Assets
      • Get Started
      • First Steps
      • Taproot Assets Channels
      • Asset Decimal Display
      • Become an Edge Node
      • RFQ
      • Collectibles
      • Universes
      • Asset Loop
      • Debugging Tapd
      • Multisignature
      • Minting Assets With an External Signer
      • Lightning Polar
      • Operational Safety Guidelines
      • Taproot Assets API Documentation
    • Aperture
      • ⚒️Get Aperture
      • LNC Backend
      • LNC Mailbox
      • Pricing
    • Faraday
      • 🛠️Get Started
      • The Faraday CLI
      • Faraday API Documentation
  • LAPPs
    • Guides
      • Use Polar to Build Your First LAPP
        • Setup: Local Cluster with Polar
        • Setup: Run the Completed App
        • Setup: Run the App Without LND
      • Add Features
        • Feature 1: Connect to LND
        • Feature 2: Display Node Alias and Balance
        • Feature 3: Sign and Verify Posts
        • Feature 4: Modify Upvote Action
      • Make Your own LNC-powered Application
    • Next Steps
  • Community Resources
    • Resource List
    • Lightning Bulb 💡
    • Glossary
    • FAQ
Powered by GitBook
On this page
  • Atomic Multi-path Payments (AMP)
  • Hash Time-lock Contract (HTLC)
  • Keysend
  • Lightning address
  • Lightning invoice
  • LNURL
  • Multi-path Payments (MPP)
  • Payment route
  • Static invoices

Was this helpful?

  1. The Lightning Network
  2. Making Payments

Payment Etymology

Learn the essentials of payments in the Lightning Network.

PreviousHashed Timelock Contract (HTLC)NextWhat Makes a Good Routing Node

Last updated 2 years ago

Was this helpful?

The Lightning Network is primarily a payment network. Peers connect with each other and establish to transfer bitcoin between each other, either as recipients, senders or routers.

Cryptography ensures that payments are made atomically, meaning they either fail completely or succeed, without a third party taking custody of the payment.

Atomic Multi-path Payments (AMP)

Atomic Multi-path payments is an implementation of multi-path payments, which allows for a single payment to be routed in shards along different routes. AMP ensures that each payment shard cannot be claimed individually by the recipient, but rather only the whole payment (all of the shards combined) can be claimed. Additionally, AMP implements keysend, which allows sending funds solely by specifying a recipient's public key, without a Lightning invoice. AMP also allows the creation of static invoices, which can safely be paid multiple times.

Hash Time-lock Contract (HTLC)

A Hash Time-lock Contract (also sometimes Hashed Time-lock Contract) is central to the mechanism of a Lightning payment. A HTLC is a bitcoin transaction that can either be redeemed by producing a secret preimage represented by a hash or by waiting for a predefined period of time. Lightning payments are made to this hash of the preimage, which has to be revealed by the recipient to claim the payment. If the payee does not reveal the preimage, the payment can be claimed back by the sender after a timeout period. When sending a payment along a payment route, each hop will make a payment to the same preimage, ensuring that the payment can either be claimed in its entirety or fail.

Keysend

Keysend is the mechanism to make a Lightning payment knowing only the recipient’s public key. This enables streaming payments, donations and removes the requirement of prior interaction between payee and payer. Keysend is also the name of an implementation of this idea, today the concept of keysend is implemented as part of AMP.

Lightning address

A Lightning address is a standard to look up LNURL pay requests on a http server. This allows us to associate email addresses with LNURL pay requests and make Lightning payments to usernames.

Lightning invoice

A Lightning invoice is a bech32 encoded string containing all vital information to make a Lightning payment, such as the amount, recipient, features and payment hints in the case of a private node.

LNURL

A Lightning Network URL is a bech32 encoded url, through which a Lightning wallet can interact with a server in an automated way. LNURLs can be an alternative to static invoices, allow for the withdrawal or redemption of funds, open channels or even authenticate users.

Multi-path Payments (MPP)

Payment route

A payment route is the path a payment takes from the payer to the payee. Unless there exists a direct channel with sufficient capacity between the two, payments need to be routed through the network. This can be done along multiple routing nodes with the use of HTLCs. A single payment can not only be routed through multiple channels in serial, but also in parallel, using AMP.

Static invoices

A static invoice is an invoice that does not expire and can be safely paid multiple times. AMP allows for the creation of static invoices, as do other proposals.

Also read:

Multi-path payments is the idea to route a payment along multiple routes to its destination. This can make it easier to route larger payments, but also help with costs and privacy. MPP is also the name of an implementation of this idea, today superseded by .

Also read:

payment channels
Also read: The guide to AMP
Watch: Get AMPed: Making Atomic Multi-Path Payments
Understanding Lightning invoices
AMP
Payment lifecycle