pull down to refresh
It's a soft fork.
A soft fork can still produce a chain split.
If miners do not enforce BIP 110, nodes running BIP 110 will fork off from the main chain in September.
Yeah, I know.
BIP-110 is much closer to Segwit than to BCH, given that Segwit was a softfork, while BCH was a hardfork.
True.
And also BCH enabled much bigger blocks, which hurts decentralization. Meanwhile BIP-110 aims to do the opposite by reducing block bloat caused by inscriptions.
So the comparison to BCH makes no sense.
Blocks aren't bloated due to inscriptions... maybe the UTXO set is, but not blocks themselves. Blocks are the same size.
And UTXO set bloat can and does occur with 10 byte op_returns (with bip-110 doesn't fix) so imo bip-110 changes nothing.
Blocks aren't bloated due to inscriptions... maybe the UTXO set is, but not blocks themselves. Blocks are the same size.
Blocks might have the same weight but one look at a block explorer shows that blocks are not the same size in terms of bytes:
And UTXO set bloat can and does occur with 10 byte op_returns (with bip-110 doesn't fix) so imo bip-110 changes nothing.
OP_RETURNs are not part of the UTXO set.
OP_RETURNs are not part of the UTXO set.
No they aren't... but someone can 'pretend' than an op_return creates a 'token' therefore 'pretending' that one op_return and lots of outputs... means lots of tokens. "Runes" memecoins do this but there are unlimited arbitrary possibilities.
Blocks might be the same size in terms of weight but one look at a block explorer shows that blocks are not the same size in terms of bytes:
Blocks are bigger due to the 'witness discount', witness data weighs less than transactional data
No they aren't... but someone can 'pretend' than an op_return creates a 'token' therefore 'pretending' that one op_return and lots of outputs... means lots of tokens. "Runes" memecoins do this but there are unlimited arbitrary possibilities.
Yeah, they can pretend but Bitcoin nodes do not care about Runes. It's just an unspendable script with an OP_RETURN and some unimportant data to them.
Blocks are bigger due to the 'witness discount', witness data weighs less than transactional data
Correct. This witness discount is exactly what inscriptions make use of, causing blocks to balloon up.
Yeah, they can pretend but Bitcoin nodes do not care about Runes. It's just an unspendable script with an OP_RETURN and some unimportant data to them.
Correct. That's why it's impossible to stop. Even if bip-110 were fully implemented and adopted... it wouldn't stop runes memecoins or any other arbitrary schemes for gambling on random data.
Bip-110 has an 83 byte op_return limit right? So it doesn't stop Runes at all
Bip-110 has an 83 byte op_return limit right? So it doesn't stop Runes at all
Fine by me. I don't see OP_RETURNs as the problem.
Inscriptions are the problem.
It's a hard fork, they just somehow think they're 'going to win'.
The bcashers thought the same