The OP_RETURN discussion is not new and dates back to 2014 when Bitcoin Core 0.9.0 was released with the OP_RETURN policy included which was intended to discourage more egregious forms of spam. At that time, 40 bytes was the default max datacarriersize limit across all node implementations; this was and still is sufficiently large for tying data to a transaction (32 bytes for a hash and 8 bytes for a unique identifier). Core subsequently increasing the default to 80 bytes was an entirely voluntary decision and in no way contradicts the design objective that OP_RETURN creates a provably-prunable output to minimise damage caused by data storage schemes, which have always been discouraged as abusive. There are also other good technical reasons which I have chosen to retain the lower default in Bitcoin Knots, and no justification for increasing it.
It is not my intention, nor that of my team at
nostr:npub1qtvl2em0llpnnllffhat8zltugwwz97x79gfmxfz4qk52n6zpk3qq87dze, to filter coinjoins. These present an innovative tool for increasing Bitcoin’s privacy and, when constructed properly, coinjoins can easily stay within the OP_RETURN limit (indeed, there is no reason for them to have *any* OP_RETURN data at all). I have some ideas on how to alleviate the recent issue where some coinjoin transactions were flagged as spam from Knots v25, and I am willing, with the full resources of my team, to work collaboratively on a solution in good faith.
Bitcoin does and always has allowed nodes to set filters based on multiple sets of criteria and Knots v25’s defaults are IMO what is best for Bitcoin at this time. Others may disagree and that is ok. They are free to (and should) run their own nodes - it is good for Bitcoin to have more people running nodes, including miners, and there should be a natural diversity in node policies. As was stated before, OCEAN is on a path to decentralization and very soon we are going to be in a position where hashers will be able to fully participate as miners and perform the intelligent parts of mining such as deciding which version of node software to run and what filters or other policies to apply to block template construction.
Stop messing with it. Listen ffs.
Funny. I was saying this on Shitter last year. Bitcoin fixes itself. We don’t need to interfere Luke. Just sounds more like he just doesn’t really get Bitcoin. Sorry, not sorry.
Inconvenient truth: AI will be owned by giant corporations. Not you.
What's up with Iris? Why does this web client have to be so bad? It's time some seasoned devs came through with something better for nostr. It's not a good look.
If you watch MSM news and/or read it online, you are part of the problem.
Everything will always just sort itself out.
I always think of being superhuman and the best of the best. It really does work.
I overheard that apparently some people were actually impressed by ChatGPT 4… Is this true???🤯
Why is that even a question? It should be as easy as saying that it’s its own protocol. There’s nothing more to be said about it.
Honestly, thinking with emotions is where human beings get into trouble most as a species.
Doom scrolling: No one wants to hear me out because they don’t think it could be fixed. Sad… If that’s the case, nostr is doomed.
When I was a kid, the kids playing video games were nerds and talk radio was for boring, old dudes. Now it's cool to be a gamer and they all want to know what podcast you listen to. LOL...
We must fix doom scrolling, strive to get rid of it, with nostr. This is one of the worst "features" of social media.
This is exactly the experience I had. I cashed out all my stocks, converted most of my money from the bank to Bitcoin.
