From: Krzysztof Okupski <k.okupski@googlemail.com>
To: bitcoin-development@lists.sourceforge.net
Subject: [Bitcoin-development] Bitcoin Protocol Specification
Date: Sun, 18 May 2014 15:35:33 +0200 [thread overview]
Message-ID: <5378B725.50400@googlemail.com> (raw)
Dear all,
I'd like to kindly ask, those of you that have a bit of spare time, to
take a look at a Bitcoin protocol specification I've written. It is still
in development and, as some of you have already indicated, needs
improvement. I'd be very thankful if some of you could take the
time to review it. If there are any errors or suggestions from your
side, I'd gladly hear them. My e-mail can be found on the front page
of the document:
http://enetium.com/resources/Bitcoin.pdf
Warm greetings,
Chris
next reply other threads:[~2014-05-18 13:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-18 13:35 Krzysztof Okupski [this message]
2014-05-18 14:38 ` [Bitcoin-development] Bitcoin Protocol Specification Adam Back
2014-05-20 17:48 ` [Bitcoin-development] good bitcoin summary paper in more detail than Satoshi paper (Re: Bitcoin Protocol Specification) Adam Back
2014-06-26 11:30 [Bitcoin-development] Bitcoin Protocol Specification 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-07-09 9:34 Krzysztof Okupski
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-14 14:44 Krzysztof Okupski
2014-07-14 17:16 ` Jeff Garzik
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=5378B725.50400@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