From: Ron <rdwnj@yahoo•com>
To: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] "Bitcoin Protocol Guide"
Date: Mon, 14 Jul 2014 20:34:42 -0700 [thread overview]
Message-ID: <1405395282.75933.YahooMailNeo@web164501.mail.gq1.yahoo.com> (raw)
In-Reply-To: <mailman.253891.1405338074.2207.bitcoin-development@lists.sourceforge.net>
[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]
________________________________
Message: 6
Date: Mon, 14 Jul 2014 13:26:19 +0200
From: Mike Hearn <mike@plan99•net>
Subject: Re: [Bitcoin-development] Bitcoin Protocol Specification
To: Krzysztof Okupski <k.okupski@googlemail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Message-ID:
<CANEZrP21sc9smev5tg07HnLpw-8WWS7EvzzTyEvD6qYEfHvpoA@mail•gmail.com>
Content-Type: text/plain; charset="utf-8"
Nice work, but please don't call it the "Bitcoin protocol spec". Your
document is not a spec. It is an attempt to describe in English the Bitcoin
protocol, but anyone who implemented it based on your description would get
it wrong. For example you didn't mention the SIGHASH_SINGLE bug and many
other important areas like the difficulty transitions are also left
unspecified.
As a loose description of the protocol for newbies it's an invaluable
resource and perhaps we should link to it from the developer guide. As
something that claims to be a specification it is quite possibly dangerous
- the only spec that matters is the C++ original.
...
Hello Mike,
What C++ original might that be? Version 0.1.0? 0.9.x? 0.8.6? And what parts of which version?
Ron
[-- Attachment #2: Type: text/html, Size: 2347 bytes --]
parent reply other threads:[~2014-07-15 3:37 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <mailman.253891.1405338074.2207.bitcoin-development@lists.sourceforge.net>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1405395282.75933.YahooMailNeo@web164501.mail.gq1.yahoo.com \
--to=rdwnj@yahoo$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox