public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Krzysztof Okupski <k.okupski@googlemail.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Bitcoin Protocol Specification
Date: Mon, 14 Jul 2014 16:44:32 +0200	[thread overview]
Message-ID: <53C3ECD0.2000809@googlemail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]

I've renamed it to "Bitcoin Developer Specification" a little while ago.
Maybe it should rather be named "Bitcoin Developer Reference"? Either
way, creating a good description of Bitcoin is an incremental process
and there are certainly many quirks I'm not aware of. I hope that
together we will soon be able to fill in the missing gaps.

Warm greetings,
Krzysztof Okupski

On 07/14/2014 01:26 PM, Mike Hearn wrote:

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

[-- Attachment #2: Type: text/html, Size: 1504 bytes --]

             reply	other threads:[~2014-07-14 14:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14 14:44 Krzysztof Okupski [this message]
2014-07-14 17:16 ` [Bitcoin-development] Bitcoin Protocol Specification Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2014-07-14  9:54 Krzysztof Okupski
2014-07-14 10:41 ` sickpig
2014-07-14 11:26 ` Mike Hearn
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
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=53C3ECD0.2000809@googlemail.com \
    --to=k.okupski@googlemail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    /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