From: Isidor Zeuner <cryptocurrencies@quidecco•de>
To: Krzysztof Okupski <k.okupski@googlemail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Bitcoin Protocol Specification
Date: Thu, 3 Jul 2014 03:21:31 +0200 (CEST) [thread overview]
Message-ID: <20140703012131.1A3D9E00A82@quidecco.de> (raw)
In-Reply-To: <53AC0439.9070501@googlemail.com>
Hello Krzysztof,
[...]
> As before, it can be found under:
>
> http://enetium.com/resources/Bitcoin.pdf
>
> I hope it will prove useful to the community and thank in advance
> for any further improvement proposals.
>
I think it's great work and provides a good reference for those
who want to get some insight into Bitcoin's design.
Have you considered putting the document source under version control,
which may facilitate tracking future protocol improvements in the
document easily?
Best regards,
Isidor
next prev parent reply other threads:[~2014-07-03 1:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 11:30 Krzysztof Okupski
2014-07-03 1:21 ` Isidor Zeuner [this message]
[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
-- 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-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-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=20140703012131.1A3D9E00A82@quidecco.de \
--to=cryptocurrencies@quidecco$(echo .)de \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=k.okupski@googlemail$(echo .)com \
/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