3 ms·
I don't know Bitcoin well enough to understand the LN paper, but I've read articles on the basic ideas and think I understand enough to implement LN on Ethereum
by DennisP 10y ago
I don't know Bitcoin well enough to understand the LN paper, but I've read articles on the basic ideas and think I understand enough to implement LN on Ethereum, where it's much easier.
If channels were not networked together, then they'd only be good for recurring payments.
But there's a trick that lets you network them, so A can have recurring payments to B, and B can have recurring payments to C, D, and E, and now A can pay all the others via his one channel to B. And it's done in a way that prevents B from being able to run away with money intended for C,D,E.
- RustyRussell 10y ago> LN on Ethereum, where it's much easier. Genuine question? What makes it easier? Thanks!
- zmanian 10y agoBitcoin script provides a no elegant way to invalidate old states. There are various solutions to this in lightning network tx but they end up requiring actively watching the network in case an old state is broadcast. If you have a better mechanism for invalidate the previous state, the whole system can be massively simplified.
- RustyRussell 10y agoYou mean, every transaction causes an on-chain ethereum change? That seems to miss the point?
- DennisP 10y agoMainly, having account balances and arbitrary data storage, instead of bitcoin's unspent transaction outputs. See this article by Ethereum's inventor: https://medium.com/@ConsenSys/thoughts-on-utxo-by-vitalik-buterin-2bb782c67e53#.fst8lrv1d https://medium.com/@ConsenSys/thoughts-on-utxo-by-vitalik-bu... Also, having a convenient scripting language instead of dealing directly with opcodes, like you have to do on Bitcoin.
- RustyRussell 10y agoSince we're only talking about a single utxo in either case, the difference seems moot. And writing and testing the opcodes took less than a day; that's not the hard part! (Though getting the convenient opcodes into bitcoin was definitely non-trivial!)