It’s a month since the last update, sorry for making the community have to wait that long, but it’s always ideal to update the community on the visible outputs rather than repeating the same thing of development progress week over week.
The following are things we’ve done in the past few weeks:
Incognito - Binance Smart Chain bridge
This has been done, a staging Incognito app might be found in the topic, please give it a try and let us know your thoughts prior to its official release on production environment around next week.
The privacy V2 protocol has been completed and deployed on Testnet environment already. The thing left is to upgrade the Incognito app to the new privacy protocol, this is almost done too, a staging app for this upgrade will be released within next week so that everyone in the Incognito community can experience it and give us feedback or bug report if any.
Since this is one of the biggest upgrades of Incognito, it’s vital for us to be able to hunt as many bugs as possible prior to the official launch and we’re planning to organize a short and simple bug bounty program for it. The bounty details will also be announced along with the staging app release next week.
Also, a series of posts to explain changes in Privacy v2 will be published from next week till the official launch date.
The Incognito SDK (version 2)
We’ve just released a beta version of Incognito SDK V2, you can check it out here. This is of much higher quality and better documentation as compared to the previous version.
The SDK will help Incognito integrate with external platforms easier. Developers will also have a handy tool to build their own privacy applications on top Incognito chain.
The new Mempool
Besides the new development, we’re also figuring out many ways to improve the platform continually. One of them is the new mempool that improved transaction throughput significantly - about 2 - 2.5 times as compared to the old one.
We’ve just detected an issue with the randomness assignment mechanism that caused the unbalanced validator number among shards. The bug has to be fixed before enabling slashing. Otherwise, a good, healthy and honest validator may also be slashed just because of insufficient time for it to sync required data for contributing to the consensus process.
For this reason, we’ve decided to delay slashing one more time till August. But in the meantime, we still try our best to support node owners with node issues. We believe that Incognito is having stronger validators than itself in the last couple of months that help the network more robust and resilient.
Many big things are coming soon, thanks for still being here!