On Tuesday 11 July 2017 8:54:42 PM Lucas Clemente Vella via bitcoin-discuss wrote: > What status does a BIP needs to be in order to be implemented/merged into > Core?
You have it backward. BIP status reflects the reality of the Bitcoin network. So to leave Draft status, they need to be implemented. See BIP 2 for a general overview on the specific criterias each kind of BIP needs to meet. Note that the BIP process is implementation-independent and is not in any sense tied to Bitcoin Core. > BIP-141 is "draft" but was merged into Core release. BIP-148 is "draft", > but I have read in bitcoin-dev list it can't be realistically merged into > Core. BIPs 141 and 148 are softforks, so their status depends on adoption by the network. They should probably be Proposed by now, but in any case, they won't become Final until successful activation. > Of all BIPs that will not be implemented on core, why only one (BIP-109) is > "rejected" on the list? BIP 109 was clearly rejected by the community at large, and its former proponents have also all moved on to other ideas. Luke _______________________________________________ bitcoin-discuss mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-discuss
