public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Danny Thorpe <danny.thorpe@gmail•com>
To: Telephone Lemien <lemientelephone@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin transaction
Date: Tue, 12 May 2015 11:40:31 -0700	[thread overview]
Message-ID: <CAJN5wHVpHo4Yep3goUbMtbtxa8aWBtwdPegtHF8wTq6XxYSSww@mail.gmail.com> (raw)
In-Reply-To: <CAL6tyga6HyYJkhbS+yCDTkNe7LDxGxcXzbwgfjQmKs20gAGPHA@mail.gmail.com>

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

See the Open Assets protocol specification for technical details on how a
colored coin (of the Open Asset flavor) is represented in a bitcoin
transaction.

https://github.com/OpenAssets/open-assets-protocol

http://www.CoinPrism.com also has a discussion forum where some colored
coin devs hang out.

http://www.coinprism.info is a blockchain explorer that is colored-coin
aware.

On Tue, May 12, 2015 at 2:54 AM, Telephone Lemien <lemientelephone@gmail•com
> wrote:

> Thank You,
> I know this, but I want to have mores details in the inputs/outputs, or in
> the script of input/output and how i will proceed in the code.
> Thanks for all replaying
>
> 2015-05-12 11:47 GMT+02:00 Patrick Mccorry (PGR) <
> patrick.mccorry@newcastle•ac.uk>:
>
>>  There is no difference to the transaction as far as im aware – just the
>> inputs / outputs have a special meaning (and should have a special order).
>> So you can track 1 BTC throughout the blockchain and this 1 BTC represents
>> my asset. Someone may give a more useful answer.
>>
>>
>>
>> *From:* Telephone Lemien [mailto:lemientelephone@gmail•com]
>> *Sent:* 12 May 2015 10:45
>> *To:* Bitcoin Dev
>> *Subject:* [Bitcoin-development] Bitcoin transaction
>>
>>
>>
>> Hello evry body,
>>
>> I want to know what is the difference between a bitcoin transaction and
>> colored coins transaction technically.
>>
>> Thanks
>>
>
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>

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

      reply	other threads:[~2015-05-12 18:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-12  9:45 Telephone Lemien
     [not found] ` <DB5PR07MB09193865EE13BEF6ABD2CC79B5DA0@DB5PR07MB0919.eurprd07.prod.outlook.com>
2015-05-12  9:54   ` Telephone Lemien
2015-05-12 18:40     ` Danny Thorpe [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=CAJN5wHVpHo4Yep3goUbMtbtxa8aWBtwdPegtHF8wTq6XxYSSww@mail.gmail.com \
    --to=danny.thorpe@gmail$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=lemientelephone@gmail$(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