Task 2 of 4 Detailed Instructions:
1. Examine the page at
https://boards.4channel.org/vip/thread/99136#p99161 which has been cc'd to the zenoribbon.freeforums.net claimchain ledger.
It will have this text:
CONTAINERIZATION
CONTAINER
ZR 0 to 1
CONTENT IDENTIFIER: Zenoribbon of Rainbow Road
CONTAINER IDENTIFIER: d9533c95c6a0d03e634b124f90c08c58800d3fb368b7f392ac698c66f140a6f7adf84ab27fa4f36 064f9817f17a1e578ee0d25e5c3fdb2c593a1e3f035c02b60
Hash of Containerization SHA-512: a2041a22eec1a991d91fb71c40f6e88549ca64008f6df59834ad7b32e486221fb3f6db7f53738d6
9bd5d340a12b93cb96debcb819b6034d735acfd2d40d06a7c
Hash Signature: JO+1T3LpvwQRAJ3F0wgx2+5774fO0MewdreycjDLFGAPbJlLI5+9uW4LRFwUKTtQ0YEnP2v/iBC/tqtxK6iVAg==
This is a claim that Zenoribbon is being placed in a container which can be transacted over the Public Settlement Network (PSN), which can only be honored if done by the rightful owner. So, Check to see if there are any other earlier tranfers of Zenoribbon using a basic internet search. If not, the transaction is potentially valid.
2. Verify that the "Hash of Containerization" matches the text beginning "CONTAINERIZATION" and ending "...b60"
Unlike the previous hashes in task 1, this hash is in Base64 encoding and so the TweetNaCl hash won't match. However, the more common version will work.
A good SHA-512 Base64 hash tool can be found here:
https://emn178.github.io/online-tools/sha512.htmlIn the input box, the hash from above beginning "CONTAINERIZATION" and ending "...b60"
Remove any spaces in the hash because copying and pasting from a browser sometimes adds spaces that ruin the hash.
The output should match the hash as claimed beginning "a204..." for the containerization to be valid. If valid, then you can go to the next step.
3. Verify that the hash signature matches the owner of "Zenoribbon of Rainbow Road" which is indicated by this public key according to your previous evaluation:
Claimant Sharing Key: hqXdZnrTvicitWv4V/LH/9qA3nUMcl5PIbbdgclZ9cY=
A good signature kit can be found at:
https://tweetnacl.js.org/#/signClick on the verify tab.
Enter the sharing Key as the signature public key.
Enter the Hash signature from above "JO+... Ag==" in the signature line.
Once again, delete any spaces added by your browser.
Enter the "Hash of Containerization" hash as the message. In this case that is the above hash beginning "a204" ending "...a7c"
Click Verify. Hopefully the statement verifies correctly!
4. If everything is valid and there are no conflicting claims found by an internet search, then you can honor the statement using the same signature signing process used in step 1:
Create the evaluation statement as:
Evaluation:
Honor to: 0nP5UpmI3+m9Uk1qf8fMQK3drWwS7p4+sLSZu7iepnFv1rHUJElJqDjQtYJLfWM/jW1e/LwdLn69g1bdLvuyCQ==
Hash of Evaluation Statement: (hash of honor statement above goes here)
Signature: (signature of the hash in the previous line above)
Public Key: (insert your public key here)
a. Hash the text starting with "Evaluation" and ending "...CQ==" using a hash tool such as the linked page above.
b. Sign the hash such as by using
https://tweetnacl.js.org/#/signYou should still have your public and private key from the previous task. If you don't have that key, generate a new one with the "random" button and save both the private and public keys it for future use.
Paste your private key to the private key field.
In the message field, put the line generated from hashing your evaluation statement, which may be this:
8e549d1b367600979314c83a788bf1215223bf6ac8b1d81fe19862e141151928c5e0a20e1a01dfc
dc57e7723672825648cd22a8c9adddb7283d80ff951eb3e46
Then click sign.
Paste the resulting signature in place of "(signature of the hash in the previous line above)" in your evaluation statement.
c. Paste your public key in place of "(insert your public key here)" in your evaluation statement.
5. Post your evaluation statement to this thread. Done! As always, don't be afraid to loosely interpret these instructions and do things according to your personal preferences.