core vs knots is just another way that you are allowing yourself to be divided and fighting like dogs
both sides are fucking you over in real time and telling you that the other side will cause unthinkable horrors
Discussion
There should be many more bitcoin software options.
now that there is decent separation of consensus critical code, it is best that it happens
the bitcoin core client and derivatives are technically flawed in much dumber but important ways, like still using LevelDB even though it keeps corrupting data over and over
and the lack of more clients that focus on more things, like maybe more flexible data analysis, or compression for a smaller chain, etc
Core devs: "We're gonna push through this change because fuck the users"
Knots devs: "We're gonna push through this soft fork because fuck the users"
Maybe the two tribes can unite each other under “we love people that hate our opinion”
Empty your mind, be formless. Shapeless, like a cat. If you put cat into a cup, it becomes the cup. You put cat into a bottle and it becomes the bottle. You put it in a teapot, it becomes the teapot. Now, cats can flow or it can crash.
Be a cat, my friend.
nostr:note10vg9vg5f3yyq6kgt06n0y36k23gdtt64dmjf66kld7uexu69tcnqsll834 This thread is really confusing because you’re both confidently saying directly contradictory things. But thank you for the information you’re providing.
Basically, witness data is only necessary for proving *authorization to spend*. It can be discarded and it is what happens with pre-SegWit clients.
The witness merkle root is committed separately of the main merkle root.
Inscriptions store data in the witness which can be easily pruned, and also is cheaper (which does not matter, except for the fact that economic incentives will push people to use it).
OP_RETURN is committed to by the main block hash. Unlike the witness which can be separately downloaded and if needed ignored from the main block data, the OP_RETURN is part of the main transaction. This means you have to download OP_RETURNs to be able to verify a block and much more important guarantees like:
- no double spends
- conservation of supply
Assumevalid could be extended to not download witnesses on old blocks as they are only needed to prove the authorization to spend.
good chance this is a perfect encapsulation of the entire messy issue
the original point was “op_return was easier” for some cases where you needed just a little bit more data, as you did not need 2 txs.
it was never cheaper or better compared to inscriptions for mass data storage, and was in fact a major step back on that front
now all of this is moot because taproot annex exists which does the best of both worlds and is even more “prunable” as it is guaranteed useless
the fact that the limit was increased beyond a few KB feels even after user feedback feels like there is no regard for sensibility, and nuking op_return to 40 bytes like with knots is also pointless as it can’t fit enough data for some use cases
all this has done is one of the leading implementations being open arms to data storage which will encourage it, while leaving people with 2 shit choices
I also do not understand why some people feel the need to defend use cases they have no involvement in
there is 1 problem with inscriptions which is that it created a ton of dust outputs, but this is more of a problem with the fact ordinals encouraging 1 UTXO per inscribed “sat” as any other way was hard to manipulate by a wallet app
and that consolidating the 2nd tx output was not economical in terms of fees at high feerates, when your intention was to store data, compared to just leaving it be and forgetting about it
A 6 month Slop_RETURN psyop brought to you by Luke and Ocean 💐
if it didn't take me forever to write this on my phone keyboard we mighta jinxed eachother
party-as-solution was the term I was looking for.
Just because someone chooses to use Core or Knots does not mean they automatically want BIP 444 or think the ignoring of user feedback is a good idea.
Maybe they do not know of the other options, or the ideal option does not exist yet.
bull cycle noise
If we aren't aware, then we are really fuck! So I prefer to educate myself and arrive at my own conclusion: this is #Bitcoin, and it is money. Peer to Peer Cash
interpretation: don't run a node and don't participate in node discussions.
Just post mindless vlog slop on nostr and let the smart people figure it out.
Ultimate cuckery.
Actual interpretation: knots vs core is a false dichotomy, and both sides are fucking people ovef
we need more implementations/patchsets that match people’s choices instead of people fighting each other over deranged #1 and deranged #2
reading what that update does, the simple solution is before making transactions, first clean up that extra space so you don't send anything else
The true fight is against monetary tyranny.
This kind of thinking is useless. Ideas were always meant to go to war with counter ideas. It’s how we tell which ones are true. There’s not always a middle ground.
If we never disagree, then we are living in a dictatorship
False dichotomy, I just don't want to see garbage on the blockchain, and knots is the only thing that allows me to do my minuscule part in both filtering as much garbage as possible and in signaling to the rest of the network that I am against it.
But I don't care for the rest of the politics behind the schism.
🎯
Just like politicians
Core is trying to change Bitcoin.