pull down to refresh
Keep in mind... that BRC20s don't exist. It's like the tooth fairy. It's a made up thing from a few random lines of code that gets 'indexed' somewhere so... people can 'pretend' that tokens don't exist.
It's impossible to 100% stop these meta-protocols.
reply
Denial isn't a good strategy, imho.
reply
The core dev team is too centralized
Paychecks from same company
Work in same office
We need knots and a third major client implementation too
There seems to be a bit of a disconnect between the cheering around technical achievements and the economic reality that surrounds it, yes.
But if I look at both the comments and the article, then there's also a disconnect there: if you want quick block reconstruction by already knowing all the txs in the block beforehand, then it is useful to know... all the txs that are mined in the block, beforehand.
This is why not tracking transactions that you could know of is self-defeating. Whereas not mining transactions you consider undesired, is only unwise from a profit-maximalist perspective.
Technically, you can create any rules you desire for inclusion in your block templates without unnecessarily limiting your mempool's contents. All it takes is taking a step back and realize that you can be spam hating and censorship hating at the same time. This is the challenge to all that seem to be polarizing themselves over something as retarded as BRC-20.