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-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WYE44-0001c0-4i for bitcoin-development@lists.sourceforge.net; Thu, 10 Apr 2014 12:26:44 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of pixodegames.com designates 209.85.215.44 as permitted sender) client-ip=209.85.215.44; envelope-from=flavien.charlon@pixodegames.com; helo=mail-la0-f44.google.com; Received: from mail-la0-f44.google.com ([209.85.215.44]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WYE42-0000ae-QP for bitcoin-development@lists.sourceforge.net; Thu, 10 Apr 2014 12:26:44 +0000 Received: by mail-la0-f44.google.com with SMTP id c6so2258391lan.31 for ; Thu, 10 Apr 2014 05:26:36 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=5WIezqdO0CtakU3Zv3w/AFpbmrAAsU8cBWpC5NXGVVY=; b=IvJ+RGj3Rg37iAsrF7mzAuchk3NGq4WawZH2Vt+Zow//hVhOHabMzhEGNZZTN1unng O1DQN9q8/n/3wVw0pJD48lhD3WlBCym2+nMDN9n1CS5Y7/NOrccIFBVhofyKHyg8j3Ko +zdkj2VtMjQde4hLumMIkkinDxgUiDHHH+BJji6Cec11wepcltGUMJ4aNUpSWIVzXjXr F4L3tttDzQUdxXTgJvrbptgisPkFJjhvc7bko7WkXAdrM+2fXIOXmqBxT4V+cSn9zDQ5 VAptK2+tGk8sEyXgv7V4qsKUWc6h8zC/Q/fPMAbFm5t55Ft6leDkhBoS7wKJcRh8WFWI a6Nw== X-Gm-Message-State: ALoCoQnMxh4sG2K1lgv4ZWfvKKaPC8CNmJz/d8xPqklwm3eaMuGCnmK2x/Sm5pnDtoVdg0sqzqwr X-Received: by 10.112.128.231 with SMTP id nr7mr11578785lbb.9.1397132399030; Thu, 10 Apr 2014 05:19:59 -0700 (PDT) Received: from mail-la0-f52.google.com (mail-la0-f52.google.com [209.85.215.52]) by mx.google.com with ESMTPSA id jp6sm3270123lbc.15.2014.04.10.05.19.58 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 10 Apr 2014 05:19:58 -0700 (PDT) Received: by mail-la0-f52.google.com with SMTP id ec20so2258932lab.11 for ; Thu, 10 Apr 2014 05:19:58 -0700 (PDT) X-Received: by 10.112.56.148 with SMTP id a20mr1389251lbq.44.1397132398422; Thu, 10 Apr 2014 05:19:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.114.185.230 with HTTP; Thu, 10 Apr 2014 05:19:18 -0700 (PDT) X-Originating-IP: [2a01:110:8:1003:494e:7ce7:f38e:659a] In-Reply-To: References: <5341E1FF.7080204@monetize.io> <5342BEE0.3050204@monetize.io> From: Flavien Charlon Date: Thu, 10 Apr 2014 13:19:18 +0100 Message-ID: To: Alex Mizrahi Content-Type: multipart/alternative; boundary=001a113393c84ffc1f04f6af3ce0 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 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: 1WYE42-0000ae-QP Cc: bitcoin-development@lists.sourceforge.net 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: Thu, 10 Apr 2014 12:26:44 -0000 --001a113393c84ffc1f04f6af3ce0 Content-Type: text/plain; charset=ISO-8859-1 Thanks for the valuable feedback. I see there is a strong concern with requiring a large BTC capital for issuing coloring coins, so I am now in the process of modifying the specification to address that. I will post an update when this is finished. By the way, padding doesn't solve the issue entirely (issuing 10 billion shares sill takes you 100 BTC, even with padding and 1 satoshi = 1 share), so I am going for the solution where the asset quantity of every output is explicitly encoded in the OP_RETURN output. That way, whether you are issuing 1 share or 100 trillions, you never need to pay more than 540 satoshis. On Mon, Apr 7, 2014 at 8:58 PM, Alex Mizrahi wrote: > 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. > > > > ------------------------------------------------------------------------------ > Put Bad Developers to Shame > Dominate Development with Jenkins Continuous Integration > Continuously Automate Build, Test & Deployment > Start a new project now. Try Jenkins in the cloud. > http://p.sf.net/sfu/13600_Cloudbees > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > > --001a113393c84ffc1f04f6af3ce0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Thanks for the valuable feedback. I see there is a st= rong concern with requiring a large BTC capital for issuing coloring coins,= so I am now in the process of modifying the specification to address that.= I will post an update when this is finished.

By the way, padding doesn't solve the issue entirel= y (issuing 10 billion shares sill takes you 100 BTC, even with padding and = 1 satoshi =3D 1 share), so I am going for the solution where the asset quan= tity of every output is explicitly encoded in the OP_RETURN output. That wa= y, whether you are issuing 1 share or 100 trillions, you never need to pay = more than 540 satoshis.


On Mon,= Apr 7, 2014 at 8:58 PM, Alex Mizrahi <alex.mizrahi@gmail.com>= wrote:
= This is beyond ridiculous...

Color kernel which works with padding is still quite simple. I think we hav= e extra 10-50 lines of code to handle padding in coloredcoinlib. Essentiall= y we have 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 differe= nt colored coin representing 10 shares, and another one representing 100 sh= ares (like the different denominations of dollar bills)" =A0is much more com= plex, and it won't work:

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

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


-----------------------------------------------------------------------= -------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.= sf.net/sfu/13600_Cloudbees
_________________________________________= ______
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment


--001a113393c84ffc1f04f6af3ce0--