The Intense Coin team has been through several iterations of design for the Intense VPN services, and we were pleased to announce finalization of the design and requirements a couple weeks ago. As we mentioned in the past, judicious planning in this phase has allowed our products to be designed with supreme flexibility, longevity, and capability. The purpose of this document is to provide a high level and succinct overview of the proposed design. Major principles and themes are discussed while granular details have been omitted. Throughout the design process, the guiding principles have been privacy, fair payment and seamless use of services.
Our development team has produced a comprehensive design allowing us to start development in the second week of March.
We would like to share the main components of the design with our project supporters.
The primary components of the VPN services are depicted below, on a component architecture diagram.
We use the Intense Coin blockchain for payment transactions. Each payment for a VPN service will have a special flag associated distinguishing them from other payments.
The “VPN service” comprises a full VPN service provided by OpenVPN and a partial VPN service operating only on supported browsers running our Browser Extension.
The key components of the full VPN service are OpenVPN server, OpenVPN client, and HAProxy. On the provider side, the Dispatcher manages service descriptions, publishes these to our cloud based Service Description Platform, and manages authorised users for both full and partial VPN services.
On the client side, we wanted to deliver an experience that is as seamless as possible. As such, the Intense wallet software contains the OpenVPN client and an embedded Dispatcher to setup partial proxy connection.
The cloud based Service Feedback Platform allows Clients to submit their anonymous feedback after payment and the usage of a service.
In our design, we have used strong encryption standards, namely elliptic curve ed28819, OpenVPN’s and HAProxy strong ciphers restricted to the strongest possible. We have also taken into account possible TLS traffic interception and hence all critical traffic and messages are designed to detect and fail-safe when such interception is performed by outside actors.
These design decisions were reached after lengthy periods of careful planning and discussion using the expertise on our team, which comprises nearly 100 years of combined experience. We appreciate your interest and support and will continue to update you as the software is developed.