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. A RAIDA that is fracked requires four neighbor 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 four "corners". Or, any five neighboring servers can be called to vouch for the CloudCoin being authentic.
Circle of Trust with 4 Trusted Servers
Shows the servers that RAIDA 0 will trust in order to repair. There are four different combinations (called corners) that are acceptable to the RAIDA for fixing. Each represented by a different color.
Ticket Service
Trusted Server Identification:
The program or user that has the fractured CloudCoin will identify the fractured RAIDA's trusted servers.
Rules:
Ticket Request:
The client makes a Detect requiest to a four or five trusted servers. Note that separate requests are needed to separate RAIDAs.
Ticket Request Examples of a POST attempt to fix a fractured RAIDA1:
https://RAIDA0.CloudCoin.Global/service/multi_detect
nn=1&
corner=1&
pan=9f70f199f0844df2bd6e607620002cbf&
a=a4aedc27bf524e3aabf8dbcca686140a8ae06de08934&
b=11328c19f7ef4a63a4a56d25f9785c05197b44d4bae1&
c=c35bfa217d364cc58d9c0a96a7a256f4822c10be9233&
d=48df533f42364308b3a2ce15f1d216e266c649dc656a&
sn[]=145895&sn[]=66585&sn[]=16589554
RESPONSE:
If all the coins were authentic:
{
"server": "RAIDA11",
"status": "allpass",
"message": "All the coins were authentic",
"version": "2020-04-13",
"time": "2020-04-18 22:57:55"
}
If all the coins were counterfeit:
{
"server": "RAIDA11",
"status": "allfail",
"message": "All the coins were counterfeit",
"version": "2020-04-13",
"time": "2020-04-18 22:57:55"
}
If some of the coins were counterfeit and other authentic:
{
"server": "RAIDA11",
"status": "mixed",
"message": "pass,pass,fail",
"version": "2020-04-13",
"time": "2020-04-18 22:57:55"
}
You may ask for a "master ticket" that will work of all the RAIDA SNs that you need to fix.
Ticket Response:
The client will receive a "ticket" from each RAIDA that authenticates the Detec 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 each RAIDA Administrator can change this amount.
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"}
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"}
