3 ms·

No. Except for Lightning Network, which is this software that somehow routes transactions on a separate network, and it's not bitcoin; it doesn't have the same

No. Except for Lightning Network, which is this software that somehow routes transactions on a separate network, and it's not bitcoin; it doesn't have the same assurances, there are some third-party channels that route the transactions. (I admit, I haven't studied LN in detail.) It uses bitcoin as a "backbone", sort of like you have SWIFT which is slow and expensive, and then you have credit card payments/paypal/whatnot that is built on top of it. LN specifically requires segwit (the main issue of this "civil war").

kanzure 9y ago
> and it's not bitcoin; it doesn't have the same assurances, there are some third-party channels that route the transactions. (I admit, I haven't studied LN in detail.) lightning clients pass around bitcoin transactions to each other, check the protobufs: https://github.com/ElementsProject/lightning/blob/2bf92c906326d299e42317cc15727edf845b16ca/lightning.proto https://github.com/ElementsProject/lightning/blob/2bf92c9063... admittedly the protobufs have changed since i last looked, here's the canonical diagram describing the hashed timelock bitcoin transaction concept: https://github.com/ElementsProject/lightning/blob/2bf92c906326d299e42317cc15727edf845b16ca/doc/htlc.svg https://github.com/ElementsProject/lightning/blob/2bf92c9063... or read the paper https://lightning.network/lightning-network-paper.pdf https://lightning.network/lightning-network-paper.pdf > LN specifically requires segwit false, see http://diyhpl.us/wiki/transcripts/scalingbitcoin/hong-kong/overview-of-bips-necessary-for-lightning/ http://diyhpl.us/wiki/transcripts/scalingbitcoin/hong-kong/o...
- shp0ngle 9y ago
  Thanks for the links. I was under the impression that LN needs maleability fix. (And I am not the only one who thinks that - see https://www.cryptocoinsnews.com/segwit-lightning/ https://www.cryptocoinsnews.com/segwit-lightning/ ) I don't take FlexTrans as serious attempt at malleability fixing

kanzure 9y ago

> and it's not bitcoin; it doesn't have the same assurances, there are some third-party channels that route the transactions. (I admit, I haven't studied LN in detail.) lightning clients pass around bitcoin transactions to each other, check the protobufs: https://github.com/ElementsProject/lightning/blob/2bf92c906326d299e42317cc15727edf845b16ca/lightning.proto https://github.com/ElementsProject/lightning/blob/2bf92c9063... admittedly the protobufs have changed since i last looked, here's the canonical diagram describing the hashed timelock bitcoin transaction concept: https://github.com/ElementsProject/lightning/blob/2bf92c906326d299e42317cc15727edf845b16ca/doc/htlc.svg https://github.com/ElementsProject/lightning/blob/2bf92c9063... or read the paper https://lightning.network/lightning-network-paper.pdf https://lightning.network/lightning-network-paper.pdf > LN specifically requires segwit false, see http://diyhpl.us/wiki/transcripts/scalingbitcoin/hong-kong/overview-of-bips-necessary-for-lightning/ http://diyhpl.us/wiki/transcripts/scalingbitcoin/hong-kong/o...

shp0ngle 9y ago
Thanks for the links. I was under the impression that LN needs maleability fix. (And I am not the only one who thinks that - see https://www.cryptocoinsnews.com/segwit-lightning/ https://www.cryptocoinsnews.com/segwit-lightning/ ) I don't take FlexTrans as serious attempt at malleability fixing