summaryrefslogtreecommitdiff
path: root/4c/4f81d34587eb6b66ffb60aa15da633a642b1c6
blob: 8b81ca848ed21e160abbbe12ff92217bd53b7403 (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
Return-Path: <pieter.wuille@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 73B1B504
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sun, 17 Sep 2017 02:29:44 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-yw0-f175.google.com (mail-yw0-f175.google.com
	[209.85.161.175])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id F354012F
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sun, 17 Sep 2017 02:29:43 +0000 (UTC)
Received: by mail-yw0-f175.google.com with SMTP id t127so3369581ywg.4
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 16 Sep 2017 19:29:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to; 
	bh=HWOv4Id84x6mf0H/xS9k2K4E1IIYI/PIVmDo09l91/A=;
	b=klimf7bNGj0UZmMqNsgLDDeNTgX8ipKRh0fv3QuOhyYKQ9wVxjwklvBqgE/9rfBhNT
	E7HuJvtygWeRMs+/hhmfLLqtT2T7l+u5Rgx1EHRCxNiMJqyu5p2Rv56baAyCIq1gVavc
	jB7SUdtq95eIOiIrwNbhjIUdsRoi9iHCpx61G428UPCgnguzC0cTuh2IpwiWw2K0nM/0
	3+5ntXSwM1o4xG1eFlYG0J+BrXrKxrfHz8fgHtFUHKi1aZAWTQQmmXEfiOacGNa802yl
	5T1h2zMFpGQw5fw1kX58Piy/rU7C1mGg5dNX/c4DO9nrTkax/0vX6YWOWhZXEU3zXhHV
	6Nrg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to;
	bh=HWOv4Id84x6mf0H/xS9k2K4E1IIYI/PIVmDo09l91/A=;
	b=JPCpBYV+nkHfvM4Yg4xeK/hO/Mp7SCm3JGQazE9Sc2zoam8/4e3Wg6AxRpSPfqZBE8
	5qbdQzRcMr8WnNL6ZZAXLR16TpeQHOCixQI07/mXEc6/4C9grpZvP8W+4emkYvv2rF0y
	4liRS3lGRZFSETvhrWsN3fENYJ1ecKGJ8BvM3MeJXqDLIOofKIr4spta1VzM868KlAA+
	5gqYAL+4Uqgp6pfVR3Pjd8hlgBwIAV2cLjyigidohQAVV4gdXUy/IwfQMEEiEK/VgWvZ
	T8JXfshrBrFa6c6vESDJifLU5zWqNzI7Lae5/3xuJ1GwIbUdgSj4ZPI2516KgyJk8Hxr
	wOng==
X-Gm-Message-State: AHPjjUg8LeEdyAwaRAumPKjPrRpNB7pituEaY73sxTLjoGqPUaOcRhyG
	mi1VbTLfMMZwoCnYyoch+q+J+2RXFnljQavZMkX3fQ==
X-Google-Smtp-Source: AOwi7QDwMY616yGYkOjY89woTZWjkkZenO3cIYOcNxr84PockcNpkJ1R9YTC1hm226kMY81GVVovnXsyrO3vU7EjvK8=
X-Received: by 10.129.174.94 with SMTP id g30mr7629886ywk.153.1505615382917;
	Sat, 16 Sep 2017 19:29:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.80.80 with HTTP; Sat, 16 Sep 2017 19:29:41 -0700 (PDT)
Received: by 10.37.80.80 with HTTP; Sat, 16 Sep 2017 19:29:41 -0700 (PDT)
In-Reply-To: <34198916-cde9-c84d-ca41-9feb8956bd80@electrum.org>
References: <34198916-cde9-c84d-ca41-9feb8956bd80@electrum.org>
From: Pieter Wuille <pieter.wuille@gmail.com>
Date: Sat, 16 Sep 2017 19:29:41 -0700
Message-ID: <CAPg+sBgukwdRvfFcgdusrXoo8RiXm8OEL-WvHzjpiD8_HU5KmQ@mail.gmail.com>
To: Thomas Voegtlin <thomasv@electrum.org>, 
	Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="f403045f6d8c113a4d05595966bb"
X-Spam-Status: No, score=0.4 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,
	RCVD_IN_SORBS_SPAM autolearn=disabled version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] proposal: extend WIF format for segwit
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 Sep 2017 02:29:44 -0000

--f403045f6d8c113a4d05595966bb
Content-Type: text/plain; charset="UTF-8"

On Sep 15, 2017 01:56, "Thomas Voegtlin via bitcoin-dev" <
bitcoin-dev@lists.linuxfoundation.org> wrote:

Note 3: we could also use a bech32 format for the private key, if it is
going to be used with a bech32 address. I am not sure if such a format
has been proposed already.


I've been working on an "extended bech32" format with 12 character checksum
rather than 6, for private keys and other things that need stronger
protection. It would guarantee correcting 4 errors, where normal bech32 can
only detect (but not correct) 4.

The rationale is that in the case of an address, if an error is detected,
you can ask the receiver for a corrected version. As that option doesn't
exist for private keys you want something stronger.

This has been a low-priority thing for me, though, and the computation work
to find a good checksum is significant.

Cheers,

-- 
Pieter

--f403045f6d8c113a4d05595966bb
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div class=3D"gmail_extra" dir=3D"auto"><div class=3D"gma=
il_quote">On Sep 15, 2017 01:56, &quot;Thomas Voegtlin via bitcoin-dev&quot=
; &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@=
lists.linuxfoundation.org</a>&gt; wrote:<blockquote class=3D"quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Note 3: we could also use a bech32 format for the private key, if it is<br>
going to be used with a bech32 address. I am not sure if such a format<br>
has been proposed already.<br></blockquote></div></div><div dir=3D"auto"><b=
r></div><div dir=3D"auto">I&#39;ve been working on an &quot;extended bech32=
&quot; format with 12 character checksum rather than 6, for private keys an=
d other things that need stronger protection. It would guarantee correcting=
 4 errors, where normal bech32 can only detect (but not correct) 4.</div><d=
iv dir=3D"auto"><br></div><div dir=3D"auto">The rationale is that in the ca=
se of an address, if an error is detected, you can ask the receiver for a c=
orrected version. As that option doesn&#39;t exist for private keys you wan=
t something stronger.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Th=
is has been a low-priority thing for me, though, and the computation work t=
o find a good checksum is significant.</div><div dir=3D"auto"><br></div><di=
v dir=3D"auto">Cheers,</div><div dir=3D"auto"><br></div><div dir=3D"auto">-=
-=C2=A0</div><div dir=3D"auto">Pieter</div><div dir=3D"auto"><br></div><div=
 class=3D"gmail_extra" dir=3D"auto"><div class=3D"gmail_quote"><blockquote =
class=3D"quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;paddi=
ng-left:1ex"></blockquote></div></div></div>

--f403045f6d8c113a4d05595966bb--