I will expound upon this later, but I support this proposal. Primarily because it includes BIP148 UASF, secondarily because it includes a 2mB blocksize increase, which I support in principle (I am a big blocker but opposed to divergent consensus.)
AbstractThis document describes a virtuous combination of James Hilliard’s “Reduced signalling threshold activation of existing segwit deployment”, Shaolin Fry’s “Mandatory activation of segwit deployment”, Sergio Demian Lerner’s “Segwit2Mb” proposal, Luke Dashjr’s “Post-segwit 2 MB block size hardfork”, and hard fork safety mechanisms from Johnson Lau’s “Spoonnet” into a single omnibus proposal and patchset.
The string “COOP” is included anywhere in the txn-input (scriptSig) of the coinbase-txn to signal compatibility and support.
Fast-activation (segsignal): deployed by a "version bits" with an 80% activation threshold BIP9 with the name "segsignal" and using bit 4... [with a] start time of midnight June 1st, 2017 (epoch time 1496275200) and timeout on midnight November 15th 2017 (epoch time 1510704000). This BIP will cease to be active when segwit is locked-in.
Flag-day activation (BIP148): While this BIP is active, all blocks must set the nVersion header top 3 bits to 001 together with bit field (1<<1) (according to the existing segwit deployment). Blocks that do not signal as required will be rejected... This BIP will be active between midnight August 1st 2017 (epoch time 1501545600) and midnight November 15th 2017 (epoch time 1510704000) if the existing segwit deployment is not locked-in or activated before epoch time 1501545600. This BIP will cease to be active when segwit is locked-in. While this BIP is active, all blocks must set the nVersion header top 3 bits to 001 together with bit field (1<<1) (according to the existing segwit deployment). Blocks that do not signal as required will be rejected.
The hard fork deployment is scheduled to occur 6 months after SegWit activates:
(HardForkHeight = SEGWIT_ACTIVE_BLOCK_HEIGHT + 26280)
For blocks equal to or higher than HardForkHeight, Luke-Jr’s legacy witness discount and 2MB limit are enacted, along with the following Spoonnet-based improvements:
- A "hardfork signalling block" is a block with the sign bit of header nVersion is set [Clearly invalid for old nodes; easy opt-out for light wallets]
- If the median-time-past of the past 11 blocks is smaller than the HardForkHeight... a hardfork signalling block is invalid.
- Child of a hardfork signalling block MUST also be a hardfork signalling block
- Hardfork network version bit is 0x02000000. A tx is invalid if the highest nVersion byte is not zero, and the network version bit is not set.
DeploymentDeployment of the “fast-activation” soft fork is exactly identical to Hilliard’s segsignal proposal. Deployment of the “flag-day” soft fork is exactly identical to Fry’s BIP148 proposal. HardForkHeight is defined as 26280 blocks after SegWit is set to ACTIVE. All blocks with height greater than or equal to this value must adhere to the consensus rules of the 2MB hard fork.
Backwards compatibilityThis deployment is compatible with the existing "segwit" bit 1 deployment scheduled between midnight November 15th, 2016 and midnight November 15th, 2017.
To prevent the risk of building on top of invalid blocks, miners should upgrade their nodes to support segsignal as well as BIP148.
The intent of this proposal is to maintain full legacy consensus compatibility for users up until the HardForkHeight block height, after which backwards compatibility is waived as enforcement of the hard fork consensus ruleset begins.
The goal here is to minimize chain split risk and network disruption while maximizing backwards compatibility and still providing for rapid activation of segwit at the 80% threshold using bit 4.Shaolin Fry’s “Mandatory activation of segwit deployment” is included to:
cause the existing "segwit" deployment to activate without needing to release a new deployment.Both of the aforementioned activation options (“fast-activation” and “flag-day activation”) serve to prevent unnecessary delays in the network upgrade process, addressing a common criticism of the Scaling Agreement and providing an opportunity for cooperation and unity instead.
Segwit2Mb combines segwit as it is today in Bitcoin 0.14+ with a 2MB block size hard-fork activated ONLY if segwit activates (95% of miners signaling ... to re-unite the Bitcoin community and avoid a cryptocurrency split.Luke Dashjr’s “Post-segwit 2 MB block size hardfork” suggestions are included to reduce the marginal risks that such an increase in the block size might introduce:
if the community wishes to adopt (by unanimous consensus) a 2 MB block size hardfork, this is probably the best way to do it right now... Legacy Bitcoin transactions are given the witness discount, and a block size limit of 2 MB is imposed.Johnson Lau’s anti-replay and network version updates are included as general hard fork safety measures:
In a blockchain split, however, since both forks share the same historical ledger, replay attack would be possible, unless some precautions are taken.===Copyright===
James Hilliard’s “Reduced signalling threshold activation of existing segwit deployment” explains: The goal here is to minimize chain split risk and network disruption while maximizing backwards compatibility and still providing for rapid activation of segwit at the 80% threshold using bit 4. “Die Version 0.14 bietet eine Menge Verbesserungen, neben neuen netzwerkseitigen Funktionalitäten, an”, sagte Hilliard. Weiterhin gab es eine Überarbeitung des Codes durch Bitcoin-Entwickler Cory Fields in 0.14.0. Die Arbeit fand nach fast 2 Jahren ein Ende. In Zukunft sollen durch die Überarbeitungen die neuen Entwickler schneller in ... The latter is when Segwit activation is “all in the clear,” as BIP 91 creator James Hilliard said. That’s when bitcoin’s SegWit upgrade will be official, and an upcoming user-activated soft fork (UASF) proposal, BIP 148, superseded. Now, what the possible setbacks may be. However, some members of the community, including respected bitcoin developers and mining pool operators, are ... Check out all of our speakers for Bitcoin 2020! Bitcoin 2020 is coming back to San Francisco, this time with more attendees, more fun and more Bitcoin. Register for Bitcoin 2020 today! Follow @bitcoin2020conf on Twitter for updates. Bitcoin Core contributors James Hilliard and Greg Maxwell mostly agreed with Themyos’ points. More Bitcoin application and service developers should spend more of their resources on testing Bitcoin Core and its code. The less companies are willing to do research on the code, the less Bitcoin community can profit from the open nature of Bitcoin code. Though the bug was soon fixed, it could ...
[index]          
MASSIVE BITCOIN DUMP COULD BE HAPPENING TOMORROW THE NEXT PRICE WILL SHOCK YOU!! ... Take everything I say as pure entertainment value only. Do not take any financial advice from me at all. I am ... 2018 for bitcoin wasn’t something we expected, but there is the reason why it happened what it happened. Bitcoin was in the bubble in 2017, it skyrocketed by 1,800% reaching its all time high ... In this interview, I talk to Richard James, the creator of Hard Money, a film looking at how money has been corrupted and co-opted. We discuss Austrian economics, the similarities between gold and ... bitcoin is forming the largest bull flag in history but it doesn't mean what you think (price news) - duration: 33:43. Crypto Crew University 40,580 views 33:43 How Much Money Will You Make Bitcoin Mining BITCOIN PRICE , BITCOIN FUTURE in doubt http://youtu.be/eO-yrpQpIT8 What is NAMECOIN BITCOIN'S First Fork http://...