public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
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 16:19:20 +0100	[thread overview]
Message-ID: <CABbpET8Qbvhb47ZJX4EVh4673_ic9UwpMdMyZbsHay9F2zTj9Q@mail.gmail.com> (raw)
In-Reply-To: <5342BEE0.3050204@monetize.io>

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

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.


On Mon, Apr 7, 2014 at 4:06 PM, Mark Friedenbach <mark@monetize.io> wrote:

> Flavien, capital is wealth or resources available for the stated purpose
> of the company. These bitcoins represent nothing more than a speculative
> floor owned by the investors, not the company.
>
> On 04/07/2014 07:00 AM, Flavien Charlon wrote:
> > Jorge, they'd have to be. Otherwise, assuming the price of the share
> > goes low enough, you could buy a share of the company, melt the gold
> > plate, and sell it for a profit. If the gold is part of the capital of
> > the company, the cheapest a share can be is the price of the gold on
> > which the stock certificate is printed.
> >
> > This is why I think the importance of padding with colored coins is
> > overblown.
> >
> >
> > On Mon, Apr 7, 2014 at 1:12 PM, Jorge Timón <jtimon@monetize.io
> > <mailto:jtimon@monetize.io>> wrote:
> >
> >     On 4/7/14, Flavien Charlon <flavien.charlon@coinprism.com
> >     <mailto:flavien.charlon@coinprism.com>> wrote:
> >     > 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.
> >
> >     This doesn't make much sense to me.
> >     If you print shares on gold plates instead of paper, is that gold
> >     "part of the capital of the company"? I don't think so.
> >
> >
>

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

  reply	other threads:[~2014-04-07 15:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-06 20:59 [Bitcoin-development] Feedback request: colored coins protocol 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 [this message]
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=CABbpET8Qbvhb47ZJX4EVh4673_ic9UwpMdMyZbsHay9F2zTj9Q@mail.gmail.com \
    --to=flavien.charlon@coinprism.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=mark@monetize.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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