litecoin VS bitcoin-abc

Open Source Litecoin is fully decentralized in the fact any one person could submit code into the network and as long as a majority of miners agree to that fork it will be implimented. This is similar to bitcoin.

Progress continues with the integration of Litecoin code changes into the v24 Bitcoin codebase. The month of May saw a major milestone with the resolution of all remaining functional tests for the pre-MWEB merge task. The code has been submitted for review here.

git clone https://github.com/litecoin-project/litecoin.git

"If upgrading to 0.21.2 after MWEB has activated, you must resync to download MWEB blocks." https://github.com/litecoin-project/litecoin/releases

I tried following this tutorial: https://github.com/litecoin-project/litecoin/blob/master/doc/build-osx.md

However, this serialization format seems to contradict with BIP 0144, which states: "if the witness is empty, the old serialization format must be used." also contradict the comments in the litecoin source code at https://github.com/litecoin-project/litecoin/blob/master/src/primitives/transaction.h

In order to add MWEB support to PSBTs, I first had to merge in PSBTv2 (BIP-0370), which can be seen here. I then defined the MWEB fields we needed to add, and added them to the PSBT data structures along with serialization and deserialization here.

A pull request has also been submitted for downloading and verifying HogEx transactions, MWEB headers, and the UTXO leafset bitmap. This covers steps 2 and 3 of the light client sync process.

I found a definition of MAX_STANDARD_TX_SIZE here.

If you have old miners or just like to mine into cold storage wallets .If you don't have a core wallet then download it on the official repository https://github.com/Bitcoin-ABC/bitcoin-abc/releases or electrum wallet https://github.com/Bitcoin-ABC/ElectrumABC

You mean when a BCH developer discovered a bug in BCH while testing the CTOR consensus change which redid all the double spend detection but somehow left this bug in place, and mistakenly believed it only caused a crash and reported to Bitcoin Core.

Here's a link: https://github.com/Bitcoin-ABC/bitcoin-abc/commit/d1d091ba73f574ae5eb189fe7655c67bf5d338cf

https://github.com/Bitcoin-ABC/bitcoin-abc/issues/35#issuecomment-337921237

Do you mean the default value of the -minrelaytxfee command-line option? That's "hard-coded" in exactly the same way that the BCH blocksize generation limit has been "hard-coded" to 2 MB since 2017 in Bitcoin ABC. But it turns out that miners don't always use the default values for command-line options that matter to them.

But in bch, the software keeps to be improved and is hosted on Github: https://github.com/Bitcoin-ABC/bitcoin-abc these pullrequests get approved, but at some point, somebody, a breathing person! Must select the pulrequests and merge them into a new version, that gets flagged as verson xx.xx.xx . Who in bch does that. This is indeed a centralised action ( this tis the same as in btc)