The development of email services has given a big boom in the era of the advent of the Internet. With the advent of Web3, people massively using email began to think about greater security on the network and look for alternative solutions.
Today, in our interview, I will tell you about the team that launched the Web3 DeMail Service from the initial idea to the full implementation of a working solution that will help solve current problems in existing email services and answer why people are moving to Web3.
We will talk with the Team Lead and Project Owner, Nikita Tkach, and the main team members.
Editor’s Note: The following interview has been edited for brevity and clarity.
Let's start with the first question. Can you tell our readers about Qamon and how it differs from traditional email services?
Oh, there are a lot of differences. It starts with the fundamental work principle. Qamon is basically a backed-less service. That means that we don’t have any kind of intermediary servers. We use blockchain itself, where one user sends a transaction to another user, where the payload of this transaction is email content itself (or the file). So, the blockchain serves as the difference:
No intermediary servers = 0 risk for privacy. Who knows what happens on the back-end side when the mail travels from one user to another? I think it's self-explanatory here.
We use a distributed file system (IPFS) to store files (attachments). It’s censorship-resistant and redundant to attacks.
Decentralized Availability: With IPFS, your content will be available through a network of nodes that store copies of that content. If one site becomes unavailable, users can still access content through other sites. This improves the overall availability of content even under failure conditions.
No central point of failure: Since IPFS does not depend on a centralized infrastructure, the risk of losing access to your content due to service outages or shutdowns is greatly reduced. Your content will remain available even if specific nodes or a dead service are down.
Why do we need to migrate from traditional emails?
Well, first of all, Qamon doesn’t have any intermediary servers, which classy mails have.
Moving from traditional email to services like Qamon removes the limitations of traditional email systems. Traditional emails are subject to privacy breaches, hacks, and centralized points of failure. Using blockchain technology and a decentralized infrastructure, Qamon brings privacy and security risks to 0, ensures uninterrupted communication with less risk of data leaks associated with centralized servers, and provides a more reliable email ecosystem.
Moving from traditional email to services like Qamon removes the limitations of traditional email systems. Traditional emails are subject to privacy breaches, hacks, and centralized points of failure. Using blockchain technology and a decentralized infrastructure, Qamon brings privacy and security risks to 0, ensures uninterrupted communication with less risk of data leaks associated with centralized servers, and provides a more reliable email ecosystem.
What inspired the team to create a decentralized mail service based on the Everscale blockchain?
The motivation for creating Qamon is related to the desire to eliminate the shortcomings of traditional mail services. The use of blockchain and a serverless approach can provide increased privacy, security, and availability for email communication. Decentralization is in line with the broader trend towards Web3 technologies that emphasize user empowerment, privacy, and data ownership with the same set of features and conveniences that are available to businesses and customers.
How does Qamon use Everscale's decentralized infrastructure to enhance email security and privacy?
The details will depend on the specific implementation of Qamon, but in general, the decentralized nature of the Everscale blockchain can contribute to email security and privacy by:
- Reduced dependency on centralized servers vulnerable to attack
- Enable end-to-end encrypted communication between users
- Zeroing the risk of exposing sensitive data during transmission
Using blockchain immutability to maintain a tamper-proof record of transactions.
How do you prevent censorship or surveillance in Qamon?
Decentralization and detection technology to detect censorship and surveillance in Qamon. The transmission of emails over a distributed network in encrypted form makes it impossible for a single entity to control or censor communication. Encryption and the distributed nature of the system are raised to maximize user privacy, making surveillance difficult.
How does Qamon deal with scalability and potential network congestion issues in a decentralized environment?
We just use the most scalable blockchains as transport for our emails. Those are Venom and Everscale. I’m 100% sure that this kind of retail service (which fully relies on the blockchain as a backend).
How Qamon protect users from spam, phishing, and other email attacks?
In the Qamon ecosystem, there is no shared address database susceptible to spam. Instead, the blockchain acts as a decentralized and immutable ledger that records email transactions. Each email transmission involves a cost, adding a layer of financial disincentive for sending unsolicited or malicious messages. This cost requirement significantly hinders spammers' ability to flood the network with unwanted content.
Are there any special encryption or authentication protocols used by Qamon to improve security? Could you tell us more about it?
Qamon's sophisticated security framework employs a combination of asymmetric and symmetric encryption (utilizing the chacha20Poly1305 algorithm), blockchain-based storage, recipient key exchange, and cryptographic signatures, establishing a comprehensive email security system that guarantees confidentiality, authenticity, integrity, and non-repudiation, all underpinned by meticulous implementation, vigilant key management, and ongoing threat surveillance.
Do you have some integrations with other Web3 Apps/dApps?
Of course, in addition to the security measures mentioned earlier, Qamon offers support for the Ylide protocol. This protocol currently allows users to receive and decrypt messages if they previously used it as part of our service. Looking ahead, we have ambitious plans for full protocol integration, which will cover both sending messages and expanding support for EVM (Ethereum Virtual Machine) and TVM networks, reflecting our desire to improve the security and ease of communication in decentralized ecosystems.
Can you discuss the user interface and accessibility aspects of Qamon? Is it compatible with existing centralized email clients?
The user interface and accessibility of Qamon are driven by our design philosophy, prioritizing user-friendly familiarity akin to traditional email clients while seamlessly incorporating blockchain functionalities. In the upcoming quarter, we're set to embark on a journey to bridge the gap between Web2 and Web3. This will empower users to have human-readable addresses, much like popular email services, enabling them to send messages from centralized platforms and receive them within Qamon, thereby enhancing interoperability and convenience.
Are there any plans to expand Qamon's features or integrate with other decentralized platforms in the future?
Qamon's future trajectory hinges on our development roadmap and visionary goals. This encompasses potential integration with further decentralized platforms, the expansion of functionalities, and forging collaborations with additional services. Our current integration with the ylide protocol is just the tip of the iceberg; we have even more ambitious plans in this realm, driven by our commitment to pushing the boundaries of secure and decentralized communication.
Let's discuss the future. What is your vision for further mail services? Will it also be in demand in the future?
Email services, especially those that offer enhanced privacy, security, and data ownership through decentralization, are likely to remain relevant in the future. As users become more conscious of their digital footprint and data privacy, demand for secure and censorship-resistant communication platforms could continue to grow.
Will the government also use services like Qamon? What do you think?
Undoubtedly, government entities stand to derive substantial benefits from embracing services akin to Qamon. The potential utility of such platforms extends to enhancing the security, efficiency, and reliability of governmental communications. We are, in fact, already in the midst of a pioneering phase, actively subjecting Qamon to rigorous testing within the administrative frameworks of select nations. The outcomes of these ongoing trials stand to offer tangible insights into the viability and adaptability of Qamon within governmental contexts.
What else could you tell our readers?
I'd like to emphasize that Qamon's unique approach to email services highlights the ongoing innovation in the tech industry. The use of blockchain, decentralization, and cryptography opens up new possibilities for enhancing digital communication security and privacy. As you explore these advancements, remember that the success and adoption of platforms like Qamon depend on a balance between innovation and practicality, ensuring that technology truly meets users' needs while safeguarding their digital lives.
About the Qamon Team
Nikita Tkach – Team Lead and Project Owner
Nikita Tkach is an experienced IT professional with seven years of experience in Web3 since 2021. Responsible for the development of the entire project, has four years of experience as a team leader, and since 2023 as a project manager. Nikita's expertise notes the choice of technologies, the structure of the platform, and the development of the main application modules.
Ruslan Galimov – Technical advisor
Ruslan Galimov is an experienced IT specialist with ten years of development experience, has a master's degree, and also has experience in managing teams and business processes. Ruslan advised on the development of the Qamon backend (ipfs) and architectural solutions.
Ivan Vasyliev – frontend developer
With six years of experience, Ivan Vasiliev is a skilled front-end developer. He's primarily known for his work on the web component of the Qamon application, making user interfaces smooth and intuitive. He's also been involved in integrating blockchain technology, adding advanced security features to Qamon's capabilities.
Vadim Reznichenko - Flutter developer
Vadim Reznichenko is an experienced Flutter developer with over four years of experience specializing in blockchain integration. It excels in the development of decentralized applications, providing a user-friendly experience. In addition to Flutter, Vadim also acts as a universal server developer, demonstrating a holistic understanding of the project from idea to implementation. His dedication and diverse skill set make him a valuable asset to our team.
