district0x Dev Update - January 7th, 2020

Development progress and product changes from district0x

Welcome to the first update of the new year! Given the amount of time taken off for the holidays in the last two weeks, this update will be rather thin on new information. Most initiatives we mentioned in our Christmas Eve update are being rebooted, with a few key reprioritizations that are causing a group effort to form around the release of the District Registry.

Recently, we’ve seen problems with Meme Factory involving an issue with newly submitted memes not being displayed. Though somewhat unrelated, the remedy involves resyncing our parity nodes. This has always been a shaky process, and is now compounded by the added load that the District Registry is adding to our parity node. Because of all of this, the launch of the District Registry has been put on hold.

The fix is already in the works. In fact, we’ve been testing our new infura node on the QA instance of Meme Factory for a few weeks. Once we migrate this to mainnet, most of the load to our parity instance will cease, allowing the District Registry (a relatively light-touch app with a clean on-chain history, compared to Meme Factory) to launch to it more confidently, until we can work out the kinks and complete a full migration of all apps to infura in the coming months.

All of this has come to a head in the last 24 hours for the organization, so we’re somewhat reactively initiating this gameplan, and focusing on the steps required to both recover Meme Factory and get the District Registry in a stable, launch-ready state as soon as possible.

We may have more specific updates in the coming week but if not, we’ll be sure to have a complete breakdown of development progress per usual in the next update.