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
|
Return-Path: <dev@jonasschnelli.ch>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 2C89EB12
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 7 Sep 2017 16:47:24 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from bitcoin.jonasschnelli.ch (bitcoinsrv.jonasschnelli.ch
[138.201.55.219])
by smtp1.linuxfoundation.org (Postfix) with ESMTP id 3BEB41E2
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 7 Sep 2017 16:47:23 +0000 (UTC)
Received: by bitcoin.jonasschnelli.ch (Postfix, from userid 1002)
id 2781315E4806; Thu, 7 Sep 2017 18:47:22 +0200 (CEST)
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Spam-Level:
X-Spam-Status: No, score=-0.0 required=5.0 tests=RP_MATCHES_RCVD
autolearn=disabled version=3.3.1
Received: from [10.0.1.66] (199-241-203-51.PUBLIC.monkeybrains.net
[199.241.203.51])
by bitcoin.jonasschnelli.ch (Postfix) with ESMTPSA id 58D1E15E4804;
Thu, 7 Sep 2017 18:47:21 +0200 (CEST)
From: Jonas Schnelli <dev@jonasschnelli.ch>
Content-Type: multipart/signed;
boundary="Apple-Mail=_BF4753AD-8747-47E4-9292-418FF2C99571";
protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Thu, 7 Sep 2017 09:47:16 -0700
References: <0d405f5d-c0a4-bad7-b6c3-08ba4424bf17@satoshilabs.com>
To: Pavol Rusnak <stick@satoshilabs.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
In-Reply-To: <0d405f5d-c0a4-bad7-b6c3-08ba4424bf17@satoshilabs.com>
Message-Id: <A806D2EB-744F-41A9-91C1-603F89E9005B@jonasschnelli.ch>
X-Mailer: Apple Mail (2.3273)
X-Virus-Scanned: clamav-milter 0.99.2 at bitcoinsrv.jonasschnelli.ch
X-Virus-Status: Clean
Subject: Re: [bitcoin-dev] Proposal: Extended serialization format for
BIP-32 wallets
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: Thu, 07 Sep 2017 16:47:24 -0000
--Apple-Mail=_BF4753AD-8747-47E4-9292-418FF2C99571
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8
Thanks for the proposal.
Three points it could see as possible improvements:
1.
=46rom what I know, the exact birthday in seconds doesn=E2=80=99t matter =
that much therefore it may be possible to just use 13 or 16bits to =
create a representation in week from 2009-01-09 00:00 UTC. 13bits would =
give you 157 years.
Always round down to the beginning of the week when the key was created.
But not sure if it=E2=80=99s worth to save ~two bytes for that.
Also not sure if the key-birthday in seconds could have a security or =
privacy implication (week maybe better).
2.
Would it make sense to have special depth bytes that directly implies =
it=E2=80=99s a BIP44 master key (and therefore avoid the bip32 path =
serialisation)? I know some =E2=80=9Ecentralised=E2=80=9C table need to =
be available for that which may be not a good idea. But maybe the BIP =
could reserve a couple of depth-bytes (maybe 0xF0 to 0xFF) for =
predefined paths.
3.
Would adding a version bit make sense to allow future extensions?
/jonas
> Am 06.09.2017 um 15:29 schrieb Pavol Rusnak via bitcoin-dev =
<bitcoin-dev@lists.linuxfoundation.org>:
>=20
> The discussion about changing bip32 version bytes for SegWit got me
> thinking and I ended up with what I think is the best proposal:
>=20
> https://github.com/satoshilabs/slips/blob/master/slip-0032.md
>=20
> (It is hosted in SL repo for now, but if there is will, I would love =
to
> have this added to BIP repo as an extension to BIP32)
>=20
> Feel free to comment.
>=20
> --
> Best Regards / S pozdravom,
>=20
> Pavol "stick" Rusnak
> CTO, SatoshiLabs
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
--Apple-Mail=_BF4753AD-8747-47E4-9292-418FF2C99571
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEyhopCNzi8TB0xizeHrd2uwPHki0FAlmxeBQACgkQHrd2uwPH
ki0VQhAA1DD2tKCCPlsIH0Z+gGDwKkFTeoSDLDjAKU4KLvK4DLlU6/wowrGYHC72
VbneJlLVjjKgJRDpDn1c2LDe1ifl3NC6oDUo+PcPyLQTJmOLlokLisb+BkZVTOZg
B6wjE3767w3wJlK3LGyA99KRzwMobacInZSN4VgN67OFsQhmdrIx/5kcD2ssJse6
kXaRbDlCDsBw3jyK87D96966S4kaAUKQ9tRZJqOg5BFgYBTCzlgH2xVBwte9Jvq6
pbOxCRxYmAXXK2xmIq1m72Dsc6AipHTybTkafIc4nSKGUgWlDLYswLr8PEd1sJw1
Af9u3oRnFSMjKogDJj0lZPFqEGlKVP6/GKcbn0h4XcZei8+Q1lrt4lvA8KvpbbfF
cDTwHxDug5bhC4TAFD8JylNdUYxDAWrJO5avjuiLOU3AqS2iUgSL4CXjzPtJlmfe
cagCXFW9asc337EMOqA4cR1s0+kW2Hdjo8R7u7LStl70niuqLIJGYt+606+DtQDD
3qbnG1FWZm1pYHpHbwvRQm84v9q9PEcn2cYJhbIYlR0bg2eufxjz941VViY216u8
/o+QheFI4mhJT/sqkAyfLMv2yXHer0/ZifSNdLk0flTzeAwIy96KwZhlfJxuI4tH
nuLjyvBf28+PlQP9AFtHaqIc8P/k758XTRLuf10FyiH9z71Jy7g=
=i85G
-----END PGP SIGNATURE-----
--Apple-Mail=_BF4753AD-8747-47E4-9292-418FF2C99571--
|
