digital_asset_verification

Installation

	sudo chmod -R 777 domain/certs
	sudo chmod 777 domain/*.sh

Setup

Github

Generate API token

• Create an account on Github
• In the top right corner of any page, click your profile photo, then click Settings.
• In the user settings sidebar, click Personal access tokens.
• Click Generate new token and name it.
• Use the default scope, this is enough to read gists which is all we need.
• Copy the token to your clipboard and save it to the file social/secrets.php in the following format:

# social/secrets.php
<?php
	define('GITHUB_PERSONAL_TOKEN', '*****************');
?>

• This token is limited to 5000 calls/hour.

Facebook

Generate API token

• Creat an account and sign in
• Navigate to https://developers.facebook.com/
• Click on the My Apps tab
• Register as a developer
• Click again on the My Apps tab
• Create a new application
• Select the www option and click on the top left skip and create App ID
• Display Name: coloredcoins
• Namespace:
• Category: Finance
• Answer the kaptcha and create app id
• Navigate to the Tools & Support tab and select Access Token Tools
• Save the app token in a file social/secrets.php in the following format:

# social/secrets.php
<?php
	define('FACEBOOK_APP_TOKEN', '**************|************');
?>

Twitter

Generate API tokens

• Creat a Twitter account and sign in
• You must add your mobile phone to your Twitter profile before creating an application
• Navigate to https://apps.twitter.com
• Create a new application
• Website: http://colu.co
• Callback URL:
• Navigate to the "Keys and Access Tokens" tab
• Save the following secrets in a file social/secrets.php in the following format:

# social/secrets.php
<?php
  define('TWITTER_CONSUMER_KEY','***********');
  define('TWITTER_CONSUMER_SECRET','*************');
  define('TWITTER_OAUTH_ACCESS_TOKEN','****************');
  define('TWITTER_OAUTH_ACCESS_TOKEN_SECRET','****************');
?>

Usage

Social

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
...

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

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

Domain

• 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 a line to the text file

...
Verifying issuance of colored coins asset with ID #U3uPyQeyNRafPy7popDfhZui8Hsw98B5XMUpP
Verifying issuance of colored coins asset with ID #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.