Lightning and other layers
Objective
Understand channel-based payments and recognize features outside the reviewed Cuvex workflow.
Understanding the topic
Lightning uses channels and updates to make payments without recording every exchange individually on the base chain. Opening and closing channels and some recovery scenarios may require on-chain transactions. Availability, inbound and outbound liquidity, and monitoring depend on wallet design and the services used.
An invoice may include an amount, description and expiry. Depending on context, amounts may be in satoshis or millisatoshis. Millisatoshis do not imply sub-satoshi outputs on the base chain. Paying an invoice requires compatible support and an available route. A QR code does not guarantee payment through any application.
Custodial and noncustodial services have very different models. Typical speed does not prove the absence of risks. Do not present Lightning as completely anonymous. Observers, routes, counterparties and metadata remain relevant.
Cuvex chat can coordinate requests for sats paid on-chain through a WOW account. This edition does not attribute a Lightning node, channel management or Lightning invoice signing to Desk. If a request includes several payment methods, verify which you understand and which your application will execute.
Practice
- Classify training examples of an on-chain address, a bitcoin: URI and a Lightning invoice.
- Compare on-chain and channel payments in terms of confirmation, liquidity, custody and recovery.
- Explain why an expired invoice should be checked with the recipient instead of being reinterpreted as an address.
Show what you know
Decline an incompatible payment method without exposing keys or incorrectly attributing a failure to Cuvex.
Common question
Are all payments in sats Lightning payments? No. Satoshis express value. The method depends on the protocol used.
Pause point
Record the exercise’s payment method without saving real invoices.
Reading, self-assessment and physical practice are different. This result is not a certificate.