<p>Just wanted to add that Colu has been working on this problem since at least 2016, so i would dive deeper into their repositories, if you haven't already:</p>

<p><a href="https://github.com/Colored-Coins" rel="nofollow noreferrer">https://github.com/Colored-Coins</a></p>

<p>the most recent information I can find on these efforts is:</p>

<p><a href="https://bitcoinexchangeguide.com/coloredcoins/" rel="nofollow noreferrer">https://bitcoinexchangeguide.com/coloredcoins/</a></p>

CC BY-SA 4.0
2019-06-08T18:12:39.000Z
2019-06-08T18:12:39.000Z
InfoMiner
<p>I can only answer the first part of your question as I am not aware of the implementation details other than that they use some form of "pay to contract script". </p>

<p>BHB-networks with Alekos Filini are working on the RGB protocol (which are colored coins) for Bitcoin. There is an <a href="https://github.com/rgb-org/spec" rel="nofollow noreferrer">rgb-spec</a> which also has a section about Lightning but it is not very extensive. The first page says there are c Lightning and lnd forkes but I believe that is work in progress. </p>

CC BY-SA 4.0
2019-01-09T21:08:39.517Z
2019-01-09T21:21:56.583Z
2019-01-09T21:21:56.583Z
Rene Pickhardt
<p>Coloured coins work by adding metadata to the a transaction output with an <code>OP_RETURN</code> output script. The metadata describes a transaction of the coloured coin, but is ignored by the Bitcoin script interpreter.</p>

<p>This allows any state-transition protocol to be implemented on top of Bitcoin, with a state-change fee being paid in Bitcoin for confirmation, but validation rules which are enforced by a separate coloured coin server, parsing the Bitcoin strong chain for valid metadata.</p>

<p>Transferring such a coloured coin across a single payment channel requires both channel peers being able to sign Bitcoin channel states with coloured coin transactions represented in <code>OP_RETURN</code> outputs. A channel state update can be in both Bitcoin, since the states are captured as Bitcoin transactions, and in the metadata, representing a balance change of the coloured asset.</p>

<p>Routing a coloured coin across multiple hops just requires the first and last routing segment balances to denominated in "colour coins", so that the colour coin can be delivered in the channel balance at your destination. An intermediary who is routing from a mSat denominated channel to one which is denominated in your coloured coin along this path would be necessarily be agreeing to an exchange of the two coins.</p>

CC BY-SA 4.0
2019-01-10T08:13:58.513Z
2019-01-10T10:36:59.623Z
2019-01-10T10:36:59.623Z
James C.
<p>I'm trying to research how tokens or colored coins would work on top of bitcoin lightning channels / nodes. Has any project tried to build token issuance on top of  the Bitcoin lightning network? How would that work exactly? </p>

<lightning-network><colored-coins><tokens>
Implementation of tokens/assets/colored coins on top of bitcoin lighning nodes / channels?
Patoshi パトシ
# Implementation of tokens/assets/colored coins on top of bitcoin lighning nodes / channels?

(Asked by: username_0 on 2019-01-09)

I'm trying to research how tokens or colored coins would work on top of bitcoin lightning channels / nodes. Has any project tried to build token issuance on top of the Bitcoin lightning network? How would that work exactly?

**Tags:** lightning-network, colored-coins, tokens


---

## 3 answers

### Answer by username_1 on 2019-06-08. Score: 1

Just wanted to add that Colu has been working on this problem since at least 2016, so i would dive deeper into their repositories, if you haven't already:

<https://github.com/Colored-Coins>

the most recent information I can find on these efforts is:

<https://bitcoinexchangeguide.com/coloredcoins/>


---

### Answer by username_2 on 2019-01-09. Score: 0

I can only answer the first part of your question as I am not aware of the implementation details other than that they use some form of "pay to contract script".

BHB-networks with Alekos Filini are working on the RGB protocol (which are colored coins) for Bitcoin. There is an [rgb-spec](https://github.com/rgb-org/spec) which also has a section about Lightning but it is not very extensive. The first page says there are c Lightning and lnd forkes but I believe that is work in progress.


---

### Answer by username_3 on 2019-01-10. Score: 0

Coloured coins work by adding metadata to the a transaction output with an `OP_RETURN` output script. The metadata describes a transaction of the coloured coin, but is ignored by the Bitcoin script interpreter.

This allows any state-transition protocol to be implemented on top of Bitcoin, with a state-change fee being paid in Bitcoin for confirmation, but validation rules which are enforced by a separate coloured coin server, parsing the Bitcoin strong chain for valid metadata.

Transferring such a coloured coin across a single payment channel requires both channel peers being able to sign Bitcoin channel states with coloured coin transactions represented in `OP_RETURN` outputs. A channel state update can be in both Bitcoin, since the states are captured as Bitcoin transactions, and in the metadata, representing a balance change of the coloured asset.

Routing a coloured coin across multiple hops just requires the first and last routing segment balances to denominated in "colour coins", so that the colour coin can be delivered in the channel balance at your destination. An intermediary who is routing from a mSat denominated channel to one which is denominated in your coloured coin along this path would be necessarily be agreeing to an exchange of the two coins.


---

