Multi-Detect V 4/18/2020

Purpose:

The RAIDA Multi Detection Protocol allows many coins to be authenticated at the same time.

PARAMETERS:

  • b=t: This means brief mode is true. You will need to include this or you will get the old responses and these are very large and slow to download
  • nn: Network Number. All coins must be on the same network.
  • sns[]: Serial Number between 1 and 16,777,216 inclusive
  • ans[]: Authenticity Number that is a guid without hypends. Lowercase prefered.
  • pans[]: Proposed Authenticty Number. A new random GUID. Use the ans if you want to see if a coin is real but not pown.
  • dn[]: Denomination Number. For CloudCoin this must be either 1,5,25,100 or 250.

Example POST authenticating three coins

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

        b=t&
        nn=1&
        sns[]=145895&sns[]=66585&sns[]=16589554&
        ans[]=8ae06de0f9ce4917b3309df71570f92c&ans[]=b25fc7a548c341c98cefbac35689aff1&ans[]=f193f1304ffc4344822c10be9309a4c3&
        pans[]=c7bea382188d404d8f0efc5969c54c5a&pans[]=75819e4721cb4970a2e2582d7e26318b&pans[]=0a4a8a4014264cbf8c00383ae180a152
        dn[]=250&dn[]=1&dn[]=250
        

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",
            	"ex_time":0.0623654445
            }
        
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",
             	"ex_time":0.0623654445
             }
        
If all the coins were counterfeit:
             {
             	"server": "RAIDA11",
             	"status": "mixed",
             	"message": "pass,pass,fail",
             	"version": "2020-04-13",
             	"time": "2020-04-18 22:57:55",
             	"ex_time":0.0623654445
             }
        
If there were some fails you will get comma seperated values in the message. One value for every coin in order that they were sent:

pass,pass,fail


RESPONSE IF TOO MANY COINS SENT (OVER 200)

{
        "server":"RAIDA1",
        "status":"dud",
        "message":"Length: Too many coins attached.",
        "version": "2020-04-13",
        "time":"2016-44-19 7:44:PM"
}

RESPONSE IF ARRAY LENGTHS NOT THE SAME

{
        "server":"RAIDA1",
        "status":"dud",
        "message":"Length: Arrays not all the same length (nn,sn,an,denominations).",
        "version": "2020-04-13",
        "time":"2016-44-19 7:44:PM"
}

RAIDA Multi-Hints Protocol V 6/12/2018

Purpose:

The RAIDA Multi Hints Protocol allows many tickets to be fetched

Example POST authenticating three coins

	
https://RAIDA0.CloudCoin.Global/service/multi_hints
rns[]=c8b7a96e7cf1961587977cfb3847b2ba7c7a308a3fd2&
rns[]=61fd09083302bb3eb8350dfeb1d7bf6c125b13e560bf&
rns[]=dcea173685e387f7007bf2e578917cbdd10750088c29

Example Response if two of the three tickets are failed:

[-2:9223372036854775807:1,-2:9223372036854775807:1,1:6447:1]

Negative numbers are fails. Positive numberes represent serial numbers. See the hints protocol for details. The last is the network number.

RAIDA Multi-Ticket Protocol V 6/12/2018

Purpose:

The RAIDA Multi Ticket Protocol allows many tickets to be generated at the same time.

Example POST requesting three tickets:

https://RAIDA13.CloudCoin.Global/service/multi_ticket
nn=1&
sns[]=145895&sns[]=66585&sns[]=16589554&
ans[]=8ae06de0f9ce4917b3309df71570f92c&ans[]=b25fc7a548c341c98cefbac35689aff1&ans[]=f193f1304ffc4344822c10be9309a4c3&
pans[]=c7bea382188d404d8f0efc5969c54c5a&pans[]=75819e4721cb4970a2e2582d7e26318b&pans[]=0a4a8a4014264cbf8c00383ae180a152&
denomination[]=1&denomination[]=1&denomination[]=1

Example Response if all tickets were successful:

[
  {
  "server": "RAIDA13",
		"status": "ticket",
		"sn": "145895",
		"version": "2018-04-01",
		"message": "10be9309a4c3f193f1304ffc4344822c10be9309a4c3",
		"time": "2018-09-05 06:19:34"
	},
	{
		"server": "RAIDA13",
		"status": "ticket",
		"sn": "66585",
		"version": "2018-04-01",
		"message": "304ffc434482210be9309a4c3f193f1c10be9309a4c3",
		"time": "2018-09-05 06:19:34"
	},
	{
		"server": "RAIDA13",
		"status": "ticket",
		"sn": "16589554",
		"version": "2018-04-01",
		"message": "4c3f193f1304f10be9309afc4344822c10be9309a4c3",
		"time": "2018-09-05 06:19:34"
	}
]

Example Response if all tickets failed:



[{
		"server": "RAIDA13",
		"status": "fail",
		"version": "2018-04-01",
		"message" : "Database: Operation failed. Ticket has not been created.",
		"time": "2018-09-05 06:19:34"
	},
	{
		"server": "RAIDA13",
		"status": "fail",
		"version": "2018-04-01",
		"message" : "Database: Operation failed. Ticket has not been created.",
		"time": "2018-09-05 06:19:34"
	},
	{
		"server": "RAIDA13",
		"status": "fail",
		"version": "2018-04-01",
		"message" : "Database: Operation failed. Ticket has not been created.",
		"time": "2018-09-05 06:19:34"
	}
]
The last byte of each ticket (returned in the 'message' field) in the response holds the Detection Agent number. This number can be used by RAIDA server to forward the request to the corresponding Detection Agent.

RAIDA Multi Fix Protocol V 6/12/2018

Purpose:

The RAIDA Multi Fix Protocol allows many coins with the same fracked RAIDA# to be fixed using the same "Corner" at the same. All the coins must be on the same network.

This protocol only works with the "Four-Fix" protocol in which three trusted raida on one corner and one trusted raida on the oposite corner are required to fix.

The client would first scan the fracked folder and find all the CloudCoins that are fracked on RAIDA0.

Then the client would collect multi-tickets from RAIDA0's four trusted servers (using the fix 4 - not fix 3 - protocol) for corner one. The essential requirement here is that client must generate multi_ticket requests using the same order of SNs across all four servers.

After the fix attempt, the CloudCoin files would be updated. Then RAIDA would be checked again. If there are still fracked coins then the client would try again this time using corner #2. Only after all the Coins are fixed on RAIDA0 or all the corners have been tried, the client move on to RAIDA1. This process would repeat until all 25 RAIDA have been tried.

Then the process would be reversed as some of the recently fixed RAIDA may be able to aid in fixing others.

Example POST authenticating three coins

The RAIDA Multi Fix Protocol allows many coins with the same fracked RAIDA# to be fixed using the same "Corner" at the same. All the coins must be on the same network.

This protocol only works with the "Four-Fix" protocol in which three trusted raida on one corner and one trusted raida on the oposite corner are required to fix.

The client would first scan the fracked folder and find all the CloudCoins that are fracked on RAIDA0.

Then the client would collect multi-tickets from RAIDA0's four trusted servers (using the fix 4 - not fix 3 - protocol) for corner one. The essential requirement here is that client must generate multi_ticket requests using the same order of SNs across all four servers.

After the fix attempt, the CloudCoin files would be updated. Then RAIDA would be checked again. If there are still fracked coins then the client would try again this time using corner #2. Only after all the Coins are fixed on RAIDA0 or all the corners have been tried, the client move on to RAIDA1. This process would repeat until all 25 RAIDA have been tried.

Then the process would be reversed as some of the recently fixed RAIDA may be able to aid in fixing others.

Example POST authenticating three coins

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

nn=1

fromserver1=19 
fromserver2=20
fromserver3=24
fromserver4=6

message1[]=cdd8a04b46b2484aa2b02d3d2279216009cf35f63632
message1[]=4aa2b02d3d2279216009cfcdd8a0835f636324b46b24 
message1[]=2b02d34aad2279216004b46b24835f6363209cfcdd8a

message2[]=4aa216009cfcdd8a04b46b24835f636322b02d3d2279
message2[]=3d227924aa2b02d16009cfcdd8a04b46b24835f63632
message2[]=4aa2b02d16009cfcdd8ad2279224835f6363204b46b3

message3[]=5f63634aa2b02d3d2279216009cfcdd8a04b46b24835
message3[]=2b02d34aad6009cfcdd8a04b46b24835f63632227921
message3[]=4aa2b02d3d2279216009cfcdd8a04b46b24835f63632

message4[]=d2272b02d3009cfcdd8a04b46b24835f6363292164aa
message4[]=a04b46b2d3d22fcdd824835f6363279216009c4aa2b0
message4[]=fcdd8a04b46b24835f636324aa2b02d3d2279216009c

pans[]=8ae06de0f9ce4917b3309df71570f92c
pans[]=b25fc7a548c341c98cefbac35689aff1
pans[]=f193f1304ffc4344822c10be9309a4c3

RESPONSE:

[{
  "server":"RAIDA19",
  "status":"success",
  "sn":"145895",
  "nn":"1",
  "message":"Fixed: Unit's AN was changed to the PAN. Update your AN to the new PAN.",
  "time":"2016-44-19 7:44:PM"
},
{
  "server":"RAIDA19",
  "status":"success",
  "sn":"66585",
  "nn":"1",
  "message":"Fixed: Unit's AN was changed to the PAN. Update your AN to the new PAN.",
  "time":"2016-44-19 7:44:PM"
},
{
  "server":"RAIDA19",
  "status":"error",
  "sn":"16589554",
  "nn":"1",
  "message":"Connection: Could not connect to Server 11.",
  "time":"2016-44-19 7:44:PM"
}]

RESPONSE IF TOO MANY COINS SENT (OVER 400)

[{
  "server":"RAIDA19",
  "status":"dud",
  "message":"Length: Too many coins attached.",
  "time":"2016-44-19 7:44:PM"
}]

RESPONSE IF ARRAY LENGTHS NOT THE SAME

[{
  "server":"RAIDA19",
  "status":"dud",
  "message":"Length: Arrays not all the same length (nn,sn,an,denominations).",
  "time":"2016-44-19 7:44:PM"
}]