This will take some time to unpack but you are completely wrong in a lot of your assumptions. Firstly, no one puts arbitrary data in OP_RETURN. It's cheaper to stuff the witness data. It's not cheaper because of filters. It's cheaper because that's just how Bitcoin works.
Second, send me 5k sats right now and I'll make a TX with OP_RETURN larger than 80 bytes, I won't go out of band (to mara) because I know how to use a node and I don't have to.
Third, I have no interest in putting jPEgs on Bitcoin. That's dumb. If I were going to put arbitrary data, it would be some text or a message and I would just put it in OP_RETURN because it would be that big of a message.
I'm not "full of shit". I actually know how Bitcoin works and how nodes work. Your filters only affect your node. They have no bearing on what transactions are mined.
If they don't do anything, that is precisely the reason to remove them. Why have code in the code base that doesn't do anything?
Go ahead, send me 5k and I'll make that tx with a standard fee rate and it'll be mined by someone in around 10 minutes after I broadcast it. I've done it before to prove a point. I'll do it again.
I don't run core or knots. I do run a node though.
Get off your altruistic high horse and try listening to people with more technical Bitcoin experience than yourself. Have a little humility. Everyone on your "side" admits they are not technical while anyone with any knowledge of how Bitcoin actually works, are in the camp of removing the useless filters.
I'm happy to change my mind if someone can demonstrate THEIR filters stopping MY tx with an OP return past the default limit. No one can. Because you can't censor a concensous Bitcoin transaction. As it should be.
Omg boomer text wall, yeah dude, congrats you run node, so does everyone else. You describing a way to get around a filter doesn't mean the filter isn't doing anything. That is the giant faulty premise in your logic you are purposely ignoring.
I'm not going around anything. I'm Broadcasting a transaction with my own node to a decentralized network. Clearly you have no interest in learning. You're dug in. Mac vibes.
You can't just counter an argument with "you make long post, you dumb"
You're making yourself look stupid. Argue the facts. You can't because you don't know them and when people tell you, you just say okay boomer and think they must be wrong. Personal bias be damned.
Do you actually want to talk about how filters don't do anything to affect the network? Please tell me how the filters on your node or anyone else's, stops me from broadcasting a tx from my node...
Tell me. You can't because they don't.
Thread collapsed
Make your point concisely I don't want to read all this verbose shit. Broadcast whatever you want, my node won't necessarily relay it, that's how filters work.
No your node won't. But it doesn't have to. I don't care if your node relays it. Once I broadcast a tx, of it's concensous, it'll get relayes by many. Even if 99% of the network filters, it's still going to go through.
Try broadcasting a dust transaction its consensus valid but 99% of the network is going to block it anyway. There are still some old legacy nodes that don't filter dust. Filters work. Dust is proof
I made a tx like a few months ago with dust, paid 1s per vb and got into the next block. I did this to prove the same fucking point to someone on nostr. Filters don't work. My dust tx proves you wrong.
Thread collapsed
I would do it again, but I'd rather dig up that tx to show you. I consolidated the dust afterwards because useless UTXOs are no good.
Thread collapsed
Weird I don't get dust attacked anymore
You don't dust attack a node, you would do it to make a bunch of unspensdable UTXOs which grows the UTXO set and affect the whole network. No one would do that because it's just throwing money away...
Thread collapsed
OK, let's say your right and filters don't stop anything (I remain wildlyskeptical), how about we leave them in just case your wrong. If I'm wrong there's no harm. If your wrong you've just junked up the blockchain with garbage.
They did leave them. Core 30 is not out yet but when it dies come out it will still have all filters. Todd's PR was not merged. Default limit for opreturn will be raised to make it basically unlimited. You can still set your own limit in your bitcoin.conf to whatever you want. Also opreturn is the only filter in question here. All others Policies remain the same by default I believe. Policies and defaults exist for making sure users don't submit unintended transactions. They don't exist to stop anything from being relayed.
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
