From: Flavien Charlon <flavien.charlon@coinprism•com>
To: Mark Friedenbach <mark@monetize•io>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Feedback request: colored coins protocol
Date: Mon, 7 Apr 2014 10:49:55 +0100 [thread overview]
Message-ID: <CABbpET_JFceNhRkxSZMyiTxkkYr2MvQVob7o4juEsPj4wo8e8g@mail.gmail.com> (raw)
In-Reply-To: <5341E1FF.7080204@monetize.io>
[-- Attachment #1: Type: text/plain, Size: 2937 bytes --]
Thanks for the feedback Mark.
> (1) there is absolutely no reason to include asset tagging information if
it is not validated
Sure, there is a good reason to include it in the blockchain: so that
clients don't need external information to recognize colored coins. Also,
I'm not sure what you mean by "not validated", in that proposal, the tagged
transaction is the authoritative source of information.
> that just bloats the block chain
9 bytes is much less than what Mastercoin and counterparty are doing
(certainly under the 40 bytes allowed).
> Have you seen the padded order-based coloring scheme worked out here?
Yes I have seen it and find the padding quite clumsy and unintuitive. A
more general solution is the one I described in my original post, where the
color value is entirely separate from the satoshi value, and encoded
separately: if you have to have an additional "padding" value to calculate
color_value = satoshi_value - padding, you might as well have color_value
directly, independently from satoshi_value. But I don't even think it is
necessary:
> (2) And needing a capital of 54 btc for a million shares is totally
unacceptable.
An easy workaround is to have various scales, the same way you have $1
bills, $5 bills an $10 bills. I don't see that as a big problem. That way
the protocol is more lightweight and simple.
Also those 54 BTC (actually 5.4 BTC if the dust is now 540 satoshis) become
part of the capital of the company, and can always be recovered by
uncoloring the shares. It's an investment, not an expense, so I think it is
acceptable.
Best,
Flavien
On Mon, Apr 7, 2014 at 12:23 AM, Mark Friedenbach <mark@monetize•io> wrote:
> On 04/06/2014 01:59 PM, Flavien Charlon wrote:
> > Do you think this is the right approach?
>
> No, I'm afraid it has significant flaws. The two chief flaws are (1)
> there is absolutely no reason to include asset tagging information if it
> is not validated - that just bloats the block chain, and (2) you
> shouldn't be using fixed increments for share sizes either. It's not
> future-proof as the minimum output size changes based on the minimum fee
> (currently 540 satoshis, not 5,400, and it will float in the near
> future). And needing a capital of 54 btc for a million shares is totally
> unacceptable.
>
> Flavien, I know that I've seen you on the Bitcoin-X mailing list, where
> these issues have been mostly worked out:
>
> https://groups.google.com/forum/#!forum/bitcoinx
>
> Have you seen the padded order-based coloring scheme worked out here?
>
> https://github.com/bitcoinx/colored-coin-tools/wiki/colored_coins_intro
>
> Kind regards,
> Mark Friedenbach
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
[-- Attachment #2: Type: text/html, Size: 4176 bytes --]
next prev parent reply other threads:[~2014-04-07 9:50 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 [this message]
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
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=CABbpET_JFceNhRkxSZMyiTxkkYr2MvQVob7o4juEsPj4wo8e8g@mail.gmail.com \
--to=flavien.charlon@coinprism$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mark@monetize$(echo .)io \
/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