That's a whole lot of talk from a creative writer. There are tons of alternatives that can do what you just described. Good luck tho!
Your skepticism is understandable. There's no creative writing going on here - just technical writing.
For example, here are syscoind's commands for registering as a certificate issuer as well as for issuing and transferring certificates, as well as examples (Please forgive the markdown formatting but this is straight from the repo and I'm too tired to strip it out at the moment):
##certificate commands
these commands deal with issuing and transferring certificates.
**certissuernew** <title> <data>
<title>: certificate title. max 255 chars.
<data>: certificate data, max 64 kB
**returns**
[
txid,
certissuerkey
]
**example:**
$ syscoind certissuernew "Nerd Academy - We Teach you the Art of Nerd" "This certificate issuer is used to generate certificate of accreditations for our students. These are lifetime certificate and not honored if transferred or stolen."
[
"76ac8fc00b06c722918e6702837077bb27cf56a384f12935f5b3d40c7b3efc62",
"d9d333abf5d9714f"
]
**certissueractivate** <certissuerkey>
<certissuerkey> certificate issuer key generated from certissuernew command.
**returns**
txid
**example:**
syscoind certissueractivate d9d333abf5d9714f
2088c50c7de00c30ed6e6ffa0661b18ad148cf8b8dcc5927ae844e58e2b78678
**certissuerupdate** <certissuerkey> <title> <data>
<certissuerkey> certificate key
<title>: certificate title. max 255 chars.
<data>: certificate data, max 64 kB
**returns**
txid
**example:**
**certnew** <certissuerkey> <destaddress> <title> <data>
<certissuerkey> certificate key
<destaddress> destination Syscoin address
<title>: certificate title. max 255 chars.
<data>: certificate data, max 64 kB
**returns**
[
txid,
certkey
]
**example:**
$ syscoind certnew d9d333abf5d9714f Scq4eMRi8aRZxJXWas5MW8uxYCtZZgkcT1 "Certificate of Nerd Master" "Owner has achieved Nerd Mastery."
[
"6b79eaf9c171fb92a5873f86e0b1069dbd79359b0f0cce14c201fc8fd2863587",
"d532408da773032a"
]
**certtransfer** <certkey> <destaddress>
<certkey>
<destaddress>
**returns**
**returns:**
**certissuerinfo** <certissuerkey>
**example:**
$ syscoind certissuerinfo d9d333abf5d9714f
{
"id" : "d9d333abf5d9714f",
"txid" : "6b79eaf9c171fb92a5873f86e0b1069dbd79359b0f0cce14c201fc8fd2863587",
"address" : "33h59NnTq48hgrFUXYBrpL6pGhgmE8Fdjk",
"expires_in" : 123029,
"title" : "Nerd Academy - We Teach you the Art of Nerd",
"data" : "This certificate issuer is used to generate certificate of accreditations for our students. These are lifetime certificate and not honored if transferred or stolen.",
"certificates" : [
{
"id" : "d532408da773032a",
"txid" : "6b79eaf9c171fb92a5873f86e0b1069dbd79359b0f0cce14c201fc8fd2863587",
"height" : "483",
"time" : "1396857128",
"fee" : 0.00000000,
"title" : "Certificate of Nerd Master",
"data" : "Owner has achieved Nerd Mastery."
}
]
}
**certinfo** <certkey>
**example:**
$ syscoind certinfo d532408da773032a
{
"id" : "d532408da773032a",
"txid" : "6b79eaf9c171fb92a5873f86e0b1069dbd79359b0f0cce14c201fc8fd2863587",
"height" : "483",
"time" : "1396857128",
"fee" : 0.00000000,
"title" : "Certificate of Nerd Master",
"data" : "Owner has achieved Nerd Mastery.",
"issuer" : {
"id" : "d9d333abf5d9714f",
"txid" : "6b79eaf9c171fb92a5873f86e0b1069dbd79359b0f0cce14c201fc8fd2863587",
"address" : "33h59NnTq48hgrFUXYBrpL6pGhgmE8Fdjk",
"expires_in" : 123029,
"title" : "Nerd Academy - We Teach you the Art of Nerd",
"data" : "This certificate issuer is used to generate certificate of accreditations for our students. These are lifetime certificate and not honored if transferred or stolen."
}
}
Those of you familiar with namecoin will immediately notice the similar command and info structures (well - except for maybe the nested data structures returned from certissuerinfo and certinfo.
By the way - I'm the lead developer of syscoin, and I appreciate the creative writing compliment! I've never had a summary feature description of one of my projects called that before. I wrote a good chunk of the pre-announcement, which is a summary reflection of the current implemented syscoin feature set. I'm working on a more extensive white paper now.. Thanks for looking!
