summaryrefslogtreecommitdiff
path: root/86/78efa7be486d4d62cb2d95af0df886185c1e89
blob: 702a50b59fa008204d7152429798e0655521679f (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
Return-Path: <snigirev.stepan@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id BF0351592
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu,  1 Aug 2019 13:51:01 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qk1-f170.google.com (mail-qk1-f170.google.com
	[209.85.222.170])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id C433C82B
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu,  1 Aug 2019 13:50:59 +0000 (UTC)
Received: by mail-qk1-f170.google.com with SMTP id r4so51959469qkm.13
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu, 01 Aug 2019 06:50:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:references:in-reply-to:from:date:message-id:subject:to; 
	bh=2n8pJ6gUiCkVMdk+rU/GhUIjpvEhbo9FvWTpF4a4CVM=;
	b=rQtirVsptbH8GVrpRvswPSfh2WJXuO7R52mTG7Dq48uujhy9A2bFEXKlnmC/0Qotc4
	M9dSCnT+qckc76dCGrJjRjRUdX0ICuuBheSmK3LCkAdmMRdilLoa1p+XTgRntb5lZo/2
	eQBbFqixkVwD2Z+5IPE8ly77MVt14EfYzui1FO1PwQUn6eeDFnWk6XrypefBWdUmxmG8
	M75eqixetapqCAIWUQaTbHWqOcJxn1Xm8JswJ1nV1RhJ9ElP6iv8yZQ5UG3k5vKIbPjg
	WLhgqaV/j00Tw1xzt3HXNetYdVt+uRPBnK9QQVuDEHcmeilsr8lp4TPsglV5ttjn6hvG
	hvzw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:references:in-reply-to:from:date
	:message-id:subject:to;
	bh=2n8pJ6gUiCkVMdk+rU/GhUIjpvEhbo9FvWTpF4a4CVM=;
	b=TlTMw3vWrMgtBA3mU1hwV3o5enUYe23WmFwJPqLANUElhKec2yWI8orWw/oBR8Et3u
	WFDksUGhOv0xdRkamQTu5JKzwKLiPq29NufTVs3SyBLzmmMGaf/WqgGEtjbcu+lZU1la
	ZzExTKs1kLe5Glw520KyF10DWGo8seZd3zb21QDJ/5xHe1oepv1cu7ZiSl6VyqWHlKKp
	3q3P3Bc6euf9QEUlfROuAsX02I/mLuex4YzLDbI1xHjCUnC003Nn5LUamrlAud2YJGnU
	X7Ax7Y+gS3usYMvYb2Ua9jf+gVOpHCsJYMYo/SrgacSxtssRfro+xv6v2mnho4NIB6/x
	Tdpw==
X-Gm-Message-State: APjAAAUjc/pesm7BkDz8IjtFmIs0GtWzsPjvQjNCkwtLbP+ogEelO1+S
	sEYoPlcp6lK1f8tLRYQcxRV0CxQX8FXJh0oio6YfNrGhVl4=
X-Google-Smtp-Source: APXvYqxzOScZrsNWa2rki96p4ztZL+7juP0emKO0pGdbpcMAc1EIqqU48fUsEh71bkDpMf/GgFSmo2je9fx8a5E8dkA=
X-Received: by 2002:a05:620a:12af:: with SMTP id
	x15mr17333676qki.89.1564667458520; 
	Thu, 01 Aug 2019 06:50:58 -0700 (PDT)
MIME-Version: 1.0
References: <mailman.437.1564598007.27056.bitcoin-dev@lists.linuxfoundation.org>
In-Reply-To: <mailman.437.1564598007.27056.bitcoin-dev@lists.linuxfoundation.org>
From: Stepan Snigirev <snigirev.stepan@gmail.com>
Date: Thu, 1 Aug 2019 09:50:47 -0400
Message-ID: <CACL8y1tOn_U2YjpzGuRebv=2=tvaEYwR2yMCK_4girJ4WtZ1Ug@mail.gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary="0000000000000e8a5a058f0e886e"
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: Thu, 01 Aug 2019 14:26:02 +0000
Subject: Re: [bitcoin-dev] Proposed Extensions to BIP 174 for Future
	Extensibility
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, 01 Aug 2019 13:51:01 -0000

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

> why not use Bitcoin compact uint, which most PSBT consumers already
implement?

I totally agree with that, compact int parsing is already implemented in
all bitcoin applications, wallets and libraries. Also, for certain (mb
proprietary) applications I will be willing to use multi-byte keys where
the first byte defines the application type and next bytes define
application-specific fields.

I would suggest to set proprietary bytes to 0xF0-0xFC or to 0xE0-0xEF then
(E for Enterprise?).

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

<div dir=3D"ltr"><div>&gt; why not use Bitcoin compact uint, which most PSB=
T consumers already</div>implement?<div><br></div><div>I totally agree with=
 that, compact int parsing is already implemented in all bitcoin applicatio=
ns, wallets and libraries. Also, for certain (mb proprietary) applications =
I will be willing to use multi-byte keys where the first byte defines the a=
pplication type and next bytes define application-specific fields.</div><di=
v><br></div><div>I would suggest to set proprietary bytes to 0xF0-0xFC or t=
o 0xE0-0xEF then (E for Enterprise?).</div></div>

--0000000000000e8a5a058f0e886e--