pull down to refresh
352 sats \ 19 replies \ @DarthCoin 2 May \ on: My High-Level Synopsis of the Recent OP_RETURN Debates bitcoin
FUCK CITREA
Do we really need their garbage?
If this comment raises a million sats i'll vibe code a similar platform that uses OpenTimestamps and WebTorrent and call it Shitrea
reply
Im almost tempted to zap you this 1M to see if you will really do it
reply
lol, I had to think carefully about the amount to make sure it was high enough to be unlikely but low enough to bait some zaps... i'd probably get way more into it than I have time for
reply
be careful... Justin is a very determined guy...
reply
Want to see if he is THAT determined! If I get a boatload of sats I may have to see if he is truly a man of his word
@remindme in 5 months
reply
OpenTimestamps is not a solution for the problem Citrea is facing. They need a proof-of-publication: proof that data was widely published.
OpenTimestamps just doesn't solve that problem, and fundamentally can't.
Lightning uses this concept too: HTLCs are a proof of publication mechanism too. If they go on chain, the transaction ensures that the pre-image is made publicly available, ensuring the next entity learns the pre-image that they need to collect their funds.
reply
Good explainer...
Do you suppose a hypothetical Shitrea could carry forward the entire history with each update? this would obviously result in bloating itself toward unusability, but for shit shootings sake, do so instead of socializing that cost to the chain?
reply
LOL "shitrea" hahahaha good name!
reply
I agree, it's definitely a bad look for Core to be so cosy with them.
I'm glad my comment cannot be hidden on SN 😅
reply
Dumb comment.
Citrea is using perfectly standard transactions right now; we can't stop them.
In the process, Citrea occasionally creates unprunable outputs that bloat the UTXO set. We would prefer that they use OP_Return instead. They can't at the moment, as they need more than 80 bytes of data.
reply
Peception is you're playing ball with a company that doesn't give a damn about using Bitcoin as money.
We would prefer that they use OP_Return instead.
Sjors recently said in the mailing list that they probably won't.
So is the public/userbase that sees bitcoin as money supposed to then believe this pr is justified by the off-chance that "occasionally" it will divert unnecessary UTXOs?
Will it create the incentive for those non-monetary use-cases that are already spamming the network to play nice because you "would prefer" it that way?
In fact both scenarios seem unlikely to me.
And even less likely, is that this is a also a thorn in the side of mining centralization.
On the contrary, this change opening the door to new-non-monetary ways to spam the network seems much more likely to happen.
I get that Core devs are doing often thankless work, and I certainly don't take that for granted. Nor do I want to drag your name in the mud, Todd. But in spite of the countless hours I've spent trying to understand what's going on, there are still things that don't add up. I wouldn't suppose to know the details as intimately as you, but please try to afford me and the other concerned users sympathy, as I have afforded you.
reply
I didn't asked how much bytes they need for their shit.
I asked why bitcoiners need Shitrea...
reply
reply
Then why do we have to remove the restriction anyways?
There are more things we don't know yet about this fucking citrea... so better do not play their game.
reply
Because if their spam is in op_return... it has minimal impact.
If their spam is in bare multisig or fake public keys... it creates unspendable utxos that increase the utxo count permanently.
reply
What we need is serious spam filters implemented and maintained so this people will get expelled form the bitcoin ecosystem and find something else to destroy from withing. If this will not be done bitcoin would experience dead of a thousands cuts in a few years. It is my opinion that ETFs and inscriptions are dark side attacks. Let's see if bitcoiners will have the courage to fight again! I sense a great disturbance in the force this days pain and confusion avoid we must!
reply