anyhow it looks like ltc will segwit, which will be interesting
I've been putting all of my BTC miner earnings into LTC ...
Topic: SegWit2MB The Forking Compromise - page 2. (Read 1470 times)
I've been putting all of my BTC miner earnings into LTC ...
There are transaction delays and unpredictable fees. The price of BTC is going up and so are transactions. I do not see how slapping on a layerII code will address these problems. The only thing it will do is increase delays and push funds elsewhere, such as LTC, which has 2MB block sizes and they are voting on #SegWit. I think it makes more sense there and larger blocks for bitcoin.
Why would we fundamentally fork - I mean fundamentally, not vía code - Bitcoin when larger block sizes will continue to work as they have in the past?
Why would we fundamentally fork - I mean fundamentally, not vía code - Bitcoin when larger block sizes will continue to work as they have in the past?
Why do we need hard fork for the sake of simply having a hard fork?
Are you trying to please BU community which expects that any change can be done only via hard fork?
It will be trade of this kind: "Oh, look! We will let you hard fork bitcoin if you allow SegWit to activate, deal?"
No, I don't like it and we don't need it.
Are you trying to please BU community which expects that any change can be done only via hard fork?
It will be trade of this kind: "Oh, look! We will let you hard fork bitcoin if you allow SegWit to activate, deal?"
No, I don't like it and we don't need it.
i guess its an attempt at a compromise?
anyhow it looks like ltc will segwit, which will be interesting
Why do we need hard fork for the sake of simply having a hard fork?
Are you trying to please BU community which expects that any change can be done only via hard fork?
It will be trade of this kind: "Oh, look! We will let you hard fork bitcoin if you allow SegWit to activate, deal?"
No, I don't like it and we don't need it.
Are you trying to please BU community which expects that any change can be done only via hard fork?
It will be trade of this kind: "Oh, look! We will let you hard fork bitcoin if you allow SegWit to activate, deal?"
No, I don't like it and we don't need it.
I hate it, this crazy 4MB block weight doubled to 8MB effective blocksize just doubles the shittness of segwit IMO. I want malleability fix + EC HF, thats it, thats all.
SegWit2MB takes the Bitcoin protocol as it stands, but it adds a 2MB block size hard-fork that activates only if Segwit activates.
post your thoughts below and your votes above.
post your thoughts below and your votes above.
Jump to: