Akashi Hyogo's avatar
Akashi Hyogo 3 months ago
Citrea does not need the OP_RETURN increase. Here is explanation from sb from your tribe:
Super Testnet's avatar Super Testnet
It was Citrea, and AFAIK they plan to use utxo stuffing only if a bitvm contract is challenged. This is designed never to occur, as it requires someone to manually create and submit a "cheating" bitvm transaction, whereas "honest" bitvm software is designed to try very hard not to let you do that. Besides the disincentive of manual work, it also carries a huge monetary disincentive: your counterparty in the bitvm contract is meant to be running software that automatically detects cheat txs and responds by taking all of the money the cheater put in the bitvm contract. (It works a lot like a lightning penalty tx, but more complicated because bitvm is complicated.) Despite being designed never to occur, this potential for extremely rare utxo stuffing by one party has been leveraged to relax the op_return limit for everyone. Which I think is silly.
View quoted note →

Replies (1)

BitcoinIsFuture's avatar
BitcoinIsFuture 3 months ago
Well, did you see the video? I am sure there are ways to improve UTXO stuffing. Also what Super says is the abuse on the UTXO would not be so significant so thats less of a threat than blowing up OP_RETURN to 100 000 Bytes. Also there were mentions that other companies manage to do their tech with less than 80 Bytes OP_RETRUN. But what we see from the compromised Core devs are intential malicious actions - not fixing inscriptions spam for example.
BitcoinIsFuture's avatar BitcoinIsFuture
See the compromised Core devs who rejected Luke's PR that fixes inscription spam. They are the bad actors (the NACKers) They revealed themselves with their public comments on OP_RETRUN being dishonest and manipulative. The guys that ACKed are the good guys we have. image https://github.com/bitcoin/bitcoin/pull/28408 https://github.com/bitcoin/bitcoin/issues/29187 Bitcoin Knots has fixed those issues.
View quoted note →