public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mark Friedenbach <mark@monetize•io>
To: Flavien Charlon <flavien.charlon@predictious•com>,
	 Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Feedback request: colored coins protocol
Date: Thu, 10 Apr 2014 09:59:00 -0700	[thread overview]
Message-ID: <5346CDD4.8050206@monetize.io> (raw)
In-Reply-To: <CABbpET93YxPepKLHFKKabr6P7vpkRDOouVuo8zmWAf3FKc85Cg@mail.gmail.com>

On 04/10/2014 05:19 AM, 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.

At this point, I don't think what you are doing is even colored coins
anymore. You might want to look into Counterparty or Mastercoin.



  parent reply	other threads:[~2014-04-10 16:59 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
2014-04-10 16:59                     ` Mark Friedenbach [this message]
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=5346CDD4.8050206@monetize.io \
    --to=mark@monetize$(echo .)io \
    --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