Your IOTA Chat App
The goal is to create a quantum secure chat app, in which you are the owner of your own data and nobody else!
Impressions of the current state:
Table of Contents
How Chiota works?
See the GitHub Wiki for more detailed information about the different modules of Chiota.
Chiota doesn’t use the MAM Layer for sending secure messages. Instead, it uses the NTRU Encryption (see NTRU Key Exchange for IOTA for more details). There are several reasons for that:
- NTRU or some other form of key exchange is needed for the MAM-Layer anyway
- For the MAM Layer, you have a lot of different transactions and currently, the proof-of-work takes really long, so the goal is to reduce the number of necessary transactions
- You need to store the state of the MAM Layer (root hash, channel keys, etc.). If you want to store these things quantum secure on the tangle it results in more messages and therefore additional PoW
- NTRU can be extremely fast, see Speed records for NTRU
The disadvantage of the current system:
- You are limited to less characters per transaction because the NTRU encryption needs more space
- Advances in cryptanalysis may at some point break NTRU
During the process of creating the health care chatbot Florence, we found out that we can't use the technology to its full potential due to various problems with the current state of the healthcare system. You as a patient should be in control of your healthcare data and a chatbot should support the private, secure and continuous communication between you and your healthcare provider network. However, with the current technology that isn't possible. That is why we started the project “Untangle Care”, you can find out more about it on the official IOTA ecosystem page.
- Google Play beta test: https://play.google.com/apps/testing/chiotaapp.chiotaapp
IOTA Donation address
If you want to help either join our discord server or you can open issues for bugs you've found or features you think are missing. You can also submit pull requests to this repository.
If editing the README, please conform to the standard-readme specification.
MIT License © PACT Care B.V.