From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) 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 ; 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: References: <5341E1FF.7080204@monetize.io> <5342BEE0.3050204@monetize.io> Date: Mon, 7 Apr 2014 22:58:35 +0300 Message-ID: From: Alex Mizrahi 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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
This is beyond ridiculous...

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 :

=A0 =A0 value_wop =3D tx.outputs[oi].value - padding

(value_wop means "v= alue without padding").
And then we ha= ve like 10 lines of code which selects padding for a transaction.=A0

That's = not a lot of extra complexity. And it solves the problem once and for all.<= /div>

What you propose instead: &q= uot;a different colored coin representing 10 shares, and another one repre= senting 100 shares (like the different denominations of dollar bills)"= =A0is much more complex, and it won't work:

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

So you'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?
I just do not understand this= .

But I'm not going to argue. I already wrote everyth= ing which I could write on this topic.=A0

--047d7b673fb6f7796104f6794a2d--