Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update: Bitcoin Improvement Proposals (BIPS) #73

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update: Bitcoin Improvement Proposals (BIPS) #73

wants to merge 1 commit into from

Conversation

KenMan79
Copy link
Contributor

| 👷 | 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. |

| 👷 | 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. |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant