QuantumGate is a peer-to-peer (P2P) communications protocol, library and API. The long-term goal for QuantumGate is to become a platform for distributed computing based on a mesh networking model. In the short term, the goal is to provide developers with networking technology that they can easily integrate and use in their own applications. Click here for a more detailed overview.
This software is currently in alpha development stage. It has not yet undergone peer review and no security audits have yet been done on the cryptographic protocol and its implementation. The API may also change, and while big changes are unlikely it will receive small updates as development progresses. Feel free to use and experiment with this software in your own projects, but keep the above information in mind.
Based on the architecture described in the overview, the following main features are not yet implemented:
- DHT functionality
- Database functionality
QuantumGate is developed in C++17 and currently only supports the Microsoft Windows (x86/x64) platform. Support for Linux is planned for the future.
You'll require the latest version of Microsoft Visual Studio 2017, as well as the dependencies listed below. When the paths to the dependency includes and libraries have been configured properly, building is as simple as opening the
QuantumGate.sln file in the project root with Visual Studio and issuing the build command for the entire solution.
QuantumGate Core Library
|Microsoft Guideline Support Library||Latest.|
|OpenSSL||At least 1.1.1|
|zlib||At least 1.2.11|
|Zstandard||At least 1.3.4|
QuantumGate Test Applications/Extenders
|JSON for Modern C++||At least 3.2.1|
The QuantumGate MSVC project is configured to look for specific naming of the OpenSSL, zlib and Zstandard
.lib files, depending on the platform (32 or 64 bit) you're building for. You may have to build these libraries yourself to specify the names, or, alternatively you may change the names in the source code and configuration to the ones you use.
|Library||x86 Debug||x86 Release||x64 Debug||x64 Release|
|OpenSSL||libcrypto32d.lib, libcrypto32d.dll||libcrypto32.lib, libcrypto32.dll||libcrypto64d.lib, libcrypto64d.dll||libcrypto64.lib, libcrypto64.dll|
|zlib||zlib32.lib, zlib32.dll||zlib32.lib, zlib32.dll||zlib64.lib, zlib64.dll||zlib64.lib, zlib64.dll|
|Zstandard||zstd32.lib, zstd32.dll||zstd32.lib, zstd32.dll||zstd64.lib, zstd64.dll||zstd64.lib, zstd64.dll|
Documentation can be found in the Wiki.
A listing of examples to get you started quickly can be found in the Wiki.
The license for the QuantumGate source code can be found in the
LICENSE file in the project root. In addition, QuantumGate uses third party source code covered under separate licenses. This includes an implementation of SipHash (in
QuantumGateCryptoLib\SipHash) and NewHope (
QuantumGateCryptoLib\NewHope). Refer to the
LICENSE files in the subfolders for details. Licenses for implementations of NTRUPrime (
QuantumGateCryptoLib\NTRUPrime) and Classic McEliece (
QuantumGateCryptoLib\McEliece) have not yet been obtained.
For maximum efficiency and transparency open an issue on QuantumGate's GitHub repository with any questions and/or comments that you may have. Contact information for the author can be found at https://www.kareldonk.com.
This project is self-funded. If you like it and would like to ensure its continued and speedy development, consider donating to the author. If this software has served you well (in commercial projects), consider supporting its further development through donations to the author. For details please contact the author using the above contact information. Please be advised, though, that the author does not accept contributions from governments, governmental organizations, government funded organizations, or other comparable terrorist organizations. The author values the truth and will make no compromises with regard to the software, its mission and purpose.
The author is currently especially looking for engineers who would like to review the source code, report bugs or other issues, do security audits, and especially cryptographers who want to help review the cryptographic protocols used including their implementation.