4 ms·

Segregated witness should activate in litecoin in about ~6 days. http://litecoinblockhalf.com/segwit.php http://litecoinblockhalf.com/segwit.php

andy_ppp 9y ago
What is this?
- TD-Linux 9y ago
  It's a feature originally developed for Bitcoin: https://bitcoincore.org/en/2016/01/26/segwit-benefits/ https://bitcoincore.org/en/2016/01/26/segwit-benefits/ Litecoin is based on Bitcoin Core's codebase and therefore inherited it as well. Due to various reasons it's activating on Litecoin before Bitcoin.
- proto-n 9y ago
  A somewhat controversial protocol upgrade developed for bitcoin. On the bitcoin network it has not reached the necessary support yet. Most bitcoiners view its activation on litecoin as a large scale beta test.
  - cashmonkey85 9y ago
    This is really not the case. It's been pair reviewed and testing for 2 years. Plus has been run on testnet since last year. It's technically superior and should be activated on bitcoin but it's been blocked for political reasons
    - proto-n 9y ago
      You are reacting to something my comment doesn't say: that somehow segwit is not good enough. I only said it was somewhat controversial (which it is, for whatever reasons, didn't say it was technical) and that bitcoiners view it as a beta test, which is/was a widely accepted sentiment on both /r/Bitcoin and /r/btc. I didn't even say it needed one. I said the latter more to illustrate the relationship between segwit+bitcoin and segwit+litecoin than segwit itself.
- runeks 9y ago
  It's a protocol change that moves signature scripts out of the transaction itself, such that they are not included when calculating the hash/transaction ID of a transaction (a signature script contains both a signature plus additional data needed to fulfill a particular output script; only the additional data can the modified while keeping the signature valid). This is important because the signature script itself is unsigned data (a signature can't sign itself), which means that it's possible to change the signature script of a transaction, thus changing the transaction ID, and invalidating all transactions that pointed to the original transaction. This is colloquially referred to as "transaction malleability".

andy_ppp 9y ago

What is this?

TD-Linux 9y ago
It's a feature originally developed for Bitcoin: https://bitcoincore.org/en/2016/01/26/segwit-benefits/ https://bitcoincore.org/en/2016/01/26/segwit-benefits/ Litecoin is based on Bitcoin Core's codebase and therefore inherited it as well. Due to various reasons it's activating on Litecoin before Bitcoin.
proto-n 9y ago
A somewhat controversial protocol upgrade developed for bitcoin. On the bitcoin network it has not reached the necessary support yet. Most bitcoiners view its activation on litecoin as a large scale beta test.
- cashmonkey85 9y ago
  This is really not the case. It's been pair reviewed and testing for 2 years. Plus has been run on testnet since last year. It's technically superior and should be activated on bitcoin but it's been blocked for political reasons
  - proto-n 9y ago
    You are reacting to something my comment doesn't say: that somehow segwit is not good enough. I only said it was somewhat controversial (which it is, for whatever reasons, didn't say it was technical) and that bitcoiners view it as a beta test, which is/was a widely accepted sentiment on both /r/Bitcoin and /r/btc. I didn't even say it needed one. I said the latter more to illustrate the relationship between segwit+bitcoin and segwit+litecoin than segwit itself.
runeks 9y ago
It's a protocol change that moves signature scripts out of the transaction itself, such that they are not included when calculating the hash/transaction ID of a transaction (a signature script contains both a signature plus additional data needed to fulfill a particular output script; only the additional data can the modified while keeping the signature valid). This is important because the signature script itself is unsigned data (a signature can't sign itself), which means that it's possible to change the signature script of a transaction, thus changing the transaction ID, and invalidating all transactions that pointed to the original transaction. This is colloquially referred to as "transaction malleability".