It's been quite a week. As you may have seen, Bittrex announced on Friday that they will no longer be servicing US customers. We're now focused on getting listed on other exchanges and speaking to a market maker tomorrow who can help us with that, including Kucoin, Gate, IO, and Bybit. If you have a favorite exchange you'd like to see us on, be sure to post your requests in response to this tweet when I publish the recording.

Getting listed on exchanges wasn't a priority for us recently since we were focused on getting 5.1 done, but it's become more important this past week. We've already gotten TradeOgre listed and have been working with them to utilize all the commands we developed, like finance debit.

We've been in consistent communication with TradeOgre and working through any issues or snags that may arise. The 5.1 core is working well, with just a few little bugs that we've been resolving. I'm glad Trader Girl is really cool to have worked with us and get us listed so quickly. TradeOgre was really a community effort, so props and kudos to the community.

We just released a new beta version of the mobile wallet last week, which has been well-received with positive feedback. However, we've been working out some bugs related to Sigchains, such as an issue with Op migrate, which took a couple of rounds to get right. But, everyone should be able to log in now.

Currently, we're working on filters and queries using the query DSL built into the API. After this, it's mostly cosmetic adjustments. A bug with receiving legacy transactions has been fixed, and we're still working on a couple of crashes that happen on the iOS wallet version.

The 5.2 update is still in progress, and we plan to release the desktop wallet on April 26th, as part of our efforts towards maintaining more consistent and predictable timelines. We'll be doing another beta release, potentially tomorrow or early next week, and by Monday, we expect to have another mobile beta for both Android and iOS that should resolve many of the issues.

We're also working on adding a synchronization percentage so that users can see their Sigchains syncing, especially for those with very large Sigchains that can take some time to download.

A lot of time has been spent on reliability checking, with the implementation of a reliability rebroadcasting protocol to ensure that transactions are broadcasted to the network to make sure it's received. This is a significant improvement from our first mobile release where accounts and transactions couldn't be registered onto the blockchain without an internet connection.

We've also started the pre-approval process for the Google Play Store and App Store, and we're optimistic that phase one, two, and three will come fairly close to each other.

We're grateful that we were able to get on other exchange listings quickly, and we're in conversation with Komodo for the atomic DEX. The market maker has been helpful, and we're excited to keep making progress towards our goals.

So basically, there was a new iOS update that caused some delays in processing, kind of like the April Fools' joke that happened unintentionally. As a private tester, I was excited to try out the new version, but I accidentally posted the wrong version number on Twitter, which caused some confusion.

The new update has received a lot of positive feedback and has resolved many of the issues people were experiencing. It's not easy to get a node running on a phone, let alone a smart contract platform, but it's been a long haul and we've made a lot of progress thanks to the hard work of our team.

If you do come across any crashes or issues, please submit crash reports, as they are very useful in debugging and improving the platform. We've upgraded our seed nodes to RC 14, which will most likely be the next release for iOS and Android.

We're still working on the 5.2 update, which should be ready in a few weeks after some more testing. We'll be posting about it soon and looking for additional developers to help test it.

In terms of future features, we're working on the 6.0 update, which will include pooled staking and a file system that will allow for decentralized hosting mechanisms. We're also working on remote login, peer to peer messaging, and a crypto API for the 5.2 update.

The team is working on decentralized hosting, which will allow you to monetize your hard drive by submitting files into the file system and have them hosted remotely. The system will enable you to deploy a website without the need for a web server. Initially, it will be a file delivery protocol, but the team is working on adding a hook that would allow you to add a PHP interpreter or any other server-side language.

Nexus is also planning to develop a distributed MySQL database, which will enable users to one-click deploy a WordPress on Nexus. Additionally, they are working on LLP SQL, which will take a MySQL protocol and make an LLP with it, enabling users to have distributed database systems, distributed file storage, and distributed search.

The team is also planning on adding Dow global voting layers and augmented contracts, which will allow users to invoke a remote code without necessarily requiring a contract or a debit. Essentially, it will enable users to create any code within an object register that are functions or methods to modify a state in some way.

Nexus's smart contract functionality will be improved, making it more comparable to Ethereum's smart contracts. The team is working on infinite loops and the whole Turing completeness because Ethereum isn't Turing complete, it's quasi-Turing complete.

Furthermore, Nexus is planning to reduce the size of the blocks, aiming to get it to 600-700 megabytes, depending on the size of the keychain. The new desktop wallet will support client mode, allowing users to have all the mobile wallet functionality without a mobile wallet.

Lastly, the team is working on upgrading the seed nodes to support doing a more sequential read, which will help in synchronizing the wallet faster. They have fixed the bug in the sequential read system to prevent it from getting stuck on a zero. Nexus is committed to reducing battery life while synchronizing faster.

The team hopes to have more new feature buildouts in the coming weeks. We've made some good progress on the 5.2 features we're working on. Right now, we're sitting at about 60-70% completion. We just need to work on a few more protocol messages and then we'll be ready to fire everything up.

To support remote logins, we need to add some machinery inside the API. Once that's done, we'll start testing it within the next couple of weeks. The plan is to finish building it out this week, and then do some internal testing the following week with some of my colleagues: Sohan, Aeonwise, and any of you who wants to help with that.

After that, we'll be ready to let more developers start testing it out as well. Overall, it's been a great week for development and I'm excited for what's to come.

Anyway, I've got to run and fix some bugs, so thanks for your time and I'll catch you in the next update!

For a recording of the entire talk: https://twitter.com/i/spaces/1eaKbrpLXzVKX

For more info on Nexus: https//www.nexus.io