Bitcoin Forum

Bitcoin => Development & Technical Discussion => Topic started by: adamstgBit on March 29, 2016, 09:44:32 PM



Title: when will segwit be ready
Post by: adamstgBit on March 29, 2016, 09:44:32 PM
just wondering if anyone has any info / rumor of progress with segwit?

do you think they will be ready in april as expected?


Title: Re: when will segwit be ready
Post by: hudd on March 29, 2016, 10:36:24 PM
Original plan is for 0.12.X on April:
https://bitcoincore.org/en/2015/12/23/capacity-increases-faq/

However that's just the fork-ready code, the actual activation would take several months:
Quote
Dates with an asterisk are when we expect to release soft fork-ready code. The code will not be released until it has been well reviewed, and the actual fork will take time to activate


Title: Re: when will segwit be ready
Post by: achow101 on March 29, 2016, 11:30:30 PM
just wondering if anyone has any info / rumor of progress with segwit?
It's pretty close to being finished

do you think they will be ready in april as expected?
Probably. I think it will be merged in ready for a release by the end of April.


Title: Re: when will segwit be ready
Post by: adamstgBit on May 23, 2016, 07:30:57 PM
bump.

is it ready yet?


Title: Re: when will segwit be ready
Post by: rizzlarolla on May 23, 2016, 07:57:39 PM
bump.

is it ready yet?

Bump?

Like, WTF is going on?


Title: Re: when will segwit be ready
Post by: achow101 on May 23, 2016, 08:12:31 PM
bump.

is it ready yet?
It is still being reviewed. It's going a bit slowly. The code exists, the PR has been submitted, and AFAIK, it works. However, people are still reviewing it to make sure that there are no bugs and that it is optimized.


Title: Re: when will segwit be ready
Post by: rizzlarolla on May 23, 2016, 08:48:47 PM
bump.

is it ready yet?
It is still being reviewed. It's going a bit slowly. The code exists, the PR has been submitted, and AFAIK, it works. However, people are still reviewing it to make sure that there are no bugs and that it is optimized.

AFAIK?

exactly the problem with Core communication, the road map outdated,
(I see your trying to help, but)
Everyone knows afaik, and thinks it works, but no one seems to know wtf is really happening or going to happen or when.

Is that, in some part, because segwit will have no effect on "block space" for many months to come.
Whilst natural "user adoption" should continue to rise.
mempool could gridlock, leading to a stupid pointless fees bubble and long delays.
Bitcoin adoption stalled or permanently damaged.
Core should answer this question clearly,

Will it be "many" months, best case, before segwit has any noticeable effect on block space? (or longer, if ever)

I think I know.



Title: Re: when will segwit be ready
Post by: vlamer on May 24, 2016, 12:59:29 PM
bump.

is it ready yet?
It is still being reviewed. It's going a bit slowly. The code exists, the PR has been submitted, and AFAIK, it works. However, people are still reviewing it to make sure that there are no bugs and that it is optimized.

AFAIK?

exactly the problem with Core communication, the road map outdated,
(I see your trying to help, but)
Everyone knows afaik, and thinks it works, but no one seems to know wtf is really happening or going to happen or when.

Is that, in some part, because segwit will have no effect on "block space" for many months to come.
Whilst natural "user adoption" should continue to rise.
mempool could gridlock, leading to a stupid pointless fees bubble and long delays.
Bitcoin adoption stalled or permanently damaged.
Core should answer this question clearly,

Will it be "many" months, best case, before segwit has any noticeable effect on block space? (or longer, if ever)

I think I know.


Well, maybe Segwit part of the process towards Bitcoin 1.0 ..


Title: Re: when will segwit be ready
Post by: doc12 on May 24, 2016, 09:25:02 PM
I hope it will be deployed soon. Since there is no new Segnet Version in the last weeks I assume it is finally ready to go.


Title: Re: when will segwit be ready
Post by: zimmah on May 31, 2016, 10:12:33 AM
bump.

is it ready yet?
It is still being reviewed. It's going a bit slowly. The code exists, the PR has been submitted, and AFAIK, it works. However, people are still reviewing it to make sure that there are no bugs and that it is optimized.

It was scheduled for april, it's near June now, still nothign about SegWit, Lightning or 2MB blocks.

Mainwhile almost all blocks are now 999kB in size and have been for days now.

We urgently need some sort of increase in transaction capacity as there is literally 0 room for growth right now.


Title: Re: when will segwit be ready
Post by: gmaxwell on May 31, 2016, 06:12:01 PM
It was scheduled for april, it's near June now, still nothign about SegWit, Lightning or 2MB blocks.
I dunno where this april thing came from, but segwit was pull requested on April 19th (https://github.com/bitcoin/bitcoin/pull/7910).  Deployment waits somewhat on continued review (which is very actively ongoing-- though it would likely be faster if a single person from one of the companies saying we urgently needed capacity increases contributed) and to a lesser extent on the activation of the BIP 68/112/113 (http://bitcoin.sipa.be/ver9-2k.png) softfork. (It's possible to have multiple softforks running in parallel now with BIP9, but I think most people would prefer to not have the extra dynamics for the very first BIP9 softfork.)

It's worth pointing out that although btcd has a segwit implementation, Bitcoin "classic" and XT have taken no preparatory action here (and haven't even caught up to BIP-68 or BIP-9). Though these implementations don't have any real widespread use AFAICT, it's preferable to not just leave them behind.

Quote
Mainwhile almost all blocks are now 999kB in size and have been for days now.
We urgently need some sort of increase in transaction capacity as there is literally 0 room for growth right now.
You're looking at a not very useful metric: The only reason blocks are _ever_ not the maximum size now is because miners voluntarily cut the size to improve propagation or to avoid mining DOS attack transactions. It's much more interesting to look at the feerate for moderately fast confirmation (e.g. 4 or less confirms), which has been pretty stable over time.