Topic: Segregated Witness has been merged! - page 2. (Read 2126 times)

Are you being serious or joking? The core developers have done everything but run Bitcoin directly into the ground.

Sorry for being naive... I understand Seg Wit will help bitcoin to scale... Just curious: Is bitcoin the first crypto-coin with Seg-Wit or has any other Alt-coin incorporated Seg Wit?

Blockstream does not "basically represent core". That is a common misunderstanding spread by r/btc FUDers.

So... not running a Segwit release before the HF version of Core is released is perfectly allowable by the agreement.

Says who? I don't see it in any part of the agreement that segwit and a hard fork will come packaged together. If you are referencing antpool, then they are breaking the agreement as the agreement does not say that segwit and the hard fork will be activated at the same time.

We will run a SegWit release in production by the time such a hard-fork is released in a version of Bitcoin Core.

While your capitalized sentence is correct... it doesn't tell the whole story.

SEGWIT WILL NOT BE ACTIVATED UNTIL/UNLESS HF CODE FOR A FUTURE (mid-late 2017) HF IS RELEASED IN A CORE BINARY.

So... people should not get too excited about the additional capacity generated by moving signatures to witness until the HF code is released by core.

Activated Live Segwit and HF (for 2017 activation) do come together as a package, yet they don't activate together.

The Hong Kong agreement explicitly states that the hard fork code would be ready within 3 months of Segwit's release, something that has not happened yet. The miners agreed that they would run Segwit in production in the meantime. IT DOES NOT SAY THAT BOTH A HARD FORK AND SEGWIT WOULD BE DELIVERED AT THE SAME TIME.

The HK agreement between miners and blockstream (basically Core) represents consensus. It clearly says both 2 MB hardfork and Segwit to be delivered. Doing one but not the other one is actually stalling - not to mention breaking intentionally agreement is quick way to loose all credibility - not best day for Bitcoin if it really happens considering blockstream basically represents Core, the most used Bitcoin full node implementation today.

Let's stall consensus and blame Core afterwards. Good idea! 

After months of testing, coding, and work,

Core team are increasing the blocksize, Segwit is that increase. They're increasing more than what the Antpool owner has demanded, so what his issue is, I'm not sure tbh. Let's not all forget that Antpool might have ~7% hashrate today, but tomorrow is another story. Even next Tuesday is a bit uncertain

They're increasing more than what the Antpool owner has demanded, so what his issue is, I'm not sure tbh.

Innovative scaling, like the dao. The segwit disaster is lurking.

So we get both! (or neither) Cool!

Good news. This is well needed! But what's with the backporting again? Just update the current version and end support for older versions... Makes no sense.

This is very good, and is very important that he holds his ground. Bitcoin is in desperate need of a max block size increase, and as long as the blockstream core devs hold a veto card for any HF, it will be difficult to get a max block size increase without withholding support for something that the blockstream core devs need.

According to Jihan Wu, who controls Antpool (25% of global hashrate), there won't be any live segwit without a HF blocksize increase for 2017 activation.

So we get both! (or neither) Cool!

[img ]https://i.imgur.com/S89dQkA.png[/img]

This is innovative scaling, unlike a block size increase.

This is innovative scaling, unlike a block size increase.

When is activation?

Deployment plan

The following plan describes how segwit is expected to be deployed.

Merge to master (without mainnet activation code): after Bitcoin Core developers “ACK” (approve) the final segwit pull request, it will be merged into the Bitcoin Core master Git repository branch. The code that is being merged will include everything in segwit except for the activation code. This will make it easy for developers to test other features on top of segwit, such as compact blocks. Activation on testnet has already occurred so users and developers may experiment and test segwit on testnet.

Backport to 0.12 branch: the unactivated code will be backported to the 0.12 maintenance branch and the backport will receive its own testing.

Choosing the BIP9 parameters: BIP9 is a soft fork deployment mechanism that allows miners to signal their readiness to enforce new consensus rules. Each soft fork made with BIP9 chooses when miners can begin signaling for the soft fork, when the soft fork is considered unsuccessful if not enough miners have signaled for it, and which bit in the block header version field will be used by miners to signal their readiness. These parameters will be selected at this time and implemented along with the code to activate segwit on both the master and 0.12 branches.

Release candidate phase: after all developer testing is successfully concluded, a release candidate (probably named 0.12.2RC1) will be publicly provided to anyone willing to test the code. Miners, merchants, and wallet vendors are especially encouraged to test. If any problems are found, they will be fixed and a new release candidate will be issued. This will be repeated as necessary until a release candidate is found with no known problems.

Binary release: the final release candidate will have its version changed to the final release version (expected to be 0.12.2) and will be released for all users to download and begin running at their leisure (segwit is a soft fork, so upgrading is only required if they plan to use segwit features).

Miners upgrade: miners who choose to upgrade to 0.12.2 will be able to start producing blocks that signal readiness to enforce segwit once the date defined as segwit’s BIP9 started date is reached.

Lock-in: once 95% of blocks in a 2,016-block long retarget period have signaled that their miners are ready to enforce segwit, segwit will lock-in – meaning that unless the blockchain is rolled back at that point, segwit will become active (see next point).

Activation: 2,016 blocks (about two weeks) after segwit is locked-in, it will activate. That means all full nodes running segwit-aware code will begin requiring miners to enforce the new segwit consensus rules.

Wallets upgrade: similar to the P2SH soft fork in 2012, after segwit activates it will not immediately be safe for wallets to upgrade to support segwit. That’s because spends from segwit transactions look like unsecured transactions to older nodes, so if the blockchain is forked soon after segwit activates, those spends could be placed in an earlier block that is not subject to segwit’s rules. For this reason, it is suggested that wallets avoid upgrading for a few weeks after segwit activates. Allowing that extra time to pass provides extra security to wallet users, although anyone who wants to test with a small amount of money they can afford to lose can begin spending as soon as segwit activates. Users can also begin testing immediately using testnet or regtest with the proposed segwit code or (when available) any release containing segwit.