This proposal is a continuation of our previous project Funded 100% in FUND5, in which we created a proof-of-concept piece of software to upload encrypted messages/images to the Cardano blockchain.
Now we want to propose the creation of servers for a given network of operating units (robots) that will be in charge of coordinate message sending/receiving operations that may be certified via the Cardano Blockchain.
https://cardano.ideascale.com/userimages/accounts/93/936143/panel_upload_48088/scheme-58bb50.png
The server is intended to run a Cardano node and be in continuous communication with the Cardano blockchain. If an unit (robot) needs to certify and send a message to an external entity, the server will create the message, upload it to the Cardano blockchain, store a additional metadata in a private/public database and finally sent information about the transaction to the target entity. Contrary, if the server recieves a message, it will categorize the message and store it in the give database with the proper metadata. Storing information about the sent and receiving messages will ease search for old messages and categorize them.
https://cardano.ideascale.com/userimages/accounts/93/936143/panel_upload_48088/coffee-64c1f2.png
With this mechanism, users will be able to easily certify, catalog and sent critical information to external units. As the units (robots) are equipped with the needed tools to directly interact with human operators, this approach eases the flux of critical information between different users (or entities).
As we are including a database to the message send/certify/receive solution, we can easily track and classify all the information that circulates in a given network. Also, as multiple databases (private and public) may be created, the scope of the information flux is flexible, and thus can be easily modulated depending on the needs of the operator.
Challenge: Sending messages (large text or images) may be expensive in terms of currency. Possible Solution: Hybrid Model: Heavy information stored in a public database, certification upload to the Cardano Blockchain.
Challenge: Synchronization between multiple nodes (robots) may be problematic. Possible Solution: Create a queue system to manage the message receiving/sending.
Challenge: Adaptation to Raspberry Pi 4. Possible Solution: Optimize and test all the system for a Raspberry Pi.
Challenge: Public databases are not stable over time. Possible Solution: Use DOI to always assure the access to critical items.
Challenge: Deploy the same configuration over different units. Possible Solution: Use of Nix and .nix files.