I've build a tool to detect differences between _my local_ mempool and what miners include in their block (there will always be slight differences). This is primarily intended to detect censorship, but can also detect transactions that never entered _my_ mempool.
Brilliant! I remember thinking about this problem a few years back: what stops miners of a blockchain just ignoring transactions/anything from certain entities. So it's good that there exists a way to track such behaviour, if it is occurring.
Economics. If miners consistently ignore certain transactions, there is space for new miners to enter the market and earn super-normal profit. After the next difficulty adjustment cycle, the old, censoring miners may be priced out.
Yes! Will be on umbrel eventually. Currently needs a Bitcoin Core build from the master branch. The features use should be in the upcoming release. Then Umbrel!
Miners can't change Bitcoin without the consent of full nodes, who run the core client. That's why SegWit2x didn't happen three years ago. All the miners supported it, because bigger blocks means bigger transaction fees. Full nodes and core devs didn't support it, because big blocks means you won't be able to run Bitcoin on PCs much longer and therefore centralized online service providers will control it.
FWIW bigger blocks actually mean much much smaller transaction fees, both in theory and practice. Though it's true some miners erroneously believed arguments otherwise.
BCash, for example, some loopy "large block" clone of Bitcoin has only rarely had more than $1 in fees in blocks-- and not primarily because it has fewer transactions (though it does), but because there is no cause to pay more than negligible amounts when both capacity isn't scarce and mining isn't completely centralized.
The result is that the BitcoinUnlimited (one of the BCash clients) "chief scientist" proposes that security must be paid for by perpetual inflation... and they've been moving towards abandoning Bitcoin's decentralized consensus-- e.g. bcash clients will no longer reorg so if there is a split deeper than a few blocks (caused by a network partition or a block race), their nodes will just split off into separate networks. Quite a mess.
>>FWIW bigger blocks actually mean much much smaller transaction fees, both in theory and practice.
Ethereum has larger transaction fees than Bitcoin right now, on a larger volume of transactions, so in practice, that is not true.
The addressable market will necessarily shrink with too small blocks.
Now of course when Bitcoin Cash launches, with most of the world unaware of it, it's not going to get as much as adoption, and by extension transaction fees, as Bitcoin, irrespective of its block size limit, so your comparison is inappropriate.
Ethereum has a what is effectively a block size limit, which is limiting usage to pretty similarly to Bitcoin's and it is operating hard against it. ('volume' of transactions is not particularly comparable because the average bitcoin transaction now makes multiple payments in a single txn).
Back in the past the issuer of Ethereum stated publicly that online money should not cost more than 5cts/txn... and yet here we are with $50 transactions there.
BCash has not only fewer transaction in spite of tens of millions spent promoting it, but it has vastly lower fees per transaction. If its blocks were half full at 10x the current feerate (and many times larger than bitcoin blocks), its fee income would still be a tiny fraction of Bitcoin's-- and nowhere near enough to support even the extremely low level of security it currently has.
That is simply not true. You can even look to the public markets, there were futures on each of these fork attempts and they traded at a tiny fraction of the price of Bitcoin.
The "stepping back", as mentioned in the title, doesn't summarize what's happening here. laanwj decided to delegate some of his lead maintainer tasks to others with aim to further improve the decentralization and reducing the attack surface. He want to continue to work on Bitcoin an Bitcoin Core.
Most recently, this became relevant as the bitcoincore.org website he (co-)maintains received a legal letter from a (fraudulent; as in unproven and repeatedly lying) entity claiming copyright of the 2008 Bitcoin whitepaper. He complied[0] by taking the PDF down from bitcoincore.org and received a lot of slack for it by parts of the community. He then made clear that he'll happily continue to work on Bitcoin Core and Bitcoin in general, but will not be a "martyr"[1] for the project: "it's up to you as bitcoiners to protect it". As a reaction a lot of community members and companies proceeded to host the PDF on their site [2].
See https://miningpool.observer