Community Update – 15.7.15

July 15, 2015
Getting started with Colored Coins from A-Z!

Many of you has been contacting us with various questions regarding the new implementation like: how to send assets to multiple addresses,
we have decided to create an even more detailed Getting Started Guide.

Here is a detailed example, using the Colored Coins API with NodeJS,
for the following use-case:

1. Create a new address.

2. Fund the address.

3. Issue 100 assets on this address.

4. Sign the issue transaction.

5. Broadcast the signed issue transaction on the blockchain.

6. View the issue assets on the blockchain.

7. Create 3 new addresses (‘address1’, ‘address2’, and ‘address3’).

8. Send 10 assets to ‘address1’, 20 assets to ‘address2’,
    and 30 assets to ‘address3’.

9. Sign the send transaction.

10. Broadcast the signed send transaction on the blockchain.

11. View the issue & send transaction on the blockchain,
     and see the asset holders info.

Colored Coins API example

Block Explorer update Block Explorer enables the issuer (or every new owner of an asset) to add more metadata, even after issuence, using a simple transaction.
This is the first time it is done. 
That’s why the architecture design was more complicated and challenging than ever –
because of the fact that it is more than just creating a single page for a single asset.  

For example: a ticketing company is issuing 100 movie tickets to a certain date. After selling the tickets, they are now adding to each ticket it’s seat and row number. In fact, they have really created 100 unique assets (with the same asset ID).

Finally, there is no one page for each single asset since theoretically,
every asset keeps adding more layers of unlimited metadata.
That’s why we have added some changes and we have a new asset page.


We are officially on Mainet

We must admit that moving to Mainet was a bit of a hassle this week.
Some of you may know, we are in the middle of a spam attack on the bitcoin Blockchain – at the moment, there are around 62K transactions in the mempool waiting for approval.

Our API enables you to set your fees rate for each transaction
(we recommend on 1000 satoshi fee until the DDOS is over).
In the case you have an important transaction you want recorded in a block, you can decide on whatever fee you are willing to pay to make it happen. protocol also supports Zero confirmation, so in terms of user experience (not security), even when there’s no immediate confirmation, the user is not affected.  


  • Tayyab Hussain

    I got an error while transfering assets with metadata..
    Error: Metadata upload has failed 628