From f08b3e1bb4f28c6609734e83a806386065b15c9c Mon Sep 17 00:00:00 2001 From: "David A. Harding" Date: Fri, 12 Dec 2014 19:34:24 -0500 Subject: [PATCH] Dev Docs: Remove Majority Mentions In Not A Spec (thanks saivann) --- _includes/ref_intro.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/_includes/ref_intro.md b/_includes/ref_intro.md index 16cbc8ae..baead203 100644 --- a/_includes/ref_intro.md +++ b/_includes/ref_intro.md @@ -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 -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 in a large variety of unique environments, it cannot ever be fully documented here or anywhere else.