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.

Sign up for GitHub

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

Dev Docs: "Not A Specification" #679

Merged
merged 3 commits into from
Dec 19, 2014
Merged

Dev Docs: "Not A Specification" #679

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8f0a80a
Dev Docs: "Not A Specification"
harding Dec 12, 2014
f08b3e1
Dev Docs: Remove Majority Mentions In Not A Spec (thanks saivann)
harding Dec 13, 2014
82f00e8
Dev Docs: Add Subhead-Links To "Not A Spec" Subsection
harding Dec 16, 2014
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Dev Docs: Remove Majority Mentions In Not A Spec (thanks saivann)
  • Loading branch information
@harding
harding committed Dec 16, 2014
commit f08b3e1bb4f28c6609734e83a806386065b15c9c
6 changes: 3 additions & 3 deletions _includes/ref_intro.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,13 +38,13 @@ Bitcoin security depends on consensus. Should your program diverge from
consensus, its security is weakened or destroyed. The cause of the
divergence doesn't matter: it could be a bug in your program, it could
be an [error in this documentation][errors in docs] which you
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@harding Unless you stop being incredibly responsive as you currently are, I think this link will usually point to an empty list :)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, old issues should show up in that link. I'll go through and tag some/all of the old dev docs issues so it's clear to people that we (mostly me) make plenty of mistakes.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, makes sense!

implemented as described, or it could be you do everything right but the
majority software on the network [behaves unexpectedly][v0.8 chain
implemented as described, or it could be you do everything right but
other software on the network [behaves unexpectedly][v0.8 chain
fork]. The specific cause will not matter to the users of your software
whose wealth is lost.

The only correct specification of consensus behavior is the actual
program behavior of the majority software on the network. As that
behavior of programs on the network which maintain consensus. As that
behavior is subject to arbitrary inputs<!--noref--> in a large variety
of unique environments, it cannot ever be fully documented here or
anywhere else.
Expand Down