Looks like this article is missing segwit transactions, be it with the "3" format or with the bech32 (bc1) format.
Expanding on what you say: The network itself has no notion of addresses; addresses are only a human interface feature. Transactions involving Segwit addresses starting with a “3” are P2WPKH-nested-in-P2SH (Pay To Witness Public Key Hash nested in Pay To Script Hash), paid to the hash of a script consisting of OP_0 followed by the push of a witness keyhash (0x0014<20-byte hash>). Bech32 addresses permit use of native Segwit tranactions, but are not backward-compatible. An address starting with a “3” may or may not be a Segwit address; there is no way to tell, just by looking at it; it’s simply an ordinary P2SH address, which is why old clients can send money to it.
(I know that
you know this; I’m filling in for others. Good call in your reply.)
I just don't get this about Segwit because the project got canceled but now it's back on again
as Segwitx2 because they are doing a fork on 28th Dec 2017
Did the Segwit team turn it on without a fork so it just worked with BTC or something or are we
talking about a message that miners can send if they want vote for it or something
Thanks in advance
Segwit is an excellent technology which activated in Bitcoin on 2017-08-24 with Block #481824.
Bitcoin already has Segwit. The misleadingly misnamed “Segwit2X” is not Segwit and not Bitcoin.
Yes,but the project was said to be suspended actually not cancelled. However the B2X is available on some exchange and you can also find it on coinmarketcap cause the B2X project was phase into two project which is the SegWit activation and 2MB blocksize increase. Therefore, 2MB blocksize increase was the one suspended not the SegWit activation which occurs in August.
SegWit Mail List Site for more informationThe link you give is not to the Segwit mailing list. It’s to the mailing list of a hostile takeover attempt which has nothing to do with Segwit, and nothing to do with Bitcoin.
Bitcoin no longer has a block size limit. Segwit replaces the block size limit with a
block weight limit, set to 4000000 bytes:
/** The maximum allowed weight for a block, see BIP 141 (network rule) */
static const unsigned int MAX_BLOCK_WEIGHT = 4000000;