summaryrefslogtreecommitdiff
path: root/84/db2b76e416a823953f4e874d7041ae35f9441f
blob: 04f4eb27b4065ba0ea82b3b374c98086c708f603 (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
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 BB01B1069
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 19 Jun 2018 15:20:40 +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 206DA758
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 19 Jun 2018 15:20:40 +0000 (UTC)
Received: by bitcoin.jonasschnelli.ch (Postfix, from userid 1002)
	id 0C4A915E5351; Tue, 19 Jun 2018 17:20:39 +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=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	version=3.3.1
Received: from [192.168.0.13] (cable-static-238-67.teleport.ch
	[213.188.238.67])
	by bitcoin.jonasschnelli.ch (Postfix) with ESMTPSA id BA61C15E534A;
	Tue, 19 Jun 2018 17:20:38 +0200 (CEST)
From: Jonas Schnelli <dev@jonasschnelli.ch>
Content-Type: multipart/signed;
	boundary="Apple-Mail=_A1B479F3-4235-4469-AF5F-01555FBCC7DC";
	protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\))
Date: Tue, 19 Jun 2018 17:20:34 +0200
References: <CAPg+sBhGMxXatsyCAqeboQKH8ASSFAfiXzxyXR9UrNFnah5PPw@mail.gmail.com>
	<5b6b9d44-8e6c-2799-438e-d311e221bb57@satoshilabs.com>
To: matejcik <jan.matejek@satoshilabs.com>,
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
In-Reply-To: <5b6b9d44-8e6c-2799-438e-d311e221bb57@satoshilabs.com>
Message-Id: <8CF4BD50-0ECE-4F96-B978-397116CD76CE@jonasschnelli.ch>
X-Mailer: Apple Mail (2.3445.8.2)
X-Virus-Scanned: clamav-milter 0.99.4 at bitcoinsrv.jonasschnelli.ch
X-Virus-Status: Clean
Subject: Re: [bitcoin-dev] BIP 174 thoughts
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: Tue, 19 Jun 2018 15:20:40 -0000


--Apple-Mail=_A1B479F3-4235-4469-AF5F-01555FBCC7DC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I agree with matejcik=E2=80=99s point 1 to 3 and especially with point =
4.
The mandatory flag (or optional-flag) makes much sense to me.

> -----------
>=20
> In general, the standard is trying to be very space-conservative,
> however is that really necessary? We would argue for clarity and ease =
of
> use over space constraints. We think more straightforward approach is
> desired, although more space demanding. What are the arguments to make
> this as small as possible? If we understand correctly, this format is
> not intended for blockchain nor for persistent storage, so size =
doesn=E2=80=99t
> matter nearly as much.

I don=E2=80=99t see any reasons why space would be an issue.

HWWs probably can=E2=80=99t handle PBST natively since it is not =
optimised for
presenting various informations in a signing-verification.

A single stream-in of a PSBT through USB (or similar channel) will not =
work in
many cases since HWW come often with very restrictive RAM constraints.

Furthermore, I forget to mention in my last mail, that registering (or =
defining)
a mime-type for PSBT would probably a great usability feature.
(Send PSBT by email/messanger and with dbl-click to open feature, etc.)


/jonas

--Apple-Mail=_A1B479F3-4235-4469-AF5F-01555FBCC7DC
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-----

iQIzBAEBCAAdFiEEyhopCNzi8TB0xizeHrd2uwPHki0FAlspH0IACgkQHrd2uwPH
ki2YAg//WdAbBIf923ctryL2iKAtgNZp7do3plHHD1RHJT1JVNRmYDhZKbNczMfq
yMhyAjt3kGQ6xwYQkhbbDeHChyhWewCPk2+s5T4NZ1MJFBF6XqcUa5pDOYadIq//
gRn1yQVXFGxUdXbNBbQ6zVggLzMB4kv1jckOOsKEMtqNG309bpNQV1H9fueMTj1y
GoiT/6cnNyvIrM1Flh2pF+EurmQYCSL2e5LHzfQejyrkYvdb0jDQi9jMOwwW9S0y
URzgWxUAaANobGb8CcaKCVqzdIfgWfPOjetcSlxRDQobuKbNPhkNGRmyHzxZRNf4
3VwgYtLa+AuHsrGrCfeV/jEaJaUepyGxS/0/R71B0y9DCHrdWydcbRFGLN8GB+KV
KtsfKlvsBKjqXGOt7iUktrGrX+wReMJz0cr+x+FvE1E4/bIA/WSwXe+n5jr6P9yW
kRfYQzkXKTBjTpsFJGpiR/T3woOlN4WFTh5XkX2kKfRWF3RLTareZyM2kKESJuno
T9yZrmGtbgLoez0yP6hbmkM1+B7w7JwTBu5bT6z/bgfYekOpYtQy21tBCBf99Uz4
j9UneCk3Uw9+sPzIWbyIxpvZvYjBqfhf7r6fTsKLdskR/0Eev0W/cfexeZQ4uEfQ
Os4+iIWNX5YZ2le+pLke8pWBtFwOlm4msfc3PYqPCDqdHQJSYBQ=
=Dbm2
-----END PGP SIGNATURE-----

--Apple-Mail=_A1B479F3-4235-4469-AF5F-01555FBCC7DC--