Update: Bitcoin Improvement Proposals (BIPS) #73
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
| 👷 | Bitcoin Improvement Proposals (BIPS) | The BIP process was developed and introduced by early Bitcoin developer Amir Taaki who believed that the Bitcoin development process would benefit from becoming more structured and accountable.
Taaki submitted the first BIP (BIP 0001) on August 19, 2011, which described the BIP process. A Bitcoin Improvement Proposal (BIP) is a standard for proposing changes to the Bitcoin protocol or source for information for the Bitcoin community. It can also include changes like soft, and hard fork protocol upgrades as well as other changes that benefit from coordination across different Bitcoin software implementations, such as to the peer-to-peer layer or new backup seed formats. Not all changes to a Bitcoin software implementation affect the Bitcoin protocol some changes however make the code run more efficient or change the user interface, and these changes do not require a BIP. |