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
|
Return-Path: <christopher.gilliard@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 11FEEAF7
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 17 Feb 2019 14:14:23 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wm1-f52.google.com (mail-wm1-f52.google.com
[209.85.128.52])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 88E7576F
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 17 Feb 2019 14:14:22 +0000 (UTC)
Received: by mail-wm1-f52.google.com with SMTP id a62so14690163wmh.4
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 17 Feb 2019 06:14:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:from:date:message-id:subject:to;
bh=DzmSs3jEwXPru+wKiwVtLt3Vj9eprJwcqssblAzSHMk=;
b=EoBD1+X1R7ueGefOK3uCn1WKwgIwsUCWwqbUGBzfP7HTW+UMOPhpLWt2iwb7pzMN1c
LKjQJySb/8qbj2S0BAxOWg65z1BWITThHpF0wyfT40ASIirJvQd3q414iUksbhIkKkBV
jU3czWKNistHio6fzAZ+GXSWAenPHSThtx3LWJqbVcU9shbO2Jn0eWl2jMdzdS17x+GE
Ge+Y2OJgjMHbNnC8OBXhqumbLo1Ixiu/18nITLlwY599x3JxEBbUhot/u0YnEENINh/c
t1ru/sqKne94sBKdVb3w9EvbXwiDGaWrvQovw8tyj2gTC9t5K93VKkSfyRgCjsVVUHzr
VbPQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
bh=DzmSs3jEwXPru+wKiwVtLt3Vj9eprJwcqssblAzSHMk=;
b=ovW2gkkhxPimQ+VCO9OKufqmrPiyRbQzKR9Gk7KBPx89WI912TUQuklaGYAeS8aTxA
hqYYEIpiXhL6RPWOWsXOpJX//grwU0f6SVXQCjqwkeY2Y4gKNXpxn/EznmCTQCI3CyB1
RDeVFh2NBc48Cg9NWFj3jvxAiYzXZQriqJJ0fdHvovyLXa1iPzMQZrUsUTAg/egfjuMP
2rabB8Vx3sM5veN+15NqTFTHj6637SrLaPFhxkxcYyC2LYhSPEATh/U6hBMNnS2E+ljd
DfCApFwRQtvxVe8mHwwf3zu5GZqtu+hWuYPHJYadqlYa7yM6UNqPFBlHfko0CtS7xHWn
ctZQ==
X-Gm-Message-State: AHQUAuYytjcOQITLI3vC7fBQ9DtRdBlTUTWkjwn64z0KV6j7kXXedNin
0nwO3E3eDDALoyYlRFid+wUIBe3HYItz1fQWhBPgO0vYQDc=
X-Google-Smtp-Source: AHgI3IaQVM4bwJ3IngcTSnrvrS6GgK1BndeX3/ANFKv3erl93ihL8KyVN1N63yTFn0neAQVVnf46h4INEhvjQQvNC0Q=
X-Received: by 2002:a1c:c489:: with SMTP id
u131mr11888018wmf.127.1550412860704;
Sun, 17 Feb 2019 06:14:20 -0800 (PST)
MIME-Version: 1.0
From: Christopher Gilliard <christopher.gilliard@gmail.com>
Date: Sun, 17 Feb 2019 09:14:37 -0500
Message-ID: <CAK=nyAxXS6rQowFC6ENto+d+D9FzSf5WJLz-WM_vc2D5DQ2xQQ@mail.gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary="000000000000d14dfa0582179f5d"
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: Sun, 17 Feb 2019 17:01:29 +0000
Subject: [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>
X-List-Received-Date: Sun, 17 Feb 2019 14:14:23 -0000
--000000000000d14dfa0582179f5d
Content-Type: text/plain; charset="UTF-8"
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
--000000000000d14dfa0582179f5d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr">I have written up a prop=
osed BIP. It has to do with Signature formats when using Bitcoin Private ke=
ys. It is here:=C2=A0<a href=3D"https://github.com/cgilliard/BIP/blob/maste=
r/README.md">https://github.com/cgilliard/BIP/blob/master/README.md</a></di=
v><div dir=3D"ltr"><br></div><div>This BIP was written up as suggested in t=
his github issue:=C2=A0<a href=3D"https://github.com/bitcoin/bitcoin/issues=
/10542">https://github.com/bitcoin/bitcoin/issues/10542</a></div><div><br><=
/div><div>Note that the proposal is inline with the implementation that Tre=
zor implemented in the above issue.</div><div dir=3D"ltr"><br></div><div>An=
y feedback would be=C2=A0appreciated. Please let me know what the steps are=
with regards to getting a BIP number assigned or any other process steps r=
equired.</div><div><br></div><div>Regards,</div><div>Chris</div></div></div=
>
--000000000000d14dfa0582179f5d--
|
