From: Alex Mizrahi <alex.mizrahi@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Feedback request: colored coins protocol
Date: Thu, 10 Apr 2014 20:24:24 +0300 [thread overview]
Message-ID: <CAE28kUSWwamovgPA1AvAojoKuwaDvuWzbnYf6yJhQ89HRnOJGg@mail.gmail.com> (raw)
In-Reply-To: <5346CDD4.8050206@monetize.io>
[-- Attachment #1: Type: text/plain, Size: 838 bytes --]
> At this point, I don't think what you are doing is even colored coins
> anymore. You might want to look into Counterparty or Mastercoin.
>
Nope, it's still colored coins. The difference between colored coin model
and Mastercoin model is that colored coins are linked to transaction
outputs, while Mastercoin has a notion of address balances.
The implications of this is that in colored coin model explicit
dependencies allow us to rely on SPV. (Assuming that one can fetch the
dependency graph to link txout in question to genesis.)
While it is not the case with Mastercoin.
While it's pretty far from the original colored coins model, what Flavien
have described is identical to it in majority of aspects.
This is an interesting approach, but OP_RETURN size limitations can be a
significant problem for some kinds of applications.
[-- Attachment #2: Type: text/html, Size: 1199 bytes --]
next prev parent reply other threads:[~2014-04-10 17:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-06 20:59 Flavien Charlon
2014-04-06 23:23 ` Mark Friedenbach
2014-04-07 9:49 ` Flavien Charlon
2014-04-07 12:12 ` Jorge Timón
2014-04-07 14:00 ` Flavien Charlon
2014-04-07 15:06 ` Mark Friedenbach
2014-04-07 15:19 ` Flavien Charlon
2014-04-07 18:23 ` Jorge Timón
2014-04-07 19:26 ` Flavien Charlon
2014-04-07 19:58 ` Alex Mizrahi
2014-04-10 12:19 ` Flavien Charlon
2014-04-10 14:28 ` Jean-Pierre Rupp
2014-04-10 16:59 ` Mark Friedenbach
2014-04-10 17:24 ` Alex Mizrahi [this message]
2014-04-11 12:51 ` Flavien Charlon
2014-04-07 11:28 ` Alex Mizrahi
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=CAE28kUSWwamovgPA1AvAojoKuwaDvuWzbnYf6yJhQ89HRnOJGg@mail.gmail.com \
--to=alex.mizrahi@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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