The Intense Coin blockchain developers have been hard at work on the very core of our cryptocurrency: the daemon and wallet.
As the Intense VPN team discussed and finalized system architecture design in the MVP requirements, we realized that VPN exit nodes and clients would need a mechanism of securely authenticating. Ideally, this would be performed on the blockchain (“on-chain”). How does one go about sharing private information between two parties on a blockchain that everyone can see? Meet integrated addresses from Monero: 8 bytes of encrypted data that are known only to the sender and receiver, yet are present on the blockchain!
After the development team performed some analysis on the Monero codebase to see what would be involved in merging the integrated address feature into the Intense codebase, we realized that performing a full rebase to Monero would make a lot more sense. The Monero codebase is extensively developed and maintained, and is tremendously more mature and reliable than the Bytecoin codebase that Intense is based upon now. In fact, nearly all of the updates and revisions to block sizes and transactions could have been avoided in Intense if it was originally forked from Monero rather than Bytecoin. Therefore, the decision was made to rebase to Monero, if and only if our blockchain could be made compatible with the Monero daemon/wallet.
Today, we are very excited to share that the Monero-based daemon has been made fully compliant with the Intense blockchain. We are still working on polishing some features and analyzing the long-term implications of a couple aspects of the Monero codebase, but the Monero-based daemon and command line wallet are available for use now. We have tested the abilities to create, save, and restore wallets generated with the new wallet, and send and receive transactions, but be cautious that this is still strictly pre-release. Any use is at your own risk. The Monero-based wallet does not currently have the capability to open or read wallets created by Intense daemon/wallets (and vice versa), although this will be resolved soon. See version 18.104.22.168 release on Github, and follow our XMR rebase tree here. If you’re a developer, please feel free to contribute as we thrive on the open source model!
Rebasing to Monero offers us significantly increased compatibility with exchanges and third-party software such as pools and block explorers, and allows us access to many new features such as passphrase/word-based wallet seed recovery, RingCT (not currently in effect), reduced sync time, improved database management, and overall improved stability and reliability. In short, this was a difficult process for the development team, but it will open a lot of doors for us.
Stay tuned for more information on release candidates of the console (CLI) and graphical (GUI) Monero-based software!