From: Erik Aronesty <erik@q32•com>
To: Nicolas Dorier <nicolas.dorier@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP Number Request: Open Asset
Date: Tue, 2 Aug 2016 10:53:59 -0400 [thread overview]
Message-ID: <CAJowKgJys93VTFuGA3ydcuqxcx_O6r0D7715Kgfyc+SP4P8J9A@mail.gmail.com> (raw)
In-Reply-To: <CA+1nnrmsU5kLxuW=GJSmy8C7s6F3EM8sgFYoXDg1iM-eD2qzsg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]
> 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.
[-- Attachment #2: Type: text/html, Size: 1437 bytes --]
next prev parent reply other threads:[~2016-08-02 14:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 2:50 Nicolas Dorier
2016-05-26 3:53 ` Luke Dashjr
2016-07-05 17:46 ` Peter Todd
2016-07-06 1:22 ` Luke Dashjr
2016-07-06 2:14 ` James MacWhyte
2016-07-06 6:49 ` Alex Mizrahi
2016-08-02 5:21 ` Nicolas Dorier
2016-08-02 14:53 ` Erik Aronesty [this message]
2016-08-02 17:25 ` Alex Mizrahi
[not found] ` <CABbpET83UAt-TZfQsi0ZyhPAEznucc2yKYA4Md9y78=XH-vpmw@mail.gmail.com>
2016-08-13 2:25 ` Nicolas Dorier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJowKgJys93VTFuGA3ydcuqxcx_O6r0D7715Kgfyc+SP4P8J9A@mail.gmail.com \
--to=erik@q32$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=nicolas.dorier@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox