From: Jean-Pierre Rupp <root@haskoin•com>
To: Flavien Charlon <flavien.charlon@predictious•com>,
Alex Mizrahi <alex.mizrahi@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Feedback request: colored coins protocol
Date: Thu, 10 Apr 2014 15:28:29 +0100 [thread overview]
Message-ID: <5346AA8D.5000801@haskoin.com> (raw)
In-Reply-To: <CABbpET93YxPepKLHFKKabr6P7vpkRDOouVuo8zmWAf3FKc85Cg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1355 bytes --]
By deciding to use a decentralized network to hold your assets, it may
make more sense to emit less shares. Two billion shares backed by
coloured coins makes less sense than a more conservative number, like
10,000. That costs a negligible amount of money, at least until the day
when Bitcoin takes over the world and a satoshi becomes very expensive.
But it is irrelevant now.
If you have already created a massive amount of shares for your company,
then the only reasonable solution is for a coloured coin to represent a
bundle of shares as Flavien suggested. Some shareholder could emit
another coloured coin instrument with a genesis block based on a smaller
set of shares to trade among smaller investors unwilling to deal in
terms of the bundled shares.
We need to understand that coloured coins provide benefits, but also has
constraints that are not difficult to live with.
On 10/04/14 13:19, Flavien Charlon wrote:
> 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.
--
haskoin.com
[-- Attachment #1.2: 0xFF4BF34C.asc --]
[-- Type: application/pgp-keys, Size: 20568 bytes --]
[-- Attachment #1.3: root.vcf --]
[-- Type: text/x-vcard, Size: 240 bytes --]
begin:vcard
fn:Jean-Pierre Rupp
n:Rupp;Jean-Pierre
org:Haskoin
adr:;;;Dublin;;;Ireland
email;internet:root@haskoin•com
title:Co-Founder
tel;cell:+353862720509
x-mozilla-html:FALSE
url:http://haskoin.com/
version:2.1
end:vcard
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]
next prev parent reply other threads:[~2014-04-10 14:45 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
2014-04-07 19:58 ` Alex Mizrahi
2014-04-10 12:19 ` Flavien Charlon
2014-04-10 14:28 ` Jean-Pierre Rupp [this message]
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=5346AA8D.5000801@haskoin.com \
--to=root@haskoin$(echo .)com \
--cc=alex.mizrahi@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=flavien.charlon@predictious$(echo .)com \
/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