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
|
Return-Path: <earonesty@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 5F1C09FA
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 2 Aug 2016 14:54:02 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-yw0-f174.google.com (mail-yw0-f174.google.com
[209.85.161.174])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id BE63F1D0
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 2 Aug 2016 14:54:01 +0000 (UTC)
Received: by mail-yw0-f174.google.com with SMTP id u134so200278037ywg.3
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 02 Aug 2016 07:54:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:sender:in-reply-to:references:from:date:message-id
:subject:to:cc;
bh=6ZXpVM02EWpIW39ADjClKhl9wO1iasj7bCn0MLqYed4=;
b=EIotFvzBI8lCbUNQAcUWiMN3jkfiWgHYP02ysIBoz+8q3kp+XGKrFc1MGw5VzI7NCq
GKnyLPij0cxXuBrOphND9sw813lrqPRM3HS7oht1gy3NF6gFHNu5ZPHm8IQWafwKyj4N
lK7CfD+nzJERD6qY48btQYqSW/rz/17usFVUCubwkvL8lIRTkWtaakyhhr8Ipr+/lXiX
WuSzBdoN99DwOyZezErQj3+L6k3Lmgu8WtWibfNLfO4U9jvMtbW2Px1zr+K6iK4CIl04
BazhJVhNC5dcZdD0BL7Aqm/u3G9X6rETdjg3aWDfPOqgD6pQLTEvwR2UQzoeR/Xc6SXQ
kGAw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:sender:in-reply-to:references:from
:date:message-id:subject:to:cc;
bh=6ZXpVM02EWpIW39ADjClKhl9wO1iasj7bCn0MLqYed4=;
b=k2SxXE/OMmKQqJV46EjUplaDXv9Ne6ZStkjlc0Uejx2UQEJKpS3cexmExI41UXYqhf
4AeueZkCuhQsC/oKndqVh3X1kWxbTXlHA0AglA431XdPFVSHDWk5+4PtNUOvGJFLNlwZ
0aUEafgv+PtofTK0OEeW7IDjfIwHW9TOAT+Ac+5drQiNzQYpcZkMP8MKCw2y3wDs+8cD
vtmdd1kgDN2CSy+x5cU02ql1ZPWbdIavVOqjLHbF25COgIivRnmJiPximL3AqBTZzm2o
/Q2XRPX4Qb2KUJo5s+mqhGG8U01CWg1regITexqKDrQR1wBsCZJLtAuXPDXLM9blxsTJ
efJg==
X-Gm-Message-State: AEkoouvumqIks+U+TUyjcaGhzwOh8aeQ5bNYvgToHzduhxlH0t0NleBEhMqqyyd9Ab+k7HDjIV4OnsYF477glg==
X-Received: by 10.129.51.149 with SMTP id z143mr48659404ywz.74.1470149640956;
Tue, 02 Aug 2016 07:54:00 -0700 (PDT)
MIME-Version: 1.0
Sender: earonesty@gmail.com
Received: by 10.37.88.214 with HTTP; Tue, 2 Aug 2016 07:53:59 -0700 (PDT)
In-Reply-To: <CA+1nnrmsU5kLxuW=GJSmy8C7s6F3EM8sgFYoXDg1iM-eD2qzsg@mail.gmail.com>
References: <CA+1nnrmZAdzBn-FMBVMGtp4n7bbG8W0VEGvi1WopS-M49zBXpw@mail.gmail.com>
<201605260353.06939.luke@dashjr.org>
<20160705174636.GA24068@fedora-21-dvm>
<201607060122.20593.luke@dashjr.org>
<CAH+Axy5A-_oDoPjabyzzAF8kVq9DsFwonEYPp9EU+Hf_BP1-DA@mail.gmail.com>
<CA+1nnrmsU5kLxuW=GJSmy8C7s6F3EM8sgFYoXDg1iM-eD2qzsg@mail.gmail.com>
From: Erik Aronesty <erik@q32.com>
Date: Tue, 2 Aug 2016 10:53:59 -0400
X-Google-Sender-Auth: E0iigbNJBK1Wife-zQPZkcaiaK4
Message-ID: <CAJowKgJys93VTFuGA3ydcuqxcx_O6r0D7715Kgfyc+SP4P8J9A@mail.gmail.com>
To: Nicolas Dorier <nicolas.dorier@gmail.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a114177f81db481053917e3e8
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, 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
Subject: Re: [bitcoin-dev] BIP Number Request: Open Asset
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, 02 Aug 2016 14:54:02 -0000
--001a114177f81db481053917e3e8
Content-Type: text/plain; charset=UTF-8
> As said, Open Asset is not a draft proposal and is already used in the
wild since 2014. We can't easily modify the protocol by now for improving
it.
You can, however, provide a new OA2.0 protocol that improves upon these
issues, and assure that upgraded wallets maintain support for both
versions.
It seems like OA's stance has *always *been to focus on integration, rather
than fixing the core protocol and then, by virtue of having the largest
integration, saying things like "it's too late to turn back now". Colu
and Chromaway/EPOBC also have stuff "in the wild".
I would love to see an RFC-style standard "multiple-colored-coin-protocol"
written by reps from all of the major protocols and that meta-merges the
features of these implementations - in collaboration with feedback from
core developers that understand the direction the protocol will be taking
and the issues to avoid. HTTP/TCP/IP MCCP/BTC
As it stands, investors have to install multiple wallets to deal with these
varying implementations. Merging them into one "meta-specification"
fairly soon might be in the best interests of the community and of future
shareholders.
--001a114177f81db481053917e3e8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><div><div><div><div>> As said, Open Asset is not a=
draft proposal and is already used in the=20
wild since 2014. We can't easily modify the protocol by now for=20
improving it.<br><br></div>You can, however, provide a new OA2.0 protocol t=
hat improves upon these issues, and assure that upgraded wallets maintain s=
upport for both versions.=C2=A0=C2=A0 <br><br></div>It seems like OA's =
stance has <i>always </i>been to focus on integration, rather than fixing t=
he core protocol and then, by virtue of having the largest integration, say=
ing things like "it's too late to turn back now".=C2=A0=C2=A0=
=C2=A0 Colu=C2=A0 and Chromaway/EPOBC also have stuff "in the wild&quo=
t;.<br></div><br></div>I would love to see an RFC-style standard "mult=
iple-colored-coin-protocol" written by reps from all of the major prot=
ocols and that meta-merges the features of these implementations - in colla=
boration with feedback from core developers that understand the direction t=
he protocol will be taking and the issues to avoid.=C2=A0=C2=A0 HTTP/TCP/IP=
MCCP/BTC<br><br>As it stands, investors have to install multiple wallets t=
o deal with these varying implementations.=C2=A0=C2=A0 Merging them into on=
e "meta-specification" fairly soon might be in the best interests=
of the community and of future=20
shareholders.=C2=A0=C2=A0 <br></div><div><br></div><div><br></div><br><div>=
<br><div><div><div><br><br><br></div></div></div></div></div>
--001a114177f81db481053917e3e8--
|
