The RAIDA Multi Detection Protocol allows many coins to be authenticated at the same time.
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
{ "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
{ "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" }
The RAIDA Multi Hints Protocol allows many tickets to be fetched
https://RAIDA0.CloudCoin.Global/service/multi_hints rns[]=c8b7a96e7cf1961587977cfb3847b2ba7c7a308a3fd2& rns[]=61fd09083302bb3eb8350dfeb1d7bf6c125b13e560bf& rns[]=dcea173685e387f7007bf2e578917cbdd10750088c29
[-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.
The RAIDA Multi Ticket Protocol allows many tickets to be generated at the same time.
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
[ { "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" } ]
[{ "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.
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.
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.
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
[{ "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" }]
[{ "server":"RAIDA19", "status":"dud", "message":"Length: Too many coins attached.", "time":"2016-44-19 7:44:PM" }]
[{ "server":"RAIDA19", "status":"dud", "message":"Length: Arrays not all the same length (nn,sn,an,denominations).", "time":"2016-44-19 7:44:PM" }]