pull down to refresh
Then, outside of treating the 'segwit' discount (which bip-110 doesn't even address) OR simply reducing the blocksize (which is obviously much simpler...)
What is the point of Bip-110? This is why I don't use knots or support bip-110. They don't really know what they are trying to solve.
I agree that the BIP-110 approach is not perfect. I would prefer a removal of the witness discount. But I am also not going to oppose BIP-110, since it would still reduce inscription spam.
Friend it will result in a hard-fork, it is not needed, it increases risks for plebs, it doesn't know the problem it is trying to solve (low block-space utilization), and most importantly you could easily end up on the wrong side of a hard-fork which is coming for bip-110 users.
Most users are better running Core on default settings, getting a lightning wallet and using those everywhere they possibly can to educate people on what Bitcoin is.
Hard fork means that new blocks are invalid by the old rules. Bip110 is a soft fork.
In case of a chain split you will not lose any coins on any side of the split. If you don't make any transactions you can wait and see which chain will be the one accepted by the people. No risks here.
Sure there is 'no risk'... but a lot of plebs don't know that. They don't even know that once September approaches the bip-110 will 'auto-activate'... and their nodes will have different rules from the vast majority of miners. There could easily be a 'hard-fork'... and any transactions they make could easily leave their utxos vulnerable confusing their view of the entire network.
My understanding is that 110 nodes once "active" will sever connections with core nodes putting them on a new network leaving 'their new' network incredibly vulnerable - it is a terrible idea and creates 2 tokens.
Influencers IMO are leading plebs down a dark path they are not accurately explaining.
It is not known in advance whether miners will or will not implement bip110. The bip110 nodes will sever the connection to the non-bip110 nodes after bip110 activates not at the point of activation, but as soon as the first non-bip110 complient block gets mined.
Why would miners actively decide to give up revenue???
Thanks @Murch
Is a chain split... not a hard-fork? I have read that a 'tightening of the rules' is a 'softfork' but... if bip-110 nodes start rejecting blocks and my 3 Core nodes don't reject those same blocks
Bip-110 and Core nodes will be on 2 different networks. Is that not a hardfork? I find that knots-supporters calling it a 'soft-fork' assumes that a lot of miners join them but if they don't their chain will keep rejecting Core-compatible blocks and if miners keep building on those blocks it's a chain-split.
2 tokens and 2 networks.
Honestly I feel like Knots should just embrace this - call it Bitcoin-Pure or 'Bitcoin-Knots' with its own network and own token that way people can more transparently discuss which network they want to use and run.
Oh, I see what you mean. Right, if we were on BIP-110 rules and switched to Bitcoin Core rules, that would be considered a hard fork. But going from Bitcoin Core to BIP-110 would be a soft fork attempt, although a failed soft fork does behave like a hard fork from the perspective of the soft forkers (although they explicitly updated to it, so there wouldn’t be nodes left behind due to not realizing what happened). I explain it a bit more comprehensively here: https://bitcoin.stackexchange.com/a/30821/5406
Yes, I would really be in favor of this!
UTXO set bloat becomes less of a problem with Utreexo.
Also OP_RETURN outputs are not part of the UTXO set.