From: Alex Mizrahi <alex.mizrahi@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Feedback request: colored coins protocol
Date: Mon, 7 Apr 2014 14:28:33 +0300 [thread overview]
Message-ID: <CAE28kURZB=huuvRPwOnVxSUzcez-pypDMpOzA3jiO7m2Q0pwsQ@mail.gmail.com> (raw)
In-Reply-To: <5341E1FF.7080204@monetize.io>
[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]
>
> Have you seen the padded order-based coloring scheme worked out here?
>
> https://github.com/bitcoinx/colored-coin-tools/wiki/colored_coins_intro
Just to clarify, a variant of padded order-based coloring called epobc is
already implemented in coloredcoinlib (which is used by
ngcccbase/ChromaWallet). It isn't document yet, however.
The idea is to use the otherwise unused nSequence field of first input to
specify padding and differentiate between genesis and transfer transactions.
Padding can be chosen for each transaction individually and can be set to
zero.
Python code is here (I recommend waiting for documentation, though):
https://github.com/bitcoinx/ngcccbase/blob/master/coloredcoinlib/colordef.py#L262
It is able to work with transactions with multiple colored and uncolored
outputs, particularly, p2ptrade transactions.
Examples of p2ptrade transactions on mainnet:
https://blockchain.info/tx/8c1926f2e3527153bf06e8ab2c8a417aad3d8e6cd993a4350efbb4050ab961fa
https://blockchain.info/tx/f85b6213939c9cbc14538dd24838061179cac2485f50be20a974b819a85e5ee9(It
looks quite a bit weird, I know.)
[-- Attachment #2: Type: text/html, Size: 1975 bytes --]
prev parent reply other threads:[~2014-04-07 11:28 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
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 [this message]
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='CAE28kURZB=huuvRPwOnVxSUzcez-pypDMpOzA3jiO7m2Q0pwsQ@mail.gmail.com' \
--to=alex.mizrahi@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
/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