From: Adam Back <adam@cypherspace.org>
To: Krzysztof Okupski <k.okupski@googlemail.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: [Bitcoin-development] good bitcoin summary paper in more detail than Satoshi paper (Re: Bitcoin Protocol Specification)
Date: Tue, 20 May 2014 19:48:38 +0200 [thread overview]
Message-ID: <20140520174838.GA12364@netbook.cypherspace.org> (raw)
In-Reply-To: <20140518143853.GA12783@netbook.cypherspace.org>
Actually I read the paper now as it was linked somewhere else also, and its
quite good. So now I can summarize it:
Its a writeup of bitcoin in 29 pages, which covers things in the original
bitcoin paper but with more detail of formats, scripts with some examples,
formats etc. Quite nice paper, concise presentation of many bitcoin details
that are otherwise hard to put together, requiring examining source or
asking people knowledgeable at algorithm/code level.
>>http://enetium.com/resources/Bitcoin.pdf
Adam
On Sun, May 18, 2014 at 04:38:53PM +0200, Adam Back wrote:
>Suggestion: maybe you want to write and post here a paragraph summarizing
>the topic of your paper so people can know if they feel qualified and if
>they need to review it from their interests.
>
>Adam
>
>On Sun, May 18, 2014 at 03:35:33PM +0200, Krzysztof Okupski wrote:
>>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
>>
>>
>>------------------------------------------------------------------------------
>>"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
>>Instantly run your Selenium tests across 300+ browser/OS combos.
>>Get unparalleled scalability from the best Selenium testing platform available
>>Simple to use. Nothing to install. Get started now for free."
>>http://p.sf.net/sfu/SauceLabs
>>_______________________________________________
>>Bitcoin-development mailing list
>>Bitcoin-development@lists.sourceforge.net
>>https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>------------------------------------------------------------------------------
>"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
>Instantly run your Selenium tests across 300+ browser/OS combos.
>Get unparalleled scalability from the best Selenium testing platform available
>Simple to use. Nothing to install. Get started now for free."
>http://p.sf.net/sfu/SauceLabs
>_______________________________________________
>Bitcoin-development mailing list
>Bitcoin-development@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bitcoin-development
prev parent reply other threads:[~2014-05-20 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-18 13:35 [Bitcoin-development] Bitcoin Protocol Specification Krzysztof Okupski
2014-05-18 14:38 ` Adam Back
2014-05-20 17:48 ` Adam Back [this message]
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=20140520174838.GA12364@netbook.cypherspace.org \
--to=adam@cypherspace.org \
--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