[nullc]

> CompatBlocks is just one of the developments that BCH has completed and released

wtf. man, stop taking credit for other people's work. Compact blocks were completed and released by Matt Corallo, myself, and the other Bitcoin developers at the time long before BCH existed. It had absolutely no involvement from any BCH developer.

> many doubt that his company is supporting Bitcoin vs handicapping it

When your link in the earlier post is an article ranting about how much money blockstream employees are making because it pays its employees partially denominated in Bitcoin and Bitcoin has increased a lot in value.

> Gavin did not endorse CSW as Satoshi himself

In fact Gavin stated that he was convinced Wright was Satoshi long before he ever met him or witnessed any signing.

> folks like Adam [...] to gain control of the core client.

Adam doesn't have any control over Bitcoin Core and never has. I don't think anything he's ever proposed has ended up in in it, in fact.

> Cash handles this by making sure to have multiple implementations

Actually, BCH's constant hardforks have killed many of those multiple implementations. "Bitcoin XT", "Bitcoin Classic", "Bcoin" to name some of those. Ironically the old BitcoinXT from back when it was Bitcoin software ... happily still works on Bitcoin. So you have it backwards: it's bitcoin that preserves people's freedom to use different implementations.

[phillipsjk]

Compact block were heavily inspired by Bitcoin Unlimited's "Thin Blocks".

[nullc]

It is another untruthful claim.

The original design document for compact blocks is was published (and last modified) on Dec 25, 2015. https://people.xiph.org/~greg/efficient.block.xfer.txt

The earliest work for Bitcoin Unlimited's "Thin Blocks" was on Jan 10th 2016: https://bitco.in/forum/threads/buip010-passed-xtreme-thinblo...

Both were motivated by an earlier effort by Bitcoin developers Matt Corallo and Pieter Wuille, https://buildingbitcoin.org/bitcoin-dev/log-2013-12-27.html#... (which Pieter had implemented, but was found to not work so well, https://buildingbitcoin.org/bitcoin-dev/log-2013-12-28.html#...).

The fact that in Bitcoin we took the time to fully think through, write a clear and complete specification https://github.com/bitcoin/bips/blob/master/bip-0152.mediawi... , and thoroughly test and review the implementation before deploying it while BU has been occasionally abused by the BU organization and their supporters to dishonestly claim that compact blocks came later (or were somehow derived) from their work.

Users on the sidelines were easily deceived by this marketing because BU rushed their implementation into production while Bitcoin took a more deliberative process.

BU's "thinblocks" implementation was, in fact, severely flawed both due to an implementation vulnerability that resulted in almost every BU node on the network being crashed near simultaniously, and due to a design error introduced because BU's "chief scientist" strongly believed that it was computationally intractable to produce a collision in the first 64-bit of transaction IDs (a sha2 hash), even though one can be computed on a fast desktop computer in seconds.

In fact, Bitcoin Cash developers went so far as to attempt to block the deployment of compact blocks by falsely claiming that it would somehow "disrupt the network": https://www.reddit.com/r/btc/comments/4xkqbk/core_intends_to... (It didn't.)

So the history is that: Bitcoin developers proposed and tested an idea for faster block propagation using filters and found it lacking. Later, it came up again as a possible way to mitigate segwit's bandwidth increase, so I wrote a design to address the known issues and we started working on implementing it. A few weeks later BU developers picked up the old work and started improving it. Within a couple months they had it deployed it in public and announced 'mission accomplished', but their deployment was unspecified and ultimately faulty. As a result of those issues and the superior relay latency of compact blocks thinblocks was replaced in the Bitcoin Cash network with the protocol from Bitcoin.

There is no common protocol feature in BU's xthinblocks that wasn't also in Bitcoin's original work that inspired both efforts. There could have been no influence on compact blocks' design by xthinblocks because it would have been physically impossible for there to be due to causality. That hasn't seemed to stop BU developers and people like you from repeating this lie.

Cheers.

[phillipsjk]

I guess I stand corrected on that one.