With the planned Sinovate Aurora mainnet upgrade scheduled to ‘go live’ at block 550 000, many of our users holding SIN, may be wondering what impact this will have on them. The purpose of this announcement is offer full visibility in this regard. In order to fully explain our current challenges and how we may be able to solve the same, we will first need to lay down a brief ‘history’ lesson – of how we got to where we are now.
Our first contact with the Sinovate team was around the beginning of the year. As with the listing of any other potential project on our decentralized service, a thorough process in terms of consideration was indeed taken. We initially held off on the listing, due to a very big update which they were preparing for. I.e. the upgrade soon to be enforced.
As a result of their unique concept of DIN nodes, it was necessary to write a custom integration. This process was concluded with the help of Sinovate developers – who confirmed that it was all correct. The end result being working Sinovate masternodes, without any apparent issues. Essentially the integration was approved by both parties at the time. With the logs themselves reflecting no major errors or warnings regarding an incorrect ‘burn’, all was reasonably assumed to be in order.
Now we need to fast forward to where we are presently
Following our preparation/integration for the update, our final tests have revealed that all is not working as anticipated. With the assistance of the Sinovate team, it has now been determined that the initial integration should not have even been possible. In other words, the initial integration was only possible as a result of a potential ‘bug’ on their end. It is now clear, that the ongoing integration of SIN nodes on the Flits app is regrettably not possible (as it currently stands).
So what does this mean for those running SIN nodes on the Flits app?
Right now this mean our users collateral will effectively become unusable in the new DIN system. We have therefore taken the decision to immediately disable SIN node deployment, as well as prevent users from adding new SIN wallets to their dashboards.
For those who currently hold SIN and/or run SIN masternodes, we can confirm that we are currently in contact with Sinovate – in an effort to find the best possible solution for all parties concerned. Discussions are ongoing and nothing definitive has been agreed upon as of yet.
We can certainly understand the frustration of all our users holding SIN. We like to remind you of the inherent risks associated with crypto, and for all to use this as a "learning curve" going forward.
As and when we have any further updates, we will of course keep you posted.
May any further questions arise, contact us at firstname.lastname@example.org or using the in-app support channel.