summaryrefslogtreecommitdiff
path: root/eb/7f64db60bac37137484c75c03a8dd25b96209a
blob: 759736f12d70256d40564375579b9b1ed16e9d41 (plain)
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
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
Return-Path: <vitteaymeric@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id CF546BAA
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 18 Feb 2019 23:50:30 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wm1-f47.google.com (mail-wm1-f47.google.com
	[209.85.128.47])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 9111FF8
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 18 Feb 2019 23:50:28 +0000 (UTC)
Received: by mail-wm1-f47.google.com with SMTP id z84so731328wmg.4
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 18 Feb 2019 15:50:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=subject:to:cc:references:from:openpgp:autocrypt:message-id:date
	:user-agent:mime-version:in-reply-to:content-language;
	bh=2tRAzy4RV+5g3W43VCeqV6TzAOwxyRhJ97LwtkVutlY=;
	b=LRyOAiSAWy+RodQF71CwPFtF8PPgQ0EbR+uQC5mZoUcLIp8SgtkMipo9LZiy7lLfcz
	YM5GgizZj09+A1xYo/7dgzA3ymS2Io85G9Mm8Ii4JRGfYN6vC1BRhCEYE2I3sc+43Dnh
	7NZLUUg9DGSLGhG6h4JinHofqonPHD+mjiNV6AlxlwQB5WKblxcVe6gCTIZQ6esGVsTF
	igORmw37Vsz9J6vaLXjlwZ+cjOL11EWHvy17z9t8YY/ZxyahtsNTbdlWYOl6PYD0mtu8
	csrP0kgguKkY1kKQps+3u9g1PHur7r6ogBYVEhlb2xUsEMmRQrK1TLi9Jn0HQ+4TzEw5
	uU9w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:subject:to:cc:references:from:openpgp:autocrypt
	:message-id:date:user-agent:mime-version:in-reply-to
	:content-language;
	bh=2tRAzy4RV+5g3W43VCeqV6TzAOwxyRhJ97LwtkVutlY=;
	b=c7rPyKdigsbV2r4oLX6mPkE4oKlwyS85+pDD1tpRADSImZ2ozJvhpdyobv5UXPj/rX
	7ZiwMRPPVyQ/eTV/3CzD16uY1+LdjRCwNN8MiZmPpYaM0Q06JEbp/H26HCIsEFgzGiK8
	4ZH4qXbO1PMJFtTHS1y9dhDqz8Q4D6MS0MGVNSpEyDEclWiNw62hbSAq8pkCM8I/cRZ/
	HkMBGKL/9gmeIwCkTm40kqnBU21MN3767VAJsWVazEt+9d0H41PClhf6gjcq0ag2tBOy
	WZmjVN7qME5465dYG3+IZFep+kR2HzEnGtsuFAXFN37UHMO7EHksNEGhogyvMxSTLyZb
	GodQ==
X-Gm-Message-State: AHQUAuYpe+L+BYWnGjxaTSttRE7+koeh9dm6sMZfG697QYCjwBmAfOpM
	jVyj/MhYaRaRaUL+GUO/RsSn+MC1
X-Google-Smtp-Source: AHgI3IZ+vsE15j4BNRte1aGXt1uFH0M83xyxsJEosa/LxO8q5jglbZjuU7LNLR3Yn/5s3xAfHDyT8Q==
X-Received: by 2002:a1c:2348:: with SMTP id j69mr708604wmj.100.1550533826861; 
	Mon, 18 Feb 2019 15:50:26 -0800 (PST)
Received: from ?IPv6:2a01:cb1d:44:6500:5ca3:78e9:912d:df78?
	([2a01:cb1d:44:6500:5ca3:78e9:912d:df78])
	by smtp.googlemail.com with ESMTPSA id
	w22sm958935wmc.9.2019.02.18.15.50.25
	(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
	Mon, 18 Feb 2019 15:50:26 -0800 (PST)
To: Christopher Gilliard <christopher.gilliard@gmail.com>
References: <CAK=nyAxXS6rQowFC6ENto+d+D9FzSf5WJLz-WM_vc2D5DQ2xQQ@mail.gmail.com>
	<5c7fac0f-818b-d78d-5d5f-7a029fdd05ef@gmail.com>
	<CAK=nyAztSeEbDL=98PTdx-sdqGOug26-3vyADA-tc5oxECyZPw@mail.gmail.com>
From: Aymeric Vitte <vitteaymeric@gmail.com>
Openpgp: preference=signencrypt
Autocrypt: addr=vitteaymeric@gmail.com; prefer-encrypt=mutual; keydata=
	mQINBFdW8uABEAC7HJScbB2d/lmYoY5Cn9loEjJwfLs1LC3om030bWFGiH3Ceo5XeHUT94rw
	Pi+HaHU8ea94425SXIFsnqp/ouoT/8Ffn6vED0OoRmK0jE4fqDApXSpoL2mHX9PAGdUItMtD
	YrxBiBZNfMkctEsm4NrQ4TCvB3Yrm6Fc69inXJjUoYgPw5tHafEeI8Qwh0j99JZZDKcAqIra
	JF3MPc59rATz0qOJtRP9EpsPVFwjJe13zN6CHILwiVgrL8EtT5WKCVO6ATxh60LHi8+MwPxV
	V31zp/NNI5Hck+XocEMO98ZvUu9X8ZxmnOk/+9pBxXEwUqSGUNWdmPJLncpI23Usce3u/MOo
	M2C4T4rD4J0XrXiyBvbeTvwq4qVNlyggeWzlBH+YpEYgDctPq4gNh4eoTtAkf8URtBeke5bQ
	CGdaZt/jxv8nvmxs9V/iSyg5ldJLQktHStXOo0OZ7FEB2C6Ggtymm4hm2MHYg07Q1MGJrFLa
	oJZkJ3JeXnVsZMam7ypQtld6rRa96CvH+llXwux6aQ5hKdzmBBMQ10LlkZhkExgTawbeqdiG
	RMP2DjD5go6TPdAHS4NN34SBkrTWLqgWOjN/lnG77bbLnpMl0P+xBTuqw1oSXaDbcdHE2nGY
	lRno/ZZIfr+1Bq56DZLBX/WpnAT4f5WtofL4CxQM9SbG6byyewARAQABtCJBeW1lcmljIFZp
	dHRlIDxheW1lcmljQHBlZXJzbS5jb20+iQI/BBMBCAApBQJXVvLgAhsjBQkJZgGABwsJCAcD
	AgEGFQgCCQoLBBYCAwECHgECF4AACgkQKh17NCYnrDm3WhAAlYmgtSmtfqjBvQMqkmtqiQJA
	aZkzFZWt6+zroduHH5/Tp8jh73gFqCUyRrl/kcKvs2+XQhfrOwk1R6OScF25bpnrZSeuyJnZ
	MZu4T0P2tGS8YdddQvWUHMtI9ZnQRuYmuZT23/hgj1JnukuGvGLeY0yDUa1xFffPN39shp5X
	FPMcpIVOV3bs+xjAdsyfRyO3qJAD1FGiR7ggJeoaxUbKZ6NtcVUPPRMjVTKfopkuDwKY318m
	BE0epfxSZ/iRhsJ0/sREUWgbgq4/QvCFwBKzgz7fTikGmf8OELWSdofmXs7gOtmMc3el8fJu
	W8PVa/OsIQHDmwSzvxmE8ba5M8bdwOYEraTWFArIymAAtRXKxmuYpkqKfeSlbCwae3W+pgNT
	8nKYRVAFlMtIxYkmPYyMTk9kCscmSqugGWbWdnqe/dhVaa31xa1qO1tDH24D2/tjCJRQt4Jk
	AEWNSmjCmjfeArMEFTGlZwMTAjVXErLSPbLOsZiZhD9sjvSbfzrtJiMli2h9+Dvds+AJk1PM
	O8LW7cCNyFoCk4OdAxzJHobZ25G+uy4NSQEHgxLC2iuh/tugz1tOHnQczPc/3AkVVI9A5DF1
	gbVRBJh6rI7sAcwuR76uoOs0Rpp7r6I66xqU/5eq8g1OsJp89tw0ppSIa0YmaxNqQZ0l3rVX
	o/ZwpBjtNQS5Ag0EV1by4AEQANhlz3Ywff4dY1HTdn05v0wVUxZzW2PUih+96m6EhpUrD9BT
	vxriKtbgxm/zl+5YAlThbrk9f0QyVTHJ95Z1/M5qjuksP9Zn3qZ/8ylANDkN2s3z8Bq/LJA+
	u7+APhMqyFWK0FqNCOogClvijiKPEzkU6tmDGO6wZ5pR/u8Fdq7DGQgwgyGZZc7qstte0M7l
	yx7bVRlPBqvd6kyX3YubQHzkctf46nFjiYZgKawdWFsA3PCdSBupbhixL5d/t1UK9ZTiQJcf
	0uhHzT06qwolFrm/ugkLDHtE4Zo3BuKch47Sms8P2hJ08gABxeJHg0ZgkIUy/Xf4nHbDCBJw
	T8tE8pWYWA2ECiPNo0TOCMVOueEzISUNKINfCuFHSbMQU39hgt3ofxODbAjOiO3e/iu1ptck
	AkuVBdtjOBP4tHRGxVrbf5EuAV5U5xtiSxMwMgojg0GIXZjnT/8uvWqcLqtJILRMmmu+WNvD
	oxuiJzcTJhDai9oujmxQwcpMvgrBB89KSTDyitO5XVjZqaR7Zxvvn3rM4bAms/lotv9+pTyh
	spazTIxb80u0ifJ6y1RxAkxQCfWwps1i3VbsM6OKX78aUyOf5V4ihXF57M37tOqPRwFvz6a+
	AIIhUNMTLo2H+o6Vw9qbX8SUxPHPs6YpJ8lWQJ9OMWHE+SbaDFAi/D5hYRubABEBAAGJAiUE
	GAEIAA8FAldW8uACGwwFCQlmAYAACgkQKh17NCYnrDmk4Q/9Fuu0h5HvIiO3ieYA2StdE7hO
	vv2THuesjJDsj6aQUTgknaxKptJogNe3dDyIT+FHxXmCw0Nrbm9Q3ryl80z/G9utfFNO3Gwc
	q31QW3n3LJHnpqdrV3WsRzT5NwJMVtiIAGRrX8ZomtarWHT0PeEHC2xBdFzRrJtmkrwer0Wc
	0nBzD7vk1XEXC9nODbmlgsesoHFgRwQBst3wClCbX1gv8aSfxQNpaf9UBC8DmyrQ621UXpBo
	PvcFEtWxV44vJfP0WOLCCN0Pzv2F2I66iKo7VMqbr5jlNAXJN9I1hXb7qwYJmBC9j5oeEoqv
	A9d44WWpxrdAr8qih4Nv89k9+9F6NoqORY3FGuVDKiW8CVhCmGT7bIvNeyicVBZFipXqPcKL
	VFduO2c5Ubc2npMWLUF1k9JJc9tH75l3+F/0RbYVTzGAZ+zSaudwR6h8YiCN2DBZGZkJEZbh
	3X/l6jtijMN/W9sPHyyKvm/TmeEC27S3TqZPZ8PUQLxZC70V6gMbenh01JdSQsn5t8Ru0RNh
	Blt0g7IyZyIKCE9b+TyzbYpX6qgqEBUHia5b0vyPtQacWQlZ8uqnghAqNkLluEsy7Q/7xG6M
	wXUYEDsFOmB9dKOzcAOIhpxlVjSKu5mzXJ11sEtE8nyF5NJ/riCA7FGcjlki3zIpzQUNo9v7
	vXl2h6Tivlk=
Message-ID: <4cfebb7d-42b3-0095-f3ac-dacfff29084d@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.3; rv:60.0) Gecko/20100101
	Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <CAK=nyAztSeEbDL=98PTdx-sdqGOug26-3vyADA-tc5oxECyZPw@mail.gmail.com>
Content-Type: multipart/alternative;
	boundary="------------9D8C40B9B186698EE4BB1A33"
Content-Language: fr
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
	RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
X-Mailman-Approved-At: Wed, 06 Mar 2019 00:22:07 +0000
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP proposal - Signatures of Messages using
 Bitcoin Private Keys
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
Date: Mon, 18 Feb 2019 23:50:30 -0000
X-Original-Date: Tue, 19 Feb 2019 00:50:27 +0100
X-List-Received-Date: Mon, 18 Feb 2019 23:50:30 -0000

This is a multi-part message in MIME format.
--------------9D8C40B9B186698EE4BB1A33
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

Ah, OK, that's of course a good thing to document this undocumented (and
strange) stuff, as a matter of fact I implemented it after reading your
post (because this was on my todo list since some time) and got annoyed
quickly, mainly by what is doing formatMessageForSigning (which is quite
trivial when you know it but would be good to document precisely)

So, yes, it's a good idea to write this, regarding the header I still
don't see the use, testing the different possibilities is not a big
deal, why the signature format is not the same as transactions one is
mysterious too

Le 19/02/2019 à 00:24, Christopher Gilliard a écrit :
> The proposal includes actual code that does verification, but I didn't
> include code for signing. I thought it could be inferred, but I could
> at least include a description of how to sign. I am not sure exactly
> what part you are referring to by "keys speech", but the signatures
> are done by ECDSA keys so it's hard to not include anything about keys
> even though that's not the main topic. The "Background on ECDSA keys"
> section was mainly meant to give background about what kind of keys
> Bitcoin uses, for people who already know that they can easily skip
> this section so I would probably think it's best just to leave in. 
> Maybe it should be at the end as an addendum though. Yes, I did not
> invent any of this, I'm just documenting what people actually seem to
> do because I had to verify signatures as part of a project I'm working
> on. I would have liked to have had this document when I started the
> project so I thought it might be useful to others since as far as I
> can tell this was not specified anywhere. The reason for including
> this data in the header is the same that compressed/uncompressed is
> included in the header so that you know which type of key the
> signature is from and you don't have to try all options to see if any
> matches. This is why Trezor did that way and why I documented it. I'm
> sure there are other ways to do this, but since this is out there in
> the field being used and is a reasonable solution, I thought I'd write
> it up.
>
> On Mon, Feb 18, 2019 at 2:59 PM Aymeric Vitte <vitteaymeric@gmail.com
> <mailto:vitteaymeric@gmail.com>> wrote:
>
>     Then, since you wrote this proposal, maybe you should add the very
>     precise description of the signing/verification process since it
>     is documented nowhere
>
>     I don't get the use of the speech regarding keys while it should
>     focus on signatures which are summarized in a vague sentence
>     inspired by your ref [2] with a not very logical link to the next
>     paragraph stating that r,s should be 32B and the whole thing 65B
>     with a header of 1B, you did not invent it, that's probably the
>     rule, not sure where it is specified again and for what purpose,
>     the header seems completely of no use especially when you extend
>     to segwit/bech32 since you just have to check that related
>     compressed key matches
>
>     Le 17/02/2019 à 15:14, Christopher Gilliard via bitcoin-dev a écrit :
>>     I have written up a proposed BIP. It has to do with Signature
>>     formats when using Bitcoin Private keys. It is
>>     here: https://github.com/cgilliard/BIP/blob/master/README.md
>>
>>     This BIP was written up as suggested in this github
>>     issue: https://github.com/bitcoin/bitcoin/issues/10542
>>
>>     Note that the proposal is inline with the implementation that
>>     Trezor implemented in the above issue.
>>
>>     Any feedback would be appreciated. Please let me know what the
>>     steps are with regards to getting a BIP number assigned or any
>>     other process steps required.
>>
>>     Regards,
>>     Chris
>>
>>     _______________________________________________
>>     bitcoin-dev mailing list
>>     bitcoin-dev@lists.linuxfoundation.org <mailto:bitcoin-dev@lists.linuxfoundation.org>
>>     https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>     -- 
>     Move your coins by yourself (browser version): https://peersm.com/wallet
>     Bitcoin transactions made simple: https://github.com/Ayms/bitcoin-transactions
>     Zcash wallets made simple: https://github.com/Ayms/zcash-wallets
>     Bitcoin wallets made simple: https://github.com/Ayms/bitcoin-wallets
>     Get the torrent dynamic blocklist: http://peersm.com/getblocklist
>     Check the 10 M passwords list: http://peersm.com/findmyass
>     Anti-spies and private torrents, dynamic blocklist: http://torrent-live.org
>     Peersm : http://www.peersm.com
>     torrent-live: https://github.com/Ayms/torrent-live
>     node-Tor : https://www.github.com/Ayms/node-Tor
>     GitHub : https://www.github.com/Ayms
>
-- 
Move your coins by yourself (browser version): https://peersm.com/wallet
Bitcoin transactions made simple: https://github.com/Ayms/bitcoin-transactions
Zcash wallets made simple: https://github.com/Ayms/zcash-wallets
Bitcoin wallets made simple: https://github.com/Ayms/bitcoin-wallets
Get the torrent dynamic blocklist: http://peersm.com/getblocklist
Check the 10 M passwords list: http://peersm.com/findmyass
Anti-spies and private torrents, dynamic blocklist: http://torrent-live.org
Peersm : http://www.peersm.com
torrent-live: https://github.com/Ayms/torrent-live
node-Tor : https://www.github.com/Ayms/node-Tor
GitHub : https://www.github.com/Ayms


--------------9D8C40B9B186698EE4BB1A33
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Ah, OK, that's of course a good thing to document this
      undocumented (and strange) stuff, as a matter of fact I
      implemented it after reading your post (because this was on my
      todo list since some time) and got annoyed quickly, mainly by what
      is doing formatMessageForSigning (which is quite trivial when you
      know it but would be good to document precisely)</p>
    <p>So, yes, it's a good idea to write this, regarding the header I
      still don't see the use, testing the different possibilities is
      not a big deal, why the signature format is not the same as
      transactions one is mysterious too<br>
    </p>
    <div class="moz-cite-prefix">Le 19/02/2019 à 00:24, Christopher
      Gilliard a écrit :<br>
    </div>
    <blockquote type="cite"
cite="mid:CAK=nyAztSeEbDL=98PTdx-sdqGOug26-3vyADA-tc5oxECyZPw@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">The proposal includes actual code that does
        verification, but I didn't include code for signing. I thought
        it could be inferred, but I could at least include a description
        of how to sign. I am not sure exactly what part you are
        referring to by "keys speech", but the signatures are done by
        ECDSA keys so it's hard to not include anything about keys even
        though that's not the main topic. The "Background on ECDSA keys"
        section was mainly meant to give background about what kind of
        keys Bitcoin uses, for people who already know that they can
        easily skip this section so I would probably think it's best
        just to leave in.  Maybe it should be at the end as an addendum
        though. Yes, I did not invent any of this, I'm just documenting
        what people actually seem to do because I had to verify
        signatures as part of a project I'm working on. I would have
        liked to have had this document when I started the project so I
        thought it might be useful to others since as far as I can tell
        this was not specified anywhere. The reason for including this
        data in the header is the same that compressed/uncompressed is
        included in the header so that you know which type of key the
        signature is from and you don't have to try all options to see
        if any matches. This is why Trezor did that way and why I
        documented it. I'm sure there are other ways to do this, but
        since this is out there in the field being used and is a
        reasonable solution, I thought I'd write it up.</div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Mon, Feb 18, 2019 at 2:59
          PM Aymeric Vitte &lt;<a href="mailto:vitteaymeric@gmail.com"
            moz-do-not-send="true">vitteaymeric@gmail.com</a>&gt; wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px
          0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div bgcolor="#FFFFFF">
            <p>Then, since you wrote this proposal, maybe you should add
              the very precise description of the signing/verification
              process since it is documented nowhere</p>
            <p>I don't get the use of the speech regarding keys while it
              should focus on signatures which are summarized in a vague
              sentence inspired by your ref [2] with a not very logical
              link to the next paragraph stating that r,s should be 32B
              and the whole thing 65B with a header of 1B, you did not
              invent it, that's probably the rule, not sure where it is
              specified again and for what purpose, the header seems
              completely of no use especially when you extend to
              segwit/bech32 since you just have to check that related
              compressed key matches<br>
            </p>
            <div class="gmail-m_416822245153225270moz-cite-prefix">Le
              17/02/2019 à 15:14, Christopher Gilliard via bitcoin-dev a
              écrit :<br>
            </div>
            <blockquote type="cite">
              <div dir="ltr">
                <div dir="ltr">
                  <div dir="ltr">I have written up a proposed BIP. It
                    has to do with Signature formats when using Bitcoin
                    Private keys. It is here: <a
                      href="https://github.com/cgilliard/BIP/blob/master/README.md"
                      target="_blank" moz-do-not-send="true">https://github.com/cgilliard/BIP/blob/master/README.md</a></div>
                  <div dir="ltr"><br>
                  </div>
                  <div>This BIP was written up as suggested in this
                    github issue: <a
                      href="https://github.com/bitcoin/bitcoin/issues/10542"
                      target="_blank" moz-do-not-send="true">https://github.com/bitcoin/bitcoin/issues/10542</a></div>
                  <div><br>
                  </div>
                  <div>Note that the proposal is inline with the
                    implementation that Trezor implemented in the above
                    issue.</div>
                  <div dir="ltr"><br>
                  </div>
                  <div>Any feedback would be appreciated. Please let me
                    know what the steps are with regards to getting a
                    BIP number assigned or any other process steps
                    required.</div>
                  <div><br>
                  </div>
                  <div>Regards,</div>
                  <div>Chris</div>
                </div>
              </div>
              <br>
              <fieldset
                class="gmail-m_416822245153225270mimeAttachmentHeader"></fieldset>
              <pre class="gmail-m_416822245153225270moz-quote-pre">_______________________________________________
bitcoin-dev mailing list
<a class="gmail-m_416822245153225270moz-txt-link-abbreviated" href="mailto:bitcoin-dev@lists.linuxfoundation.org" target="_blank" moz-do-not-send="true">bitcoin-dev@lists.linuxfoundation.org</a>
<a class="gmail-m_416822245153225270moz-txt-link-freetext" href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" target="_blank" moz-do-not-send="true">https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev</a>
</pre>
            </blockquote>
            <pre class="gmail-m_416822245153225270moz-signature" cols="72">-- 
Move your coins by yourself (browser version): <a class="gmail-m_416822245153225270moz-txt-link-freetext" href="https://peersm.com/wallet" target="_blank" moz-do-not-send="true">https://peersm.com/wallet</a>
Bitcoin transactions made simple: <a class="gmail-m_416822245153225270moz-txt-link-freetext" href="https://github.com/Ayms/bitcoin-transactions" target="_blank" moz-do-not-send="true">https://github.com/Ayms/bitcoin-transactions</a>
Zcash wallets made simple: <a class="gmail-m_416822245153225270moz-txt-link-freetext" href="https://github.com/Ayms/zcash-wallets" target="_blank" moz-do-not-send="true">https://github.com/Ayms/zcash-wallets</a>
Bitcoin wallets made simple: <a class="gmail-m_416822245153225270moz-txt-link-freetext" href="https://github.com/Ayms/bitcoin-wallets" target="_blank" moz-do-not-send="true">https://github.com/Ayms/bitcoin-wallets</a>
Get the torrent dynamic blocklist: <a class="gmail-m_416822245153225270moz-txt-link-freetext" href="http://peersm.com/getblocklist" target="_blank" moz-do-not-send="true">http://peersm.com/getblocklist</a>
Check the 10 M passwords list: <a class="gmail-m_416822245153225270moz-txt-link-freetext" href="http://peersm.com/findmyass" target="_blank" moz-do-not-send="true">http://peersm.com/findmyass</a>
Anti-spies and private torrents, dynamic blocklist: <a class="gmail-m_416822245153225270moz-txt-link-freetext" href="http://torrent-live.org" target="_blank" moz-do-not-send="true">http://torrent-live.org</a>
Peersm : <a class="gmail-m_416822245153225270moz-txt-link-freetext" href="http://www.peersm.com" target="_blank" moz-do-not-send="true">http://www.peersm.com</a>
torrent-live: <a class="gmail-m_416822245153225270moz-txt-link-freetext" href="https://github.com/Ayms/torrent-live" target="_blank" moz-do-not-send="true">https://github.com/Ayms/torrent-live</a>
node-Tor : <a class="gmail-m_416822245153225270moz-txt-link-freetext" href="https://www.github.com/Ayms/node-Tor" target="_blank" moz-do-not-send="true">https://www.github.com/Ayms/node-Tor</a>
GitHub : <a class="gmail-m_416822245153225270moz-txt-link-freetext" href="https://www.github.com/Ayms" target="_blank" moz-do-not-send="true">https://www.github.com/Ayms</a></pre>
          </div>
        </blockquote>
      </div>
    </blockquote>
    <pre class="moz-signature" cols="72">-- 
Move your coins by yourself (browser version): <a class="moz-txt-link-freetext" href="https://peersm.com/wallet">https://peersm.com/wallet</a>
Bitcoin transactions made simple: <a class="moz-txt-link-freetext" href="https://github.com/Ayms/bitcoin-transactions">https://github.com/Ayms/bitcoin-transactions</a>
Zcash wallets made simple: <a class="moz-txt-link-freetext" href="https://github.com/Ayms/zcash-wallets">https://github.com/Ayms/zcash-wallets</a>
Bitcoin wallets made simple: <a class="moz-txt-link-freetext" href="https://github.com/Ayms/bitcoin-wallets">https://github.com/Ayms/bitcoin-wallets</a>
Get the torrent dynamic blocklist: <a class="moz-txt-link-freetext" href="http://peersm.com/getblocklist">http://peersm.com/getblocklist</a>
Check the 10 M passwords list: <a class="moz-txt-link-freetext" href="http://peersm.com/findmyass">http://peersm.com/findmyass</a>
Anti-spies and private torrents, dynamic blocklist: <a class="moz-txt-link-freetext" href="http://torrent-live.org">http://torrent-live.org</a>
Peersm : <a class="moz-txt-link-freetext" href="http://www.peersm.com">http://www.peersm.com</a>
torrent-live: <a class="moz-txt-link-freetext" href="https://github.com/Ayms/torrent-live">https://github.com/Ayms/torrent-live</a>
node-Tor : <a class="moz-txt-link-freetext" href="https://www.github.com/Ayms/node-Tor">https://www.github.com/Ayms/node-Tor</a>
GitHub : <a class="moz-txt-link-freetext" href="https://www.github.com/Ayms">https://www.github.com/Ayms</a></pre>
  </body>
</html>

--------------9D8C40B9B186698EE4BB1A33--