Also mean thing is, impact is just noticed when gatewas is restarted. Had it today upgrading from 14 to 21; first though it was because of the update but the config was messed up before. Not sure what caused it. Also noticed strange behavior when editing config in vscode, so that stuff is suddenly stripped away.
@grok What are the estimated costs and time required to restart a single nuclear reactor unit in Germany? Considering the €200 billion+ spent on the energy transition since 2011, would restarting these reactors be a cost-effective and environmentally sustainable option compared to the current reliance on less green energy sources?
@grok As an expert in economics and green energy, do you believe it would be worthwhile for Germany to restart its newer nuclear reactors, given the current reliance on coal plants, which are environmentally unsustainable, and the high energy costs driving industries away from Germany and Europe? Please provide a comprehensive list of all German nuclear reactors, including their construction start dates, commissioning dates, and initial design lifespans.
Yes, I can explain that
The default of 80 bytes was useful earlier in history because it did prevent people from building protocols that stuffed more data than that in OP_RETURNs
It was also believed at the time that there was never any legitimate need for more than 80 bytes of arbitrary data since it is enough for a hash and some extra metadata.
It was not expected that any *monetary* L2 protocol would need more than that in any forseeable future
With BitVM, it changed, because now *monetary* L2 protocols that leverage the Bitcoin asset find usefulness in being able to post ZK proofs in OP_RETURNs, and these are slightly larger than 80 bytes, that's why the discussion became "maybe we should increase it to 160 bytes?"
However the science behind why "160 bytes" would be the perfect number is not exact nor even very precise. That's just the size of a Groth16 proof and a little extra for metadata.
STARK proofs for example (another type of ZK proof) are more trustless and less "exotic" (more established underlying cryptography), but their proofs are much larger. So if you set the limit to 160 bytes, you now favor ZK technology that has built-in trust assumptions over trustless ZK technology
(By the way, Satoshi and Hal Finney were both deeply interested in finding ways to improve Bitcoin using ZK proofs, and I think you’ve probably seen Luke Dashjr mention that it’s his priority too? This is not some shitcoinery, it’s really useful for Bitcoin in a monteray way, and nearly all devs understand that)
So the question then becomes, why set a limit at all on OP_RETURN? What you have to realize is that Core has already given up the fight on trying to stop 400,000 byte inscriptions in the witness portion of the block
If people started to use OP_RETURN in large sizes, it would mean 4x less data bloat than if they used witness inscriptions, and it also would leave the UTXO set unbloated, so if people favor OP_RETURN over witness inscriptions, there's only upsides to it
That's why the limit was removed rather than trying to fine-tune it to an exact limit, and having to readjust the default limit constantly as monetary scaling and privacy solutions find new optimums for it
All that said, the problem with all that I just wrote is that it requires a technological understanding, and I understand that what I said just sounds like *poof-pang wizmajjizz!" as I try to sneak a 100kb OP_RETURN up your butt
This is why the two camps can fundamentally never agree or understand eachother. They're too far apart.
Here's a writeup I did that writes about the conflict from *your* perspective, attached below. Do you agree with it?