Replying to nobody

If you run a Bitcoin node there's a PR to remove the 80 byte limit for OP_RETURN. This could make it easier for spammers to put data on the blockchain and make running a node more expensive. Go let them know what you think.

https://github.com/bitcoin/bitcoin/pull/28130

Avatar
@IsabelSydow Queen of Shrimps (but u can call me Dan.) 2y ago

Im old enough to not know how to even visit github and to just keep my node plugged and ethernet wired....

If I didn't want this to happen, would I just keep the node form taking any updates?

Taproot snuck in there, i think, cuz we updated once almost every other node had taken it...

It was sold as a "privacy enhancement..."

Reply to this note

Please Login to reply.

Discussion

Avatar
Nice and Kind Vic 2y ago

You can not update if you want..or if you update you can set value for the datacarrier config option to prevent holding and relaying those tx in mempool. Its still valid in s block

de
nobody 2y ago

They're proposing to remove the datacarrier config which is asinine.

Avatar
Nice and Kind Vic 2y ago

And add datacarriersize in its place allowing more flexibility

Avatar
@IsabelSydow Queen of Shrimps (but u can call me Dan.) 2y ago

I'm saving this to show the hubs cus he's the one who fidgets with it on occasion, but this sounds important and I will tell him about it. To limit it.

Thank you!!!!!!!

Avatar
@IsabelSydow Queen of Shrimps (but u can call me Dan.) 2y ago

I hope I understood it correctly. 🙏

de
nobody 2y ago

There's an automation on that PR where you can comment "Concept NACK" and give your reason to vote on it.

If you disagreed with this and it got accepted you could just not update your node version. Or someone like me would go and fork the code and revert this change. We'd publish it so others could use it.