Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <alex.mizrahi@gmail.com>) id 1WXFgo-0004oQ-A8
	for bitcoin-development@lists.sourceforge.net;
	Mon, 07 Apr 2014 19:58:42 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.216.54 as permitted sender)
	client-ip=209.85.216.54; envelope-from=alex.mizrahi@gmail.com;
	helo=mail-qa0-f54.google.com; 
Received: from mail-qa0-f54.google.com ([209.85.216.54])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WXFgn-0001nd-JP
	for bitcoin-development@lists.sourceforge.net;
	Mon, 07 Apr 2014 19:58:42 +0000
Received: by mail-qa0-f54.google.com with SMTP id w8so6502679qac.13
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 07 Apr 2014 12:58:36 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.224.172.131 with SMTP id l3mr18159536qaz.57.1396900716049;
	Mon, 07 Apr 2014 12:58:36 -0700 (PDT)
Received: by 10.96.77.38 with HTTP; Mon, 7 Apr 2014 12:58:35 -0700 (PDT)
In-Reply-To: <CABbpET8DaEKbafX6Cju_e+ygeV1WDf_LXQKU6tTofh32R9XM=Q@mail.gmail.com>
References: <CABbpET96CboPcQeV-nKXv-CeaPiwpTKVUB_ioGPB2s3_5Y7bnQ@mail.gmail.com>
	<5341E1FF.7080204@monetize.io>
	<CABbpET_JFceNhRkxSZMyiTxkkYr2MvQVob7o4juEsPj4wo8e8g@mail.gmail.com>
	<CAC1+kJMpEetKdpKs-OaFGvnBwi6-Pj8ycJ77cJzHOTk_jUPw=g@mail.gmail.com>
	<CABbpET-S5ahuQVcBaJZGyvFMS1=RU2mJZUAmECBKhFOFu6B6EA@mail.gmail.com>
	<5342BEE0.3050204@monetize.io>
	<CABbpET8Qbvhb47ZJX4EVh4673_ic9UwpMdMyZbsHay9F2zTj9Q@mail.gmail.com>
	<CAC1+kJPBH85p8Mgu0_7+1JxizgX19a-HWWF+38BLA7DZ4Ldd6g@mail.gmail.com>
	<CABbpET8DaEKbafX6Cju_e+ygeV1WDf_LXQKU6tTofh32R9XM=Q@mail.gmail.com>
Date: Mon, 7 Apr 2014 22:58:35 +0300
Message-ID: <CAE28kURu7-OgY6vN0az6rQUGpChK76ZQL9_eL1J4j-HZOqhRYA@mail.gmail.com>
From: Alex Mizrahi <alex.mizrahi@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=047d7b673fb6f7796104f6794a2d
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(alex.mizrahi[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1WXFgn-0001nd-JP
Subject: Re: [Bitcoin-development] Feedback request: colored coins protocol
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 07 Apr 2014 19:58:42 -0000

--047d7b673fb6f7796104f6794a2d
Content-Type: text/plain; charset=ISO-8859-1

This is beyond ridiculous...

Color kernel which works with padding is still quite simple. I think we
have extra 10-50 lines of code to handle padding in coloredcoinlib.
Essentially we have a couple of lines like this :

    value_wop = tx.outputs[oi].value - padding

(value_wop means "value without padding").
And then we have like 10 lines of code which selects padding for a
transaction.

That's not a lot of extra complexity. And it solves the problem once and
for all.

What you propose instead: "a different colored coin representing 10 shares,
and another one representing 100 shares (like the different denominations
of dollar bills)"  is much more complex, and it won't work:

Suppose you have $100 coin, as a single coin.
How do you send $54.23?
That's simply impossible.

So you'd rather push complexity to higher levels (and create inconvenience
for end users, as you admitted yourself) than add 10-50 lines of code to
color kernel?
I just do not understand this.

But I'm not going to argue. I already wrote everything which I could write
on this topic.

--047d7b673fb6f7796104f6794a2d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra">This is beyond ridiculous...</d=
iv><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Color ke=
rnel which works with padding is still quite simple. I think we have extra =
10-50 lines of code to handle padding in coloredcoinlib. Essentially we hav=
e a couple of lines like this :<br>
<br>=A0 =A0 value_wop =3D tx.outputs[oi].value - padding</div><div class=3D=
"gmail_extra"><br></div><div class=3D"gmail_extra">(value_wop means &quot;v=
alue without padding&quot;).</div><div class=3D"gmail_extra">And then we ha=
ve like 10 lines of code which selects padding for a transaction.=A0</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">That&#39;s =
not a lot of extra complexity. And it solves the problem once and for all.<=
/div><div class=3D"gmail_extra"><br></div><div>What you propose instead: &q=
uot;<span style=3D"font-family:arial,sans-serif;font-size:12.80000019073486=
3px">a different colored coin representing 10 shares, and another one repre=
senting 100 shares (like the different denominations of dollar bills)&quot;=
 =A0</span><span style=3D"font-family:arial,sans-serif;font-size:12.8000001=
90734863px">is much more complex, and it won&#39;t work:</span></div>
<div><span style=3D"font-family:arial,sans-serif;font-size:12.8000001907348=
63px"><br></span></div><div><span style=3D"font-family:arial,sans-serif;fon=
t-size:12.800000190734863px">Suppose you have $100 coin, as a single coin.=
=A0</span></div>
<div><span style=3D"font-family:arial,sans-serif;font-size:12.8000001907348=
63px">How do you send $54.23?</span></div><div><span style=3D"font-family:a=
rial,sans-serif;font-size:12.800000190734863px">That&#39;s simply impossibl=
e.</span></div>
<div><br></div><div>So you&#39;d rather push complexity to higher levels (a=
nd create inconvenience for end users, as you admitted yourself) than add 1=
0-50 lines of code to color kernel?</div><div>I just do not understand this=
.</div>
<div><br></div><div>But I&#39;m not going to argue. I already wrote everyth=
ing which I could write on this topic.=A0</div><div><br></div></div>

--047d7b673fb6f7796104f6794a2d--