Avatar
isaac-asdf
65c832e0ba60926ba4c92412bb099a0cc2f966872ae39f41e6d9560dc6a8bd9a

I would rather not establish precedent that node operators are responsible for the data on the block chain. That opens up a trivial attack vector by literally anybody. Making the argument that it’s a public space and therefore individual people aren’t responsible is much safer/robust over the long term

“Despite the controversy” - this is IMO the biggest issue here. Influencers making non-technically sound arguments should not be able to change the course of dev work

I think it’s worked for a while. I’ve got zaps going back a few months at least that I think all were nwc

The patterned side would then be on you while you sleep, which is definitely less comfortable tho

Eat Your Kids by #Hozier live 🙌🏼

Except there’s no prize for catching mice. There will just always be another mouse. And the dead mice you catch don’t die, they just get sent direct to miners. Oh wait, I’m not talking about mice anymore…

Being able to choose to not mine them seems reasonable, but I think not relaying them hurts overall network decentralization. All nodes benefit from seeing potential transactions before they come in a block so you can verify validity pre-block arriving. So if you withhold propagation it harms other nodes when a block does arrive

Replying to Avatar Guy Swann

For everyone getting on me about the OP_RETURN stuff:

I’m 100% open to being wrong, I was wrong about CTV and how I thought it could be maliciously used, but I’ve also only heard a handful of the exact same arguments about this issue for years and have been very clear why I don’t think they are sufficient and why I believe some of them are not even relevant.

• “Filters for what goes into the chain are censorship,” this is false and filtering what can be done on chain is literally how and why Bitcoin works in every way that it works. This completely begs the question about what is spam and what is an exploit, which is the whole debate.

• “You can get around it” isn’t relevant either, as standards make a difference, which is exactly why the discussion is around changing the standards. Same as someone can jump over my fence, but that doesn’t mean having one vs not being allowed to build one has no effect at all.

• “Your node doesn’t do anything,” Is the same argument I was told during the blocksize war. I’m aware it doesn’t alter the entirety of the network and it’s just my node, so don’t tell me like you’ve discovered some new information, but it is still *my* node and someone proposing to remove my control over what I should or should not accept and propagate isn’t why I run a node. I use my node to mine and wish to build my own templates. Explain how putting Bitcoins use as money ahead of as a place to store jpegs is bad. I don’t care how ineffective you think it is, but why is it bad for Bitcoin?

• “Just run Knots.” Correct, I will be now. But that doesn’t mean I don’t have an opinion about changes being made to core, and when feedback is asked for I’ll give you my honest opinion. If that bothers someone then being part of a decentralized protocol is probably not the best path for them. All anyone has done since I got into bitcoin was argue. That’s how decentralization works.

• “They paid a fee and it’s valid.” See point 1. Every bug and malicious transaction and spam in the past was always valid and paid the proper fee. Again, completely begs the question as to what is spam and what the highest purpose of Bitcoin is.

This is a conversation about the purpose of Bitcoin, and yes that’s subjective, but that doesn’t mean it’s arbitrary or it doesn’t matter. Convince me that allowing random data in unrestrained sizes will make Bitcoin better money, or the technical argument doesn’t matter, imo. Technical conversations matter only after we decide what is *worth* building technical solutions for and what the purpose of any technical change is… so again, it begs the question and comes back to the same old disagreement.

This is how I see it and I don’t see how this is at all an unreasonable perspective. Just my 2 sats

‪“You can get around it” - changing standardness to allow your node to have an accurate picture of the mempool and future blocks protects you as a node runner. Your fence analogy breaks down at who is harmed by breaking the rule - by filtering out consensus valid transactions you (the node runner) are more likely to be hurt than the person propagating the transaction

It sounds like you are saying experience trumps all other knowledge. You can reason about something and have a valid/more informed opinion than a participant in something