public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Flavien Charlon <flavien.charlon@coinprism•com>
To: "Jorge Timón" <jtimon@monetize•io>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Feedback request: colored coins protocol
Date: Mon, 7 Apr 2014 20:26:07 +0100	[thread overview]
Message-ID: <CABbpET8DaEKbafX6Cju_e+ygeV1WDf_LXQKU6tTofh32R9XM=Q@mail.gmail.com> (raw)
In-Reply-To: <CAC1+kJPBH85p8Mgu0_7+1JxizgX19a-HWWF+38BLA7DZ4Ldd6g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2279 bytes --]

An IOU written in a gold plate sure makes no sense. I see what you are
saying, the inconvenience comes from the fact that the buyer has to buy
some amount of BTC at the same time as he buys a share.

That's why I was making the point that you could have a colored coin
representing a single share, a different colored coin representing 10
shares, and another one representing 100 shares (like the different
denominations of dollar bills). Assuming you have a proper application
layer/UI that can hide this from the user, the need for padding is greatly
reduced. My opinion is that the protocol should do the minimum required and
remain as simple as possible. If a proper UI can work around this, then it
might not be worth complicating the protocol for this. Also, the dust rule
may disappear all together one day (it's already been slashed heavily to
540 satoshis), at which point we'll be left with a useless padding
parameter. It's easier to add something when you need it than to remove it.

But I am posting here to see how people feel about this, and I see you are
on the opinion that satoshi_value and color_value should have a degree of
freedom between each other. Thanks for the feedback.


On Mon, Apr 7, 2014 at 7:23 PM, Jorge Timón <jtimon@monetize•io> wrote:

> On 4/7/14, Flavien Charlon <flavien.charlon@coinprism•com> wrote:
> > Ok, I guess I'm not using the proper terminology. It would be listed on
> the
> > "Asset" section of the company's balance sheet, is what I meant.
>
> No, it's an asset for the owner of the share, not the company, just
> like the gold plates are not assets for the company when someone else
> holds them.
> What you're doing is getting less capital for the company due to the
> money that is going to pay the gold costs.
> Are you rising capital or selling gold?
> It doesn't make sense to do both at once.
> You need money, why would you spend money on gold before asking for
> other people's money to build your company?
> Investors will appreciate the convenience of being able to buy shares
> of your company and gold separately (or not buy gold at all).
>
> It may even be more clear for other use cases different than stocks.
> Does an IOU written in a gold plate make sense to you?
>

[-- Attachment #2: Type: text/html, Size: 2787 bytes --]

  reply	other threads:[~2014-04-07 19:26 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 [this message]
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='CABbpET8DaEKbafX6Cju_e+ygeV1WDf_LXQKU6tTofh32R9XM=Q@mail.gmail.com' \
    --to=flavien.charlon@coinprism$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=jtimon@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