As you know, MinexSystems is a company working on a wide range of blockchain products. And even though we’ve been recently focusing primarily on MinexPay cards, they’re part of an entire complex system where all solutions are interconnected in one way or another.
Today, the highlight is on MinexWallet, a product that allows storing your crypto assets online without installing a desktop version and that is as secure as traditional wallets.
We are continuing to develop MinexWallet as a complete platform for working with MinexPay cards. For this purpose, we are adding the card functionality to the wallet, the beta version of which has been tested by our community. We will then connect the bank API with this functionality at the same time creating support services to ensure the work of this platform.
And we will top it all off with some MinexWallet’s development updates!
Connecting Synchronizer with the Bitcoin blockchain
In the first version, we are implementing the Bitcoin blockchain for the private and public testing purposes. Synchronizer is our internal microservice-middleman that provides an interlayer between the blockchain and our microservices needed for the wallet’s operation.
This is what we’ve been facing so far: the Bitcoin blockchain is currently 280 GB. We are running all these blocks through our Synchronizer, and it takes a significant amount of time — already a couple of weeks, considering that we are using all our servers. Currently, we’ve already passed 250,000 blocks, so the halfway point is already behind us — yet not without issues.
As it is an external blockchain, we need to be sure of security of our users’ crypto funds and successful transactions. Our Synchronizer has gone mad once it has found two blocks with the same transaction on the Bitcoin’s blockchain. This issue has been resolved in the Bitcoin blockchain, but it has left the traces in the network. Therefore, we had to change the logic of our Synchronizer for the Bitcoin blockchain.
Setting up a Bitcoin test net to test the wallet
During this process, we have re-compiled our node because during installation it was adding extra peers, which were listed in the code of the Bitcoin network.
Finishing touches for the functionality of bank operators
In some cases, you cannot bypass operators’ work, such as identifying suspicious payments, their validation, and handling some manual payments. Although users do not see them at work, it is still being done. Our internal functionality can ease the operators’ work. After testing is complete, these processes will be automated.
And this is it for today. Stay tuned! More updates and news are coming in the meantime.
Twitter|Telegram|Reddit|Medium|Facebook|YouTube|GitHub|Bitcointalk