From: Alex Mizrahi <alex.mizrahi@gmail•com>
To: Erik Aronesty <erik@q32•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Cc: Nicolas Dorier <nicolas.dorier@gmail•com>
Subject: Re: [bitcoin-dev] BIP Number Request: Open Asset
Date: Tue, 2 Aug 2016 20:25:50 +0300 [thread overview]
Message-ID: <CAE28kUSaTsQ4qyGK5t5D1KiEF3yf4LEjkFvy+SiGxDK5VeAo9Q@mail.gmail.com> (raw)
In-Reply-To: <CAJowKgJys93VTFuGA3ydcuqxcx_O6r0D7715Kgfyc+SP4P8J9A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2321 bytes --]
>
> 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
>
We actually tried to do that in 2014-2015, but that effort have failed...
Nobody was really interested in collaboration, each company only cared
about it's own product.
Especially Colu, they asked everyone for requirements, and then developed a
new protocol completely on their own without taking anyone's input.
I'm not sure that merging the protocols makes sense, as some protocols
value simplicity, and a combined protocol cannot have this feature.
I don't think there is much interest in a merged colored coin protocol now.
Colu is moving away from colored coins, as far as I can tell.
CoinSpark is now doing MultiChain closed-source private blockchain.
CoinPrism also seems to be largely disinterested in colored coins.
We (ChromaWay) won't mind replacing EPOBC with something better, our
software could always support multiple different kernels so adding a new
protocol isn't a big deal for us.
So if somebody is interested in a new protocol please ping me.
One of ideas I have is to decouple input-output mapping/multiplexing from
coloring.
So one layer will describe a mapping, e.g. "Inputs 0 and 1 should go into
outputs 0, 1 and 2".
In this case it will be possible to create more advanced protocols (e.g.
with support for 'smart contracts' and whatnot) while also keeping them
compatible with old ones to some extent, e.g. a wallet can safely engage in
p2ptrade or CoinJoin transactions without understanding all protocols used
in a transaction.
> - in collaboration with feedback from core developers that understand the
> direction the protocol will be taking and the issues to avoid.
>
Core developers generally dislike things like colored coins, so I doubt
they are going to help.
Blockstream is developing a sidechain with user-defined assets, so I guess
they see it as the preferred way of doing things:
https://elementsproject.org/elements/asset-issuance/
> As it stands, investors have to install multiple wallets to deal with
> these varying implementations.
>
Actually this can be solved without making a new "merged protocol": one can
just implement a wallet which supports multiple protocols.
[-- Attachment #2: Type: text/html, Size: 3566 bytes --]
next prev parent reply other threads:[~2016-08-02 17:25 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
2016-08-02 17:25 ` Alex Mizrahi [this message]
[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=CAE28kUSaTsQ4qyGK5t5D1KiEF3yf4LEjkFvy+SiGxDK5VeAo9Q@mail.gmail.com \
--to=alex.mizrahi@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=erik@q32$(echo .)com \
--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