@@ -159,7 +159,7 @@ appear in the following order. Headers marked with "\*" are optional. All other
159
159
* Version — The current version number of this BIP. See the [ Changelog] ( #changelog ) section below.
160
160
* Requires — A list of existing BIPs the new proposal depends on. If multiple BIPs
161
161
are required, they should be listed in one line separated by a comma and space (e.g., "1, 2").
162
- * Replaces — BIP authors may place the numbers of one or more prior BIPs in the Replaces header to recommend that their
162
+ * Replaces[ ^ proposes-to-replace ] — BIP authors may put the numbers of one or more prior BIPs in the Replaces header to recommend that their
163
163
BIP succeeds, supersedes, or renders obsolete those prior BIPs.
164
164
* Proposed-Replacement[ ^ superseded-by-proposed-replacement ] — When a later BIP indicates that it intends to supersede an
165
165
existing BIP, the later BIP’s number is added to the Proposed-Replacement header of the existing BIP to indicate the
@@ -704,6 +704,16 @@ feedback, and helpful comments.
704
704
the original BIP, the authors of the new BIP, the editors, or the community? This is addressed by making the
705
705
"Replaces" header part of the recommendation of the authors of the new document, and replacing the "Superseded-By"
706
706
header with the "Proposed-Replacement" header that lists any proposals that recommend replacing the original document.
707
+ [ ^ proposes-to-replace ] : ** Why was "Replaces" retained instead of changing it to "Proposes-to-Replace"?**
708
+ When one BIP proposes to supersede another, it is on the original BIP where things get complicated. The BIP is an
709
+ author document, but depending on its progress through the workflow, it may meanwhile be co-owned by the community. Who may decide
710
+ whether the original document should endorse a potential replacement BIP? Is it the original authors, the authors of the new
711
+ proposal, the BIP Editors, some sort of community process, or a mix of all of the above?
712
+ On the new BIP these problems don’t exist in the same manner. As it is freshly written, it is wholly owned by its
713
+ authors. The community is not yet invested and the original BIP’s authors do not have a privileged role
714
+ in determining the content of the new BIP. The authors of the new BIP can unilaterally recommend that it be
715
+ considered a replacement for a prior BIP. From there, the community can evaluate the proposal and adopt or
716
+ reject it, thus establishing whether it is successful in superseding the original or not.
707
717
[ ^ evidence ] : ** How is evidence for advancing to Deployed evaluated?**
708
718
Whether evidence is deemed convincing to move a BIP to Deployed is up to the BIP Editors and Bitcoin community.
709
719
Running a single instance of a personal fork of a software project might be rejected, while a small software project with
0 commit comments