CloudCoin Logo

Directory Services: V 5.5.2017

Purpose:

The purpose of the Directory Service API is to provide a backup system for a program (or user) to learn the names or IP addresses of the RAIDA servers so they can be contacted. The Directory Service may provide the RAIDA contact information in a different (and yet uninvented) format if convenient to the application. In other words, a separate, non-JSON service could easily be created. A dynamic RAIDA Directory is planned for the future but may not be necessary for years. THE DIRECTORY SERVICE HAS YET TO BE IMPLEMENTED.

 

For network 1, the default locations that can be tried first, before accessing the directory. The names are case insensitive. are:

 

https://RAIDA0.CloudCoin.Global

https://RAIDA1.CloudCoin.Global

...

https://RAIDA23.CloudCoin.Global

https://RAIDA24.CloudCoin.Global

 

For future networks (should network multiplication occur) the names of the servers will have a network extension such as RAIDA0Net2 through RAIDA24Net2 where Net2 means they are on network 2.

 

Default Names:

https://RAIDA0net2.CloudCoin.Global

https://RAIDA1net2.CloudCoin.Global

...

https://RAIDA23net2.CloudCoin.Global

https://RAIDA24net2.CloudCoin.Global

 

Directory Request:

Client uses HTTPS to GET the directory page located on different marketing servers. Note that directory uses extension-less urls.

 

Example of a Directory Request:

//www.cloudcoin.ch/service/directory  (This is not yet implemented as of 5/5/2017)

 

A test directgory can be found at:

//www.cloudcoin.co/servers.html

 

Directory Response:

Server returns a JSON string that describes the URLs of the RAIDAs, the status, the milliseconds required to contact, and a port to use.

 

Example of a Directory Response:

 

{

  "server": [

    {

     "name": "RAIDA0",

      "url": "RAIDA0.CloudCoin.Global",

      "bkurl": "RAIDA0.CloudCoin.ch",

      "status": "unknown",

      "ms": "0",

      "location":"USA",

      "img":"cloudcoin.global\/flags\/usa1.png",

      "protocol":"https",

      "port": "443"

    },

    {

      "name": "RAIDA1",

      "url": "212.120.69.50",

      "bkurl": "RAIDA1.CloudCoin.ch",

      "status": "ready",

      "ms": "230",

      "location":"Macedonia",

      "img":"cloudcoin.global\/flags\/macedonia.png",

      "protocol":"http",

      "port": "80"

    },

     //NOTE: RAIDA3 through RAIDA22 have been left out to save space

  {

      "name": "RAIDA23",

      "url": "RAIDA23.CloudCoin.Global",

      "bkurl": "RAIDA23.CloudCoin.ch",

      "status": "unknown",

      "ms": "0",

      "location":"USA",

      "img":"cloudcoin.global\/flags\/usa1.png",

      "protocol":"https",

      "port": "443"

    },

    {

      "name": "RAIDA24",

      "url": "RAIDA24.CloudCoin.Global",

      "bkurl": "RAIDA24.CloudCoin.ch",

      "status": "down",

      "ms": "0",

      "location":"Taiwan",

      "img":"cloudcoin.global\/flags\/twain.png",

      "protocol":"https",

      "port": "443"

    }

  ]

}

 

KEY

  • url:  The Fully Qualified Domain name of the Server
  • bkurl:  a backup URL in case the DNS of one goes down.
  • name: The name of the Server
  • status: When we have a dynamic system, this might tell the people that the server is down and why.
  • ms: Milliseconds. Time to echo (This could be used if have mirrors of the same server up in the future)
  • location: Where or who runs the RAIDA
  • img: An image file that can be associated with the RAIDA
  • protocol: http, or https. Could be something different in the future such as smtp, TFTP, FTP, sms
  • port: Port number. Usually 80 or 443

 

Rules:

The Directory Service may not respond if it is unavailable.

It is possible to add backup - or secondary - RAIDA by adding items with the same "name" to the directory. Then, RAIDA with the smallest ms could be contacted first.

The Directory may be cached in case it becomes unavailable or even hard-coded in an application as a backup for fault tolerance.

The values are case-insensitive and should be compared accordingly.

bkurl is the Backup URL in case name resolution fails for the url.

All the services use extension less urls.

Typically, the ms (milliseconds required to contact) and the status are to be determined by the client using the Echo Service.

The possible statuses are:

  • "unknown" because no attempt has been made to contact the RAIDA.
  • "ready" because an echo request was sent to the RAIDA and it came back "ready."
  • "error" because an echo request was sent to the RAIDA but there was an error.
  • "no_contact" because an echo request was sent to the RAIDA and it did not return any response.
  • "down" because the server is off-line for some reason.

 

 

 

 

 

 

Echo Service V 5.5.2017

Purpose:

The purpose of the echo API is to allow a program (or user) to establish that a RAIDA is ready to detect the authenticity of CloudCoins and how many milliseconds the contact requires.

 

The client sends the RAIDA an Echo Request and the RAIDA will respond with a Echo Response.

 

Echo Request:

Client uses HTTPS and GET method for the echo url located in the service folder on the RAIDA server.

 

Echo Request Example:

 

https://RAIDA0.CloudCoin.Global/service/echo

 

Echo Response Example:

Server returns a Response Object using JSON that describes the name of the server, the status, a message, and a timestamp:

 

{

 "server":"RAIDA0",

 "status":"ready",

 "message":"Up: Detection agent ready to detect authenticity.",

 "time":"2016-49-21 7:49:PM"

}

 

Rules:

  • The RAIDA may not respond if it is unavailable.
  • All Return Objects' key values are case in-sensitive and should be compared accordingly.
  • The names of the servers on Network 1 will always be one of 25 servers: RAIDA0 through RAIDA24. Note: server names are case-insensitive and should be compared accordingly.
  • In the future, if Doubling occurs, the names of the servers will have a network extension such as RAIDA0Net2 through RAIDA24Net2 where Net2 means they are on network 2.
  • The status will always be ready otherwise it will return an error. See General Errors.
  • The message will always be divided in two parts with a colon: The Subject and the Details.
  • The subject of the echo response will always be "Up" and the details will always be "Detection agent ready to detect authenticity." otherwise it will return an error. See General Errors.
  • The time is in GMT.

 

Echo Service Brief Mode V 5.5.17

Purpose:

Brief mode allows for the a shorter "ready" response. The RAIDA would only return one word. The hope is that it would use less bandwidth and may be faster.

 

Echo Request:

Client uses HTTPS to GET the echo page located in the service file on the RAIDA server. An extra "b=t" is added on the end of the request. It means brief=true.

 

Echo Request Example:

https://RAIDA0.CloudCoin.Global/service/echo?b=t

 

Echo Response Example:

ready

Detection Service V 5.5.17

Purpose:

The purpose of the Detect API is to allow the program or user to change the Authenticity Number in the RAIDA to a Proposed Authenticity Number so that ownership change of CloudCoin is possible.

 

Detection Request:

The program sends the RAIDA server an HTTPS GET request including the NN (network number), SN (Serial Number), AN (Authenticity Number), PAN(Proposed Authenticity Number) and Denomination of the CloudCoin that is to change ownership. The SN and the Denomination are like the CloudCoin's username.The AN is like the CloudCoins' password. The PAN is like a new password.

 

Detection Request Example:

https://RAIDA20.cloudcoin.global/service/detect?nn=1&sn=1&an=1836843d928347fb22c2142b49d772b5&pan=1836843d928347fb22c2142b49d772b5&denomination=1

 

Detection Response:

Server returns a Response Object using JSON that describes the name of the server, the status, a message, and a time stamp.

 

Detection Response Example If Passed:

{

  "server":"RAIDA1",

  "status":"pass",

  "sn":"1",

  "nn":"1",

  "message":"Authentic:1 is an authentic 1-unit. Your Proposed Authenticity Number is now the new Authenticate Number. Update your file.",

  "time":"2016-44-19 7:44:PM"

}

 

Note that the 1 after the word Authentic: is the serial number of the unit that was tested.

 

Detection Response Example If failed to authenticate:

{

  "server":"RAIDA1",

  "status":"fail",

  "sn":"1",

  "nn":"1",

  "message":"Counterfeit: The unit failed to authenticate on this server. You may need to fix it on other servers.",

  "time":"2016-44-19 7:44:PM"

}

 

Detection Response Example If failed because the denomination of the coin is not its real denomination (Someone is trying to falsify the denomination):

{"server":"RAIDA1","status":"fail","sn":"1","nn":"1""message":"Denomination: The item you are authenticating is a 250 units. However, the request was for a 25 units. Someone may be trying to pass you a money unit that is not of the true value ","time":"2016-11-21 9:11:PM"}

 

If failed because of missing or out-of-range GET NN parameter:

{"server":"RAIDA1","status":"error","message":"NN: The unit's network number was out of range or not on this server.","time":"2016-15-21 9:15:PM"}

 

If failed because of missing or out-of-range GET SN parameter:

{"server":"RAIDA1","status":"error","message":"SN: The unit's serial number was out of range.","time":"2016-15-21 9:15:PM"}

 

If failed because of missing or out-of-range GET Denomination parameter:

{"server":"RAIDA1","status":"error","message":"Denomination: The unit's Denomination was out of range.","time":"2016-04-21 9:04:PM"}

 

If failed because of missing or out-of-range GET PAN parameter:

{"server":"RAIDA1","status":"error","message":"PAN: The unit's Proposed Authenticity Number was out of range.","time":"2016-06-21 9:06:PM"}

 

If failed because of missing or out-of-range GET AN parameter:

{"server":"RAIDA1","status":"error","message":"AN: The unit's Authenticity Number was out of range.","time":"2016-07-21 9:07:PM"}

 

Otherwise Detect should return a General Error

 

Detection Service Brief:

The RAIDA responds with one word. A b=t is added to the GET request. Brief = True;

 

Detection Request Example in Brief Mode:

https://RAIDA20.cloudcoin.global/service/detect?nn=1&sn=1&an=1836843d928347fb22c2142b49d772b5&pan=1836843d928347fb22c2142b49d772b5&denomination=1&b=t

 

Detection Response Example in Brief Mode: Server returns one word, either pass, fail or error.

pass

 

 

Fix Process:

Purpose:

The purpose of the Fix API is to allow the program or user to repair "fractured" CloudCoins. A fractured CloudCoin is a CloudCoin that has some RAIDA servers failing authenticity. The CloudCoin owners can request that the fractured server ask its trusted servers (Neighbors) to vouch for them. By default, each RAIDA requires three servers to vouch for CloudCoin in order to self-repair. There are four combinations of servers that the each RAIDA will trust. They will trust the three "corner" RAIDA on any of their four corners. With the numbers arranged in a circle like a clock, and the RAIDA being repaired being zero, the three servers needed to trust are -1.-5.-6 OR +1, -4, -5 OR -1, +4, +5 OR +1, +5 and +6. RAIDA12, for example, will trust RAIDA11 AND RAIDA7 AND RAIDA6 together, OR the three other combinations of three servers. Note that the Administrator for each RAIDA can change the server that their RAIDA trusts.  Circle of tru

 

 

 

 

 

 

 

 

 

 

 

Ticket Service

 

Trusted Server Identification:

The program or user that has the fractured CloudCoin will identify the fractured RAIDA's trusted servers.

 

Rules:

  • There are four combination of three corner servers that are trusted. See the four-corner diagram above. Note the numbers wrap around like a clock (see image above).
  • In order to repair, a fractured RAIDA must receive three tickets from specific triad of these trusted servers.

 

Ticket Request:

Client makes a Ticket Request to trusted server triad. Note that there are three separate requests going to three separate RAIDAs.

 

Ticket Request Examples of an attempt to fix a fractured RAIDA1:

 

https://raida0.cloudcoin.global/service/get_ticket?nn=1&sn=16777005&toserver=1&an=7ac477841f5cce2889e4329a0e994ee3&pan=7ac477841f5cce2889e4329a0e994ee3&denomination=250

 

https://raida2.cloudcoin.global/service/get_ticket?nn=1&sn=16777005&toserver=1&an=98f094b7ed7d0a3f80db7ef0b03c740f&pan=98f094b7ed7d0a3f80db7ef0b03c740f&denomination=250

 

These Ticket Request are the same as the Detection Request except that they include a "toserver" parameters. The toserver parameter describes the RAIDA number that is to be repaired (0 through 24). This facilitates advanced encryption between the fractured RAIDA and the trusted RAIDA if it becomes necessary.

 

Ticket Response:

The client will receive a "ticket" from each RAIDA that authenticates the Ticket Request. The ticket is exactly 44 characters in length and is a random and secret hexadecimal number. By default, the RAIDA servers will only honor a ticket that is less than 15 seconds old, but this amount can be changed by each RAIDA Administrator.

Note that the "message" from the Ticket Response is not divided into subject and details when it returns a ticket.

 

Example Ticket: 23a399c5358fe88be678c45fa65747c81d31293cf44c

 

Ticket Response if successful:

{

 "server":"RAIDA2",

 "status":"ticket",

 "sn":"1",

 "nn":"1",

 "message":"23a399c5358fe88be678c45fa65747c81d31293cf44c",

 "time":"2016-40-21 10:40:PM"

}

 

The Ticket fails are identical to the Detection fails

 

 

Fix Service

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Fix Request:

The fix request combines the outcomes of three ticket requests to send to the fractured RAIDA. The tickets must come from three of the corner servers.

 

Fix Request Example attempting to fix RAIDA1:

https://raida1.cloudcoin.global/service/fix?fromserver1=0&message1=4aa2b02d3d2279216009cfcdd8a04b46b24835f63632

&fromserver2=2&message2=5ce45a6141ac9cb00233b11a900ea5302e9745051659&fromserver3=4&message3=23e45a6141ac9cb00233b11a900ea5302e9745051659&pan=E9611BF6FCBB1CB58CB62A5FC24A4B39

 

Fix Response: The fix response tells the client if the fix attempt was successful or failed.

 

Fix Response Example If success in repairing the fractured RAIDA:

{

 "server":"RAIDA1",

 "status":"success",

 "message":"Fixed: Unit's AN was changed to the PAN. Update your AN to the new PAN.",

 "time":"2016-09-22 1:09:PM"

}

 

If failed because a server number is not between the range of zero to 24 (inclusive):

{"server":"RAIDA1","status":"error","message":"Server: Server 26 Out of Range.","time":"2016-39-22 11:39:AM"}

Note that the "26" number is a variable that will change.

 

If failed because the ticket (message) is not exactly 44 characters long:

 {"server":"RAIDA1","status":"error","message":"Ticket: Message 1 Out of Range.","time":"2016-39-22 11:39:AM"}

Note that the "Message 1" could be "Message 2".

 

If failed because a tickets (message) is not from a trusted server:

{"server":"RAIDA1","status":"error","message":"Trust: Server 2 Not Trusted.","time":"2016-39-22 11:39:AM"}

Note that the "2" number is a variable(0-24) that will change.

 

If failed because a GET parameters where not supplied ( message1, message2, fromeserver1, fromserver2 and pan ):

 {"server":"RAIDA1","status":"error","message":"GET Parameters: You must provide a message1, message2, fromeserver1, fromserver2 and pan.","time":"2016-39-22 11:39:AM"}

 

If failed because one of the trusted servers could not be contacted by the fractured RAIDA server:

 {"server":"RAIDA1","status":"error","message":"Connection: Could not connect to Server 0.","time":"2016-39-22 11:39:AM"}

Note: "The "0" number is a variable (0-24) that will change.

 

If failed because one of the trusted servers reported that the Ticket(message/RN) was invalid (not 44 hex symbols):

{"server":"RAIDA1","status":"error","message":"Remote Ticket: Server 4 said invalid ticket.","time":"2016-39-22 11:39:AM"}

Note: The "4" number is a variable (0-24) that will change.

 

If failed because one of the trusted servers reported that it did not authorize the Ticket ( Random Number ) and that the ticket was not found in its Fixit List:

{"server":"RAIDA1","status":"error","message":"Remote Ticket: No Ticket found on Server 2.","time":"2016-39-22 11:39:AM"}

Note: The "2" number is a variable (0-24) that will change.

 

If failed because one of the trusted servers' databases reported some kind of error:

{"server":"RAIDA1","status":"error","message":"Remote Ticket: Server 4 database said invalid ticket.","time":"2016-39-22 11:39:AM"}

Note: The "2" number is a variable (0-24) that will change.

 

If failed because one of the trusted servers reported a fixit-log time that was longer than the fractured RAIDA allows for:

{"server":"RAIDA1","status":"error","message":"Time: Only 15 seconds where allowed for the fix but server 2 took 29.","time":"2016-39-22 11:39:AM"}

Note: The 15 seconds is a variable that can be changed by the RAIDA Administrator. The "2" number is a variable (0-24) that will change.

 

If failed because one of the trusted servers errored while trying to connect to it:

{"server":"RAIDA1","status":"error","message":"Connection Exception: Server 0 System.Net.WebException: The remote server returned an error: (500) Internal Server Error. at System.Net.HttpWebRequest.GetResponse() at ASP.service_fix_aspx.Page_Load(Object sender, EventArgs e)//raida0.cloudcoin.global/service/hints?rn=f67d8b84ed22b806ac81f00227ca5637476a9197ef6a.","time":"2016-09-22 1:09:PM"}

Note: The "0" number is a variable (0-24) that will change.

 

If failed because the two trusted servers returned different serial numbers (they should return the same serial number):

{"server":"RAIDA1","status":"error","message":"Mismatch: The Serial Numbers specified by the trusted remote servers did not match.","time":"2016-09-22 1:09:PM"}

 

If failed because one of the trusted servers returned a serial number that was invalid (Greater than 16,777,216 or less than 1:

{"server":"RAIDA1","status":"error","message":"Remote SN: The trusted server provided an invalid Serial Number.","time":"2016-09-22 1:09:PM"}

Note: The "0" number is a variable (0-24) that will change.

 

If failed because of an unknown problem:

{"server":"RAIDA1","status":"error","message":"Unknown: There was a problem and the unit was not fixed. Most likely, the SN did not exist..","time":"2016-09-22 1:09:PM"}

 

RAIDA Fix Protocol

General Errors:

Purpose:

The purpose of custom errors provided in JSON form is that webapplications can more easily handle common errors. Note: RAIDA Administrators may turn off custom errors in order to troubleshoot problems. This assumes that Custom Errors are turned on in the RAIDA servers' webserver.

{"server":"RAIDA1","status":"error","message":"500: Internal Server Error","time":"2016-09-22 1:09:PM"}

{"server":"RAIDA1","status":"error","message":"404: Not Found","time":"2016-09-22 1:09:PM"}

The failure numbers will have values over 400.

4xx Client Error.

5xx Server Error.

6.3 Cloudflare.

 

Structure of CloudCoins

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Denominations of CloudCoins

 

 

 

 

 

 

 

 

 

 

 

 

 

NameRangeDescription
NN (Network Number)To start with must be 1Could increase later after doubling
SN (Serial Number)1-16,777,215The SN determines the denomination (1,5,25,100 or 250)
AN (Authenticity Numbers)GUID without hyphensThere are 25 of these
AOID (Array Of Idiosynratic Data)Array of key/value pairsOptional. Used to make CloudCoins extensible.
POWN (Last Pown results)25 symbols, 0 (unknown), 1 (pass) or F (fail) like '11111011001FF11F11111111'Optional. Used to show the RAIDA status the last time the money was checked for Authenticity (may not be true)
Expiration DateAn integer that represents the number of months after August 2016 (zero month)Optional. CloudCoins must be checked for Authenticity every two years because they are scavenged every two years for last CloudCoins.(may not be true)
SN StartSN EndDenomination
12,097,152One
2,097,1534,194,304Five
4,194,3056,291,456Twenty Five
6,291,45714,680,064One Hundred
14,680,06516,777,216Two Hundred Fifty

JPEG File Format for CloudCoins

 

 

CloudCoin JPEG File Naming Convention V 5.5.2017

Users may name the jpegs what every they like.

Uncirculated coins are as follows: Denomination "CloudCoin", NN, SN, a user tag and ".jpg" separated by dots.

JPEG Example Filename:

250.cloudcoin.1.14589548.mintTagHere.jpg

APP0 Marker FFD8 FFE0 01C3 4A46494600 0101 01 0060 0060 1D 05 20 Bytes Long.
Byte Numbers Starting with ZeroBytesNameFile BytesMandatory Hex ValueValue varies?
0 & 12SOI (Start of Image)Always the first bytes FF D8 No
2 & 32Start of APP0 MarkerThe APP0 is Used to identify the file a a JPEG FIF file. This is the start of this marker FF E0 No
4 & 52APP0 LengthShows the Length of the APP0 Marker Excluding the first 2 bytes. In CloudCoins, this Equals 16+ 435 16 is fixed APPO stuff and 435 is the CloudCoin. 01 c3 No
6 => 105File identityWrites "JFIF" in ASCII, terminated by a null byte 4A 46 49 46 00 No
11 & 122VersionFirst byte for major version, second byte for minor version (01 02 for 1.02) 01 01 No
131Density units00 or 01 = pixels per inch. 02 = pixels per centimeter. 01 No
14 & 152Xdensity? 00 60 No
16 & 172Ydensity? 00 60 No
181Thumbnail Horizontal Pixel CountCloudCoin data is in the thumbnail and is 29 pixels wide 1D No
191Thumbnail Vertical Pixel CountCloudCoin data is in the thumbnail and is 5 pixels high 05 No
CloudCoin in Thumbnail: Each pixel holds three bytes. So 29 pixels by 5 pixels = 45 pixels. 45* 3 bytes each = 435 bytes for the entire CloudCoin.
20 => 419400ANs: 25 Authenticity Numbers25 GUIDs without hyphens. The Jpeg thumbnail dimensions are 29 pixels * 5 pixels * 3 bytes each = 435 bytes. Each AN is 16 bytes and 25 x 16 = 400 bytes so there are 35 bytes left for other info (AOID, Has Comment, Health Status, Expiration Date, Network Number and Serial Number. Too Large to show Yes
420 => 43516AOID: Account / Owner IDBytes can be used by the owner for their uses. Too Large to show Yes
436 =>44813POWN: Results of last pown attempt0 (unknown), 1 (pass),2 (no Response), E (error) or F (fail) '. Hex 11111011001f11111111211e199 The last nibble can be ignorred Yes
4491HC: Has comments?Indicates if there are any other information in the comments section of the Jpeg that is used by applications. 00 = No, More than zero = Yes (Program should look in the comments section of JPEG for more owner information). There is room for 255 codes so if you need to put some data it could fit here. Yes
450 1ED: Expiration Date Months from zero month (August 2016). Hex 18 = 24 months since zero or August 2018 Yes
4511NN: Network Number 1 Through 256 01 Yes
452, 453 & 4543SN: Serial Numbersn in Hex 6 bytes FF FFFF = 16,777,215 FF FFFF Yes
Rest of JPEG Image. Size will vary

JSON File Format V 5.5.2017

CloudCoin JSON File Naming Convention:

Total Amount of CloudCoins in file, ".CloudCoin" , then a random number or use defined tab in case there are other stack/chests with the same amount of CloudCoins separated by dots. The extension could be Chest or stack.

 

Example: 12750.cloudcoin.mytag.stack

 

Stack files are for the public. Chest files are for founders uncirculated coins. 12750.cloudcoin.userTagHere.chest CloudCoins should be stored in folders that reflect their status. Or, if they are all kept in the same folder then If the stack is full of counterfeit CloudCoins then it may have a .counterfeit extension. If the stack is full of lost coins then it may have the .lost extension. If the stack has a .fracked extension, it is full of fracked coins. If the coins are enctypted using software, then it does not matter.

 

CloudCoin JSON File Naming Convention: Total Amount of CloudCoins in file, ".CloudCoin" , then a random number or use defined tab in case there are other stack/chests with the same amount of CloudCoins separated by dots. The extension could be Chest or stack. Example: 12750.cloudcoin.mytag.stack. Stack files are for the public. Chest files are for founders uncirculated coins. 12750.cloudcoin.userTagHere.chest If the stack is full of counterfeit CloudCoins then it may have a .counterfeit extension. If the stack is full of lost coins then it may have the .lost extension. If the stack has a .fracked extension, it is full of fracked coins.
KeySample ValueNotes
NN1Network Number (1-256)
SN16,777,216Serial Number (1-16,777,216)
ANs2E2720222C231C1C2837292C30313434Array of 25 ANs.
ED9-2016Expiration Date. Month and year separated with a hyphen.
POWN (Optional)ppfpppppppppppupppppepppLast Health Status. Tracking the status of detection attempts. p = passed, f= failed, e=error, u = undetected, n = No response from RAIDA
AOIDfrom_email=Sean@Worthington.comArray of key value pairs created by the user for the user. Ok to leave blank but at least add [].
Here is a sample JSON file with two CloudCoins in it:
{
	"cloudcoin": [{
		"nn": "1",
		"sn": "16777215",
		"an": ["6A415F1CC541353C9AA5CE6FEAFC15B3", "1F07C89ACEF44EFC936C3685EF013D32",
 "6A415F1CC541353C9AA5CE6FEAFC15B3", "6A415F1CC541353C9AA5CE6FEAFC15B3",
 "6A415F1CC541353C9AA5CE6FEAFC15B3", 
                       "6A415F1CC541353C9AA5CE6FEAFC15B3", "6A415F1CC541353C9AA5CE6FEAFC15B3",
 "6A415F1CC541353C9AA5CE6FEAFC15B3", "6A415F1CC541353C9AA5CE6FEAFC15B3",
 "6A415F1CC541353C9AA5CE6FEAFC15B3", 
                       "6A415F1CC541353C9AA5CE6FEAFC15B3", "6A415F1CC541353C9AA5CE6FEAFC15B3",
 "6A415F1CC541353C9AA5CE6FEAFC15B3", "6A415F1CC541353C9AA5CE6FEAFC15B3",
 "6A415F1CC541353C9AA5CE6FEAFC15B3", 
                       "6A415F1CC541353C9AA5CE6FEAFC15B3", "6A415F1CC541353C9AA5CE6FEAFC15B3",
 "6A415F1CC541353C9AA5CE6FEAFC15B3", "6A415F1CC541353C9AA5CE6FEAFC15B3",
 "6A415F1CC541353C9AA5CE6FEAFC15B3", 
                       "6A415F1CC541353C9AA5CE6FEAFC15B3", "6A415F1CC541353C9AA5CE6FEAFC15B3",
 "6A415F1CC541353C9AA5CE6FEAFC15B3", "6A415F1CC541353C9AA5CE6FEAFC15B3",
 "6A415F1CC541353C9AA5CE6FEAFC15B3"],
		"ed": "9-2016",
                        "pown":"ppeppppppfppppppnpppupppp",
		"aoid": []
	}, {
		"nn": "1",
		"sn": "24589",
		"an": ["7A415F1CC541353C9AA5CE6FEAFC15B3", "1F07C89ACEF44EFC936C3685EF013D32",
 "6A415F1CC541353C9AA5CE6FEAFC15B3", "6A415F1CC541353C9AA5CE6FEAFC15B3",

 "6A415F1CC541353C9AA5CE6FEAFC15B3", 
                       "6A415F1CC541353C9AA5CE6FEAFC15B3", "6A415F1CC541353C9AA5CE6FEAFC15B3",

 "6A415F1CC541353C9AA5CE6FEAFC15B3", "6A415F1CC541353C9AA5CE6FEAFC15B3",
 "6A415F1CC541353C9AA5CE6FEAFC15B3",

                       "6A415F1CC541353C9AA5CE6FEAFC15B3", "6A415F1CC541353C9AA5CE6FEAFC15B3",
 "6A415F1CC541353C9AA5CE6FEAFC15B3", "6A415F1CC541353C9AA5CE6FEAFC15B3",
 "6A415F1CC541353C9AA5CE6FEAFC15B3", 
                       "6A415F1CC541353C9AA5CE6FEAFC15B3", "6A415F1CC541353C9AA5CE6FEAFC15B3",
 "6A415F1CC541353C9AA5CE6FEAFC15B3", "6A415F1CC541353C9AA5CE6FEAFC15B3",
 "6A415F1CC541353C9AA5CE6FEAFC15B3", 
                       "6A415F1CC541353C9AA5CE6FEAFC15B3", "6A415F1CC541353C9AA5CE6FEAFC15B3",
 "6A415F1CC541353C9AA5CE6FEAFC15B3", "6A415F1CC541353C9AA5CE6FEAFC15B3",
 "6A415F1CC541353C9AA5CE6FEAFC15B3"],
		"ed": "9-2016",
		"aoid": ["from_email=Sean@Worthington.com", "account=859562525630"]
	}]
}


AOID Standards

The AOID is a place that the owner of the CloudCoin can store data. This can be anything at all. But it is an array of strings. AOID used internally for applications. AOID can be ignored by apps and data should be stripped when importing. Here is a standard for internal user

KeySample ValueExplanation
frackedppfpppppppppppupppppepppTracking the status of detection attempts. p = passed, f= failed, e=error, u = undetected
app_statusSample ValueStatuses include "suspect", "fracked", "authentic", "counterfeit", "exported","lost"
from_emailSean@Worthington.comThe email of the person who sent the money
from_nameSample ValueWho gave it to you.
from_account568545221474Whos account it is for?
memoCan I write anything here?Yes you can
date_recieved2016-09-15 5:30:20"Date the coin was recieved
date_sent2016-09-15 5:30:20"Date you sent it to someone else
escrow_id85521144If the money is kept for escrow
fundVacationWhat every pupose the money will be used for.

Standard Money images

John Locke 250 CloudCoins

Mind Storage V 6.20.2017

CloudCoin are the first currency that can be stored in your mind. Here are the standards for create ANs based on what you know:

Mind storage provides maximum security the user may store the Serial Numbers of their CloudCoins on paper and then the ANs in their mind..

 

 

 

Requires two Pass-phrase.

Both are turned into Hex String.

 

Pass-phrase: rules:

1. Cannot start with white space. Cannot end with white space. All all other codes are allowed. White space includes carriage returns, spaces, tabs, etc.

2. Paraphrases cannot be the same.

3. The two paraphrases combined must have a length of over 17 bytes.

 

Note: For better security, it is advised that Westerners should use 8 byte encoding. Others should use Unicode 16 byte encoding.

 

Examples:

First Pass-phrase:

We love CloudCoins!

 

Second Pass-phrase::

I store them in my mind.

 

Pass-phrase 1 converted to a Hexadecimal String:

5765206c6f766520436c6f7564436f696e7321

 

Pass-phrase 2 converted to a Hexadecimal String:

492073746f7265207468656d20696e206d79206d696e642e

 

The pass phrases are merged into a composite string:

Pass-phrase 1 becomes the odd indexes an pass-phrase 2 becomes the even indexes (note the first number is index 1):

Left overs from the longer string are added to the end (hyphen added for better visualization of the end)

 

54796250270367c466ff776266552200473466c866f5765d624046396ef260966de-6d696e642e

 

String is the repeated until there are 800 characters. Any extra characters are cut off:

 

54796250270367c466ff776266552200473466c866f5765d624046396ef260966de6d696e642e54796250270367c466ff77

6266552200473466c866f5765d624046396ef260966de6d696e642e54796250270367c466ff776266552200473466c866f5

765d624046396ef260966de6d696e642e54796250270367c466ff776266552200473466c866f5765d624046396ef260966d

e6d696e642e54796250270367c466ff776266552200473466c866f5765d624046396ef260966de6d696e642e54796250270

367c466ff776266552200473466c866f5765d624046396ef260966de6d696e642e54796250270367c466ff7762665522004

73466c866f5765d624046396ef260966de6d696e642e54796250270367c466ff776266552200473466c866f5765d6240463

76ef260966de6d696e642e54796250270367c466ff776266552200473466c866f5765d624046396ef260966de6d696e642e

54796250270367c466ff776266552200473466c866f5765d624046396ef260966de6d696e642e54796250270367c466ff77

62665522

 

The 800 characters are cut into 25 different PANs with a length of 32 characters each.

Each PAN is used during detection so that it becomes the new AN.

 

Schemes to generate passphrases.

 

There is one standard scheme to generate the two passphrases.

The standard calls for the user to enter a username, password and email address.

 

The first passphrase becomes the username and password concatenated: usernamepassword

The second passphrase becomes the email address.

 

Note that the username and email are made to go lowercase before they are used.

 

 

 

When is a CloudCoin Considered Powned?

 

Powned

  1. Powned means knowing 20 of 25 ANs
  2. To seize control of a CloudCoin you must know as few as 6 of the 25 authenticity numbers.
  3. To know that you own a CloudCoin, you must have exclusive knowledge of 20 out of 25 ANs.
  4. If during the detection process there are more than five fails then the coin must be treated as hostile
  5. If software accepts a coin that has more than five fails (as authentic), it is possible for the previous owner to seize it back.
  6. Therefore, if there are more than five fracks, the software must do one of two things:
    1. Consider any coin with more than five fails as counterfeit and reject it.
    2. Check the pown pattern to see if it has any of the four patters that could be used to seize control of the coin:
      1. UP_LEFT = "ff***f";
      2. UP_RIGHT = "ff***pf";
      3. DOWN_LEFT = "fp***ff";
      4. DOWN_RIGHT = "pf***ff";
      5. If one of the threat patterns is recognized then consider it Counterfeit. Or
      6. Fix the fracks and then detected it again until the number falls below five fails. Note, it is important to detect again in the slight chance the past owner is trying to fix fracked at the same time the new owner is.

Fracked

Fracked means that up to 19 of the ANs failed detection. If there are more than 5 fracks, the fracked coin is suspect because it maybe counterfeit, lost or, the coin could still be powned after frack fixing.

 

Counterfeit

Counterfeit means that a coin cannot be powned by a new owner even after fixing all the possible fracks.

 

Lost

Lost means that nobody is able to pown the coin any more.

 

 

 

© The CloudCoin Consortium. All rights reserved.

CloudCoin Logo
RAIDA Fix Protocol
John Locke 250 CloudCoins
CloudCoin Logo
RAIDA Fix Protocol
John Locke 250 CloudCoins