Quote from: erre on August 25, 2017, 08:38:53 PM

Quote from: 1Referee on August 25, 2017, 08:36:05 PM

Quote from: erre on August 25, 2017, 02:27:30 PM

I will search for reference, but I understood that now we are still in a test case, and segwit benefits will become fully operational only after 2 more weeks after activation.

Everything is mostly being tested on the testnet chain, but the point is that if we are going to make use of Segwit, we have to move our funds away from the current non Segwit addresses (i.e send funds to Segwit address, where after that we can start ulitizing the Segwit update). If people aren't moving their funds, and just remain using Bitcoin as how they have always been using it, nothing will change, and thus they will continue to transact in the old fashion (i.e pre Segwit activation time) way. Look at Litecoin for example - a whole lot of transactions that are being sent are till this day still non Segwit transactions.

Thank you for this explanation. So the segwit public key is different? I thought it was just a matter of how the wallet craft the tx...

Yes, a Segwit-compatible wallet must support P2SH (BIP16) and its address format (BIP13). To receive payments, the wallet must be able to create a P2SH address based on a P2WPKH script (and be able to recognize payment to such addresses).

So, Segwit addresses have a prefix 3, like other P2SH addresses. (As opposed to the the standard prefix of 1)