My heart goes out to the folks who have to tell their wives tonight that the reason theyโre down/sad is that they fought a war against a 4x more expensive & less harmful way to inscribe dickbutts on the Bitcoin blockchain and lost
And to those of you in the old school who believe this is a bubble, you simply have not understood the new mathematics of the blockchain (or you did not care enough to try). Bubbles are mathematically impossible in this new paradigm
Have you ever said thank you to Udi once for making enough ugly JPEGs to accelerate and reach the inevitable conclusion of the ideological divide in Bitcoin weโre now seeing?
Letโs face it; most of you are too dumb to understand the OP_RETURN drama, so youโll lean on the opinions of others to try to triangulate the morally and technically correct position
But if thatโs your dilemma, how is it even a question?
Have you ever said thank you to Udi for making enough ugly JPEGs to accelerate (and reach the inevitable conclusion of) the ideological divide in Bitcoin weโre now seeing once?
Itโs terrible that thereโs disagreement on the Bitcoin network in what transactions should get into the blockchain but Iโm so happy thereโs an amicable solution that works for everyone which is just that some node runners run Knots โ solves the problem and everyone is happy!
Tip: If youโre worried about blockchain bloat and UTXO set growth and want to keep the chain feasible to validate for small devices, a Bitcoin block 100% full of OP_RETURNs consumes the entire 4WU (weight units) allowed per block, while only filling up the 1MB base block with actual data.
This amounts to a -42% block size decrease relative to current average block sizes. Hurray! This helps with storage requirements and reduces bandwidth to sync a node.
OP_RETURNs are also by default *not* added to the UTXO set, so there are less disk I/O (read/writes) which reduces the wear and tear on your SSD or HDD (only 1 UTXO is added per block - the miner reward) or decreases RAM requirements for those who keep the UTXO set in active memory.
Nodes also wonโt have to compute those pesky SegWit merkle roots for these blocks, which your CPU will be happy to skip!
Bitcoin Cash people telling me I should come over to BCH because they have an opcode I want makes me feel like when my friend in Pakistan I used to play World of Warcraft with ages ago says I should move to Pakistan because his house has a bidet spray/bum gun (which I donโt)
I think bitcoin needs to become a MoE eventually, else another crypto becomes the payment MoE (if youโre turbo-bearish fiat), and I believe there is a real risk that whatever captures the MoE use case in crypto ends up re-capturing the SoV use case too, if itโs similar โenoughโ.
I was today years old when first I realized that virtually 0 bitcoin clients/node implementations out there do any form of surgical pruning whatsoever, not even witness pruning, at all. They all just throw away whole blocks over time. To keep you within your pruning limit. Lol
Hexicans be like โput your money where your mouth is!โ and then proceeds to stuff all their money up Richardโs arsehole, which, to their credit, is where their mouth is
The ETHBTC ratio did not go down because of โThe Mergeโ
The ETHBTC ratio collapsed because: - societal value rotation out of "feminized wef soyboys in unicorn t-shirts" into "bronze age mindset" broadly - ethereum always occupied a vertical more prone to competition - l2s confused the ETH asset value capture narrative and caused network fragmentation - eth does not have a saylor buyer - bitcoin and gold are maturing into wartime assets whereas the peacetime asset ETH struggles - ETH also struggles to even look nerdy/smart/futuristic compared to AI which is the new hot ball of money for that investor type - ethereum also stagnated into a depressingly small number of defi primitives relative to what past expectations were
*Not* the Merge.
Login to explore more contents
Explore the latest crypto news
โก๏ธ Be a part of the latests discussions in crypto