Home < Bitcoin++ < Lightning Specification < Bitcoin Review Podcast < Bitcoin Core Dev Tech < Stephan Livera Podcast < Advancing Bitcoin < Bitcoin Magazine < Bitcointranscripts < TABConf < London Bitcoin Devs < Misc < MIT Bitcoin Expo < Greg Maxwell < Chaincode Labs < Sydney Bitcoin Meetup < Bitcoinology < c-lightning < Adopting Bitcoin < IACR Crypto < Wasabi Research Club < Lightning Hack Day < Blockstream Webinars < Munich Meetup < TFTC Podcast < Realworldcrypto < SF Bitcoin Meetup < CPPcon < Bitcoin Design < Chicago Bitdevs < VR Bitcoin < LA Bitdevs < Ruben Somsen < Honey Badger Diaries < Andreas Antonopoulos < Austin Bitcoin Developers < Stanford Blockchain < Coordination of Decentralized Finance < Lightning Conference < Cryptoeconomic Systems < Bitcoinops < Baltic Honeybadger < Scaling Bitcoin Conference < Bitcoin Edge Dev++ < Decentralized Financial Architecture Workshop < Dallas Bitcoin Symposium < Breaking Bitcoin < Lets Talk Bitcoin Podcast < What Bitcoin Did Podcast < Magicalcryptoconference < Noded Podcast < Boltathon < Grincon < Verifiable Delay Functions < Building On Bitcoin < Layer2 Summit < Satoshi Roundtable < Blockchain Protocol Analysis Security Eng < Developers-Miners Meeting < W3 Blockchain Workshop < Simons Institute < Bit Block Boom < Coindesk Consensus < Rebooting Web Of Trust < Texas Bitcoin Conference < Lightning Network

Lightning Network

Speakers: Tadge Dryja

Date: June 30, 2016

Transcript By: Bryan Bishop

Tags: Lightning

Category: Workshop

I am going to talk about blockchain scalability using payment channel networks. I am working on Lightning Network. It’s currently being built in bitcoin but it can support other things. One of the fundamental problems with blockchain is scalability. How can you have millions of users and rapid transactions?

Fundamentally, the blockchain is shared. You can call it a DLT but it’s really a copied ledger. Every user has a copy. When you’re at a conference and everyone is using the same wifi AP, it’s pretty slow. You really want a segmented network where everyone is plugged into their own switch.

Global consensus is important but inefficient. HOw do you segment the network without losing the properties of the blockchain? Well, the way to do it is with payment channels. It’s not quite a cryptographic primitive yet, but I think in the future people will consider it a crypto primitive.

The way that it works is that in the case of bitcoin, you send it to a shared multisig address. Then you share signatures that lay claim to those coins. You keep sending messages back and forth offline. That alone is complex, I don’t have time to go into how that works. This allows you to establish channels where you send one output to the channel, then you can move money back and forth. For payments, you can’t have just one person, you need to be able to pay multiple people.

How do you explain this to multiple people? Cryptographically, Alice has a channel with Bob who has a channel with Carol who has a channel with Dave. Alice wants to use the existing channel rather than creating a new channel when she wants to pay Dave, because to do otherwise would cost money. Dave makes a random number R. Payments contingent on knowledge of the preimage of the hash. So you make a cascading chain of these obligations. As long as there’s a path, payments can be routed.

If you would like to learn more about this, then please ask me more after the talk.