Breaking: this sign seen outside the homes of multiple Core devs
Login to reply
Replies (41)
I just love it 😂😂🤣
Looks like rainbow indoctrination flag colors?
getting rid of valid transactions from one's mempool doesn't solve any problem, unless the usage of the alternative is the majority, so filters DO NOT work
Note: this is satire, I do not think any Core dev holds all of these opinions
> [a filter] doesn't solve any problem
Surely it solves the problem of "how do I purge my mempool of spam transactions?"
sure, but it doesn't get rid of those transactions on the network
it's a reference to this yard sign, which is popular in the USA: 
In This House, We Believe Yard Sign | Free Shipping | VPN
In This House, We Believe yard sign printed on durable corrugated plastic with UV-resistant inks. Stakes included. Made in the USA. Free shipping. ...
Like in email. Your mail server probably doesn't accept mails with an attachment of 1 Terrabyte.
Although the network and protocolls(tcp/ip, mail) support them.
There may be mailservers accepting any sized mail and even forward them, but why should you accept these obvious spam/ddos-mails?
There are other, better protocolls for big files, sane persons use ftp or torrent for things like that.
Same with the btc network.
you misunderstand something critical, you STILL get those transactions.
"the network" is just "other people's computers." I don't care what they want to store in their mempools. I don't want to store spam in mine. *That* is the problem Knots solves.
you get them if/when a miner mines them
but (1) you *didn't* propagate them to miners (2) you *did* reduce that miner's block propagation speed
those are two benefits you lose by opting for Bitcoin Core's mempool software
Ooooooh shyyyyyt!!!!
I can put one similar as well but it will state:
all lives matter
protect human rights (men and women are humans)
no human is illegal on planet Earth (but different countries have different citizens and not every one is citizen of every country)
science is real when its not faked
love is love (adults ony if its more than love ...)
true kindness is everything
I don't really care that much what is in my Mempool.
I care what is in my blocks.
I agree with you two points above. But, unfortunately, it's is those miners with stricter filters who are disadvantaged by reduced block propagation speed 😓
either you want to #exploitthebloat or you don't. pretty black & white to me.
I do find it amusing that #knots has caused a divide in #core.
biggest morons are barking in youtube n nostr bitcoin 21M al day
That's a different problem altogether. Which you won't fix by bending over. Once Knots and better tools for decentralized block templates are the norm it will change.
You just reject them and don't store them in your mempool, not filling up your hd and providing free storage for that spam.
Like on your mailserver.
Then why set the filter to 100k by default? Why filter at all? Why not permit up to 500MB or even no limit at all?
#RunningKnots
View quoted note →
You do realize that 1MB (blocksize) divided by 100KB is only 10 "transactions." If they had no other data. You're going from around 7 transactions per second to 1 JPG per minute.
4chan wants to store random 100KB files on your computer,, what do you do?
C'mon, be a man, and initiate a #hardfork -- you have the expertise to pull that off! Until then #Knot #filters will be an old teethless dog on a chain barking -- loud but powerless.
The mempool becomes a block every 10 minutes...
Lets see:
PLEBS ARE MORONS
I don't see Core devs suggesting this. I'm not a Core dev, I consider myself a pleb, so I disagree.
Core devs could spend more effort on getting their knowledge to the plebs, though.
YOUR NODE DOESN'T MATTER
Insofar as to what gets in the blockchain, your node doesn't matter. With this qualification it's true.
NO TX IS NON-STANDARD
Core rejects many TXs as non-standard, mainly for DoS protection, which is important for the robustness of the network. Not true.
FILTERS DON'T WORK
That's a fact. Filters cannot prevent unwanted TXs to get confirmed.
JPEGS AND ALTCOINS WELCOME
That's something others put in their mouth. I hear more of "We don't want monkeydick jpegs, but if we can't stop them at the consensus level, there is not much sensible to do."
RUN BITCOIN CORE
The only reasonable thing to do currently!
Currently near 100% of nodes have these filters. There are no raw continuous 100KB JPGs in the blockchain. I, along with at least 21% of other node runners, would like to keep it that way. Keep 4chan off our blockchain. #RunningKnots
Because the block size. We don't want large blocks, that was a debate a long time ago, and we agreed that large blocks have more downsides than small blocks.
This is already possible.
@npub1uqzg...d98g
Made 
as a meme for example, let's see how knots can prevent this without reverting taproot (f08fd61d48f79eeb0c4bc9e58f2d7ecad0e20e5d6411b588590cb0480c8e7fbe), the 80B limit didn't stop anything, and neither did your filter.
GitHub
GitHub - stutxo/labitbu
Contribute to stutxo/labitbu development by creating an account on GitHub.
>I don't see Core devs suggesting this. I'm not a Core dev, I consider myself a pleb, so I disagree.
Gloria Zhao gave a "pop quiz" to plebs to demonstrate her intellectual superiority. Ironically most plebs got it correct and she got ratio'd so bad she had to turn off her account.
We created an exploitable bug with Taproot. Instead of fixing the bug, let's embrace the SPAM and make it easier. Genius.
this can't be "fixed" due to the way merkle trees work, any "fix" would undoubtedly break real p2tr scripts
If we can't yet come up with a solusolution to our past mistakes, we can at least try not to make new mistakes.
If we can't yet come up with a solution to our past mistakes, we can at least try not to make new mistakes.
I think there is a way to fix it without breaking real p2tr scripts. Create a filter that checks if a control block, when parsed as a single hexadecimal string, contains a valid image format. If so, filter that transaction. Done.
easy to have false positives, and easy to counter.
shift everything 1 bit, literally and suddenly the control block doesn't get filtered but any client can still render the image
if that gets stopped somehow, you just xor the block with some value, or a bunch of other similar things
it is not possible to stop this.
if you shift 1 bit, we add that to the filter
if you xor by some value, we add it to the filter
it's not possible to stop filters