Chaincode Seminars
  • Seminar for Bitcoin and Lightning protocol
  • Bitcoin Protocol Development
    • Welcome to the Bitcoin Protocol Development Seminar
    • SegWit
    • Mining and Network Block Propagation
    • P2P
    • Scripts and Wallets
  • Lightning Protocol Development
    • Payment Channels, Intro to Lightning, and HTLCs
    • How the layers of Lightning Fit Together
    • Lightning Routing
    • Lightning Limitations
    • The Future of Lightning
Powered by GitBook
On this page
  • Reading
  • Discussion Questions
  • Major Limitations of Lightning
  • What Are Anchor Outputs?
  • Spamming the Lightning Network
  • Limitations of lightweight clients
  • Fee Management
  • Incentive problems in the network
  • Routing Failures
  • Lightning Attack Vectors
  • Pinning Attacks
  • On the Difficulty of Hiding the Balance of Lightning Network Channels
Edit on GitHub
  1. Lightning Protocol Development

Lightning Limitations

Reading

Content
Time (min)

60

30

45

30

25

40

25

30

45

30

15

40

50

20

25

30

Discussion Questions

  1. What are the incentives around on-chain fees for the funding tx? Does the fundee care if the funder submits a funding tx with very low fee?

Major Limitations of Lightning

  1. What is the danger of being able to associate a base layer bitcoin node with the owner’s lightning node?

  2. What problem do anchor outputs resolve? Why don't they solve the pinning problem?

What Are Anchor Outputs?

  1. Can including fees in channel transactions be abused by attackers? How do anchors seek to fix this?

Spamming the Lightning Network

  1. What variables other than htlc_minimum_msat and max_accepted_htlcs could be tweaked to make it harder or less attractive for an attacker to try and lock up a channel?

  2. Can we differentiate between the useful messages like error and trial path finding versus spam like probes?

Limitations of lightweight clients

  1. As a service, why is it easier to send funds than receive them?

Fee Management

  1. Why would the fundee care about the size the fees if it’s a funder that’s paying the fees?

  2. If you disagree about the fees with your peer, how do you negotiate them?

Incentive problems in the network

  1. What kind of info would be relevant for doing local reputation tracking?

  2. How would having bidirectional fees for payments affect overall routing incentives?

Routing Failures

  1. What challenges exist for making routing table synchronization efficient?

Lightning Attack Vectors

  1. What's to prevent an attacker from temporarily drying up network liquidity by sending himself payments using really long routes without completing the payments?

Pinning Attacks

  1. If a channel is being closed unilaterally, and the commitment tx has a low fee, can one of the parties bump the fees with CPFP (spend their output with a high fee)? If not, why not?

On the Difficulty of Hiding the Balance of Lightning Network Channels

  1. What are the effects of upfront fees for HTLC on malicious probing and "honest" probing?

  2. Is randomly denying a percentage of payment requests an effective countermeasure to the balance probing attack? Outside of the potential loss of routing fees, are there any other downsides?

  3. Another countermeasure was to remove error messages when a route fails. Besides having less clarity as to why a path failed when trying to find a route for a payment, are there any other reasons to include these error messages?

PreviousLightning RoutingNextThe Future of Lightning

Last updated 2 months ago

(starting at Lightning Problem 1: Liquidity)

(optional)

Lightning is broken
Lightning Network 2.0
Lightning Limitations
The price of anarchy
What Are Anchor Outputs?
Spamming the Lightning Network
Limitations of lightweight clients
Fee Management
Incentive problems in the network
Routing Failures
Griefing attacks
Lightning Attack Vectors
Pinning Attacks
Solutions to inbound capacity problem in Lightning Network
Unjamming Lightning
Jamming Book