From: Doug Huff <dhuff@jrbobdobbs.org>
To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Protocol versioning
Date: Wed, 15 Jun 2011 08:04:06 -0500 [thread overview]
Message-ID: <B13FEBE4-EE87-47F4-AE90-17A6673BF7F2@jrbobdobbs.org> (raw)
In-Reply-To: <BANLkTikCQ8g9bEpf2uosKm1Q_K_SSrh0nQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 638 bytes --]
On Jun 15, 2011, at 7:46 AM, Christian Decker wrote:
> On Wed, Jun 15, 2011 at 8:06 AM, Jeff Garzik <jgarzik@exmulti.com> wrote:
> Here are several mini-proposals for the Satoshi Client (anyone got a
> better nickname?) along these lines, which should better prepare the
> bitcoin protocol for the long term:
> I called it Mainline client (like the original Bittorrent client) as a hint that this is the reference implementation everybody should refer to, but Satoshi Client has a nice sound too :-)
I propose "Reference client." Seeing as that's what it is, the original reference implementation.
--
Douglas Huff
[-- Attachment #2: Type: text/html, Size: 1984 bytes --]
prev parent reply other threads:[~2011-06-15 14:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 6:06 [Bitcoin-development] Protocol versioning Jeff Garzik
2011-06-15 12:46 ` Christian Decker
2011-06-15 13:04 ` Doug Huff [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=B13FEBE4-EE87-47F4-AE90-17A6673BF7F2@jrbobdobbs.org \
--to=dhuff@jrbobdobbs.org \
--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