1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <pete@petertodd.org>) id 1VYWj2-0005Sk-Cc
for bitcoin-development@lists.sourceforge.net;
Tue, 22 Oct 2013 07:50:00 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of petertodd.org
designates 62.13.149.113 as permitted sender)
client-ip=62.13.149.113; envelope-from=pete@petertodd.org;
helo=outmail149113.authsmtp.com;
Received: from outmail149113.authsmtp.com ([62.13.149.113])
by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1VYWj0-0006lR-Dp for bitcoin-development@lists.sourceforge.net;
Tue, 22 Oct 2013 07:50:00 +0000
Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235])
by punt5.authsmtp.com (8.14.2/8.14.2) with ESMTP id r9M7nmEo005949;
Tue, 22 Oct 2013 08:49:48 +0100 (BST)
Received: from savin (76-10-178-109.dsl.teksavvy.com [76.10.178.109])
(authenticated bits=128)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id r9M7ngB9081334
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
Tue, 22 Oct 2013 08:49:45 +0100 (BST)
Date: Tue, 22 Oct 2013 03:49:41 -0400
From: Peter Todd <pete@petertodd.org>
To: Martin Sustrik <sustrik@250bpm.com>
Message-ID: <20131022074941.GB3452@savin>
References: <791a727f-2188-4848-bd77-ea733c8c5c2c@me.com>
<201310211947.59640.luke@dashjr.org> <52661DB7.7040805@250bpm.com>
<FAE2A544-9295-4087-96DE-D4602D109CBD@me.com>
<CAAS2fgS2f=gYRSr1n2DzK7CUH3xG3J2JMnDreCKBoCcJcpGLxg@mail.gmail.com>
<52662AA1.5050509@250bpm.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature"; boundary="+pHx0qQiF2pBVqBT"
Content-Disposition: inline
In-Reply-To: <52662AA1.5050509@250bpm.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Server-Quench: 85316818-3aee-11e3-b802-002590a15da7
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
bgdMdAAUF1YAAgsB AmUbW1xeVFR7XWU7 bAxPbAVDY01GQQRq
WVdMSlVNFUsqCGEG WElsWxl6dgZFfDBx bUZnWz5TWUd7c058
SlNXRDhTeGZhPWMC AkhYdR5UcAFPdx8U a1UrBXRDAzANdhES
HhM4ODE3eDlSNilR RRkIIFQOdA4xEyA9 XBEeHDMgVVEFSm0Z
DiQdYkYGG00cKV52 eVJpQUgfKxgJAwk2
X-Authentic-SMTP: 61633532353630.1023:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 76.10.178.109/587
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
X-Spam-Score: -1.5 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_PASS SPF: sender matches SPF record
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: petertodd.org]
X-Headers-End: 1VYWj0-0006lR-Dp
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Revisiting the BIPS process, a proposal
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 22 Oct 2013 07:50:02 -0000
--+pHx0qQiF2pBVqBT
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Oct 22, 2013 at 09:34:57AM +0200, Martin Sustrik wrote:
> On 22/10/13 09:03, Gregory Maxwell wrote:
> > On Mon, Oct 21, 2013 at 11:59 PM, Jean-Paul Kogelman
> > <jeanpaulkogelman@me.com> wrote:
> >> Have you seen: https://en.bitcoin.it/wiki/Protocol_specification ?
> >
> > Take care, the information in the wiki is woefully incomplete.
>=20
> Imagine myself, with no prior knowledge of Bitcoin looking at the=20
> document. It starts with "Hashes". What hashes? No idea what's going on.=
=20
> Etc.
>=20
> Now compare that to a well written RFC. It starts with introduction,=20
> description of the problem, explains the conceptual model of the=20
> solution, then dives into the details. There's also Security=20
> Considerations part in every RFC that is pretty relevant for Bitcoin.
>=20
> As I said, I am willing to help with writing such document, it would be=
=20
> a nice way of learning the stuff, however, help from core devs, such as=
=20
> answering question that may arise in the process, or reviewing the=20
> document would be needed.
Writing such RFCs is dangerous due to the consensus nature of Bitcoin -
it makes people think the standard is the RFC, rather than the code.
I hear one of the better intros to Bitcoin is the Khan academy videos,
but I've never watched them myself. Once you understand how it works,
start reading source code - the Bitcoin codebase is actually really
simple and readable. However remember that the implications of that
codebase are anything but simple; there's lots of reasons to think
Satoshi himself didn't understand Bitcoin all that well, even by the
time he left the project.
--=20
'peter'[:-1]@petertodd.org
000000000000000f155e7a648e84a83589048ae1cacb0c60bfce2437553b6af4
--+pHx0qQiF2pBVqBT
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQGrBAEBCACVBQJSZi4VXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMGNjNzBhZDFjNWRiMWUxMTA5N2I4YWQ4ZGE0NWYwNGU0ZWFj
YTQ5YzlhNGVmNjJkM2EvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkft+ZQf/YDbkhcRO6XJciE4lXRswvK8r
o2Hi9Onlnss3gEdpmizmTSAFzboWtBA4wSs/97777vJGTp5JDR5qbIRgaE2HozJv
OUh8ojcxA1mAmA6jHFjGRWbni1nLeAs8dQ01bTPAg00nJJNsoMhcHmnrpMe18gNF
XcGOpukPPmR0Y/PoUT3E0SGoOeczzwUZqaC6G/OiMWLKADIuSPtBZJRZJ/rU4cEb
CzliRYN2kaI50wDtwOHoYOrAVxNtn9L/l6QouqsDzh6CnRtwXVxwfZHCjEbEGPK/
oq1eZj2ZD8weninyPbuzWiDrEF+nWv+DCLvDLogirpcDofNrU9NbIR2qZ7V1sA==
=kPNV
-----END PGP SIGNATURE-----
--+pHx0qQiF2pBVqBT--
|
