Asset Verification

Social Verification

At the moment the colored coins implementation supports asset verification by linking to a social media profile on one of the following platforms:

• Twitter
• Facebook
• Github

Twitter

• You need the twitter handle of your twitter account @your_twitter_handle
• Add the following element under the asset metadata verifications key

{	
	"social":{		
		"twitter":{			
			"username":"your_twitter_handle"
		},
	}
}

• After the asset is issued, grab the asset id (say it is U3uPyQeyNRafPy7popDfhZui8Hsw98B5XMUpP) and tweet the following text, making sure that the asset ID is used as a hashtag:

Verifying issuance of colored coins asset with ID #U3uPyQeyNRafPy7popDfhZui8Hsw98B5XMUpP

Facebook

• Log in to your facebook account
• On the top right corner expand the menu and click on "Create Page"

• Select the appropriate category
• Considering that this page should be dedicated to posting asset endorsment messages, you should probably name it properly and consider attaching an image and an appropriate description
• Now that you have created the page, click on the "Settings" button

• On the setting page, disable visitor posts

• Grab the page ID from the url. The URL looks something like:

	https://www.facebook.com/Foobarbuzzquaxx-705379359593101/	

The page ID is the number at the end of the URL, in the above case it is 705379359593101

• Add the following element under the asset metadata verifications key, for example

{	
	"social":{		
		"facebook":{
			"page_id": 705379359593101					
		}
	}
}

• After the asset is issued, grab the asset id (say it is U3uPyQeyNRafPy7popDfhZui8Hsw98B5XMUpP) and post on that page the following text:

	Verifying issuance of colored coins asset with ID #U3uPyQeyNRafPy7popDfhZui8Hsw98B5XMUpP

Github

• Create a PUBLIC gist for asset verifications
• grab the gist_id from the url, e.g. https://gist.github.com/username/1d325dd9d1a74133bec3
• Add the following element under the asset metadata verifications key

{
	"social":{	
		"github":{			
			"gist_id":"1d325dd9d1a74133bec3"
		}
	}
}	

• For each asset that you want to verify (e.g. asset ids U3uPyQeyNRafPy7popDfhZui8Hsw98B5XMUpP and LKUYHRCMbqUNgfNCGFnXv1AvB5Pv8Lkk2EjoF) add a line to the gist like so:

...
Verifying issuance of colored coins asset with ID #U3uPyQeyNRafPy7popDfhZui8Hsw98B5XMUpP
Verifying issuance of colored coins asset with ID #LKUYHRCMbqUNgfNCGFnXv1AvB5Pv8Lkk2EjoF
...

Domain Verification

• Place a text file on your server behind httpS
• Let's say the path to the file is https://www.yourcompany.com/assets.txt
• Add the following element under the asset metadata verifications key

{	
	"domain":{
		"url":"https://www.yourcompany.com/assets.txt"		
	}
}

• If The file is not directly under the root of the website https://www.yourcompany.com/path/to/file/filename.txt you should use

{	
	"domain":{
		"url":"https://www.yourcompany.com/path/to/file/filename.txt"		
	}
}

For example:

{	
	"domain":{
		"url":"https://www.example.com/digital_assets/assets.txt"		
	}
}

• For each asset that you want to verify (e.g. asset ids U3uPyQeyNRafPy7popDfhZui8Hsw98B5XMUpP and LKUYHRCMbqUNgfNCGFnXv1AvB5Pv8Lkk2EjoF) add the following two lines to the assets text file

...
U3uPyQeyNRafPy7popDfhZui8Hsw98B5XMUpP
LKUYHRCMbqUNgfNCGFnXv1AvB5Pv8Lkk2EjoF
...

You can check that the results of this check match what you get from ssl_checker, or digicert For example, surprisingly enough "https://www.target.com" doesn't pass the verification, and indeed, we get the same result from ssl checker.