From: Mike Hearn <mike@plan99.net>
To: Krzysztof Okupski <k.okupski@googlemail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin Protocol Specification
Date: Mon, 14 Jul 2014 13:26:19 +0200 [thread overview]
Message-ID: <CANEZrP21sc9smev5tg07HnLpw-8WWS7EvzzTyEvD6qYEfHvpoA@mail.gmail.com> (raw)
In-Reply-To: <53C3A8C0.5070608@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 1630 bytes --]
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.
On Mon, Jul 14, 2014 at 11:54 AM, Krzysztof Okupski <
k.okupski@googlemail.com> wrote:
> Dear all,
>
> thank you for your invaluable feedback. As requested, the spec
> will from now on be under version control. It can be found under:
>
> https://github.com/minium/Bitcoin-Spec
>
> The old link to the PDF will be, just in case, kept updated as well.
>
>
> Warm greetings,
> Krzysztof Okupski
>
>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck®
> Code Sight™ - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
[-- Attachment #2: Type: text/html, Size: 2470 bytes --]
next prev parent reply other threads:[~2014-07-14 11:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 9:54 [Bitcoin-development] Bitcoin Protocol Specification Krzysztof Okupski
2014-07-14 10:41 ` sickpig
2014-07-14 11:26 ` Mike Hearn [this message]
2014-07-14 11:41 ` Wladimir
2014-07-14 11:49 ` Mike Hearn
2014-07-14 12:25 ` sickpig
2014-07-14 12:37 ` Mike Hearn
2014-07-14 20:51 ` sickpig
-- strict thread matches above, loose matches on Subject: below --
2014-07-14 14:44 Krzysztof Okupski
2014-07-14 17:16 ` Jeff Garzik
2014-07-09 9:34 Krzysztof Okupski
2014-06-26 11:30 Krzysztof Okupski
2014-07-03 1:21 ` Isidor Zeuner
[not found] ` <CANVdSAqEyqavSHea3uhzVWGKQU0UHGZDVqEiF3Ox2XkhwM=zpA@mail.gmail.com>
2014-07-07 17:57 ` JMOlmos GMail
2014-07-08 15:29 ` Chris D'Costa
2014-07-08 20:04 ` Matt Whitlock
2014-07-08 21:08 ` Aaron Voisine
2014-07-08 22:40 ` Jorge Timón
2014-07-09 11:57 ` Mike Hearn
2014-05-18 13:35 Krzysztof Okupski
2014-05-18 14:38 ` Adam Back
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=CANEZrP21sc9smev5tg07HnLpw-8WWS7EvzzTyEvD6qYEfHvpoA@mail.gmail.com \
--to=mike@plan99.net \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=k.okupski@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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