district0x Dev Update - April 14th, 2020

Development progress and product changes from district0x

Another development cycle is “in the books” and another dev update gets put to paper. The past few weeks mostly contained bugfixing and testing across our suite of dApps, but also some exciting news and changes to our newest application the District Designer.

The District Registry

Several modules shared across The District Registry and Meme Factory were subject to bugfixes recently, all introduced as a result of our recent updates involving EIP-55 and our migration to Infura. The first pertains to the way we handle addresses (capitalization and such) and the other relates to a problem with transaction history not appearing.

After a few different solutions were tried and tested, we were able to restore functionality to our in-app transaction log. Unfortunately, due to the constraints enforced by browsers and our desire to keep multi-device functions intact, there was no way to make this apply retroactively. Going forward, only new transactions made after the update will appear in the transaction log. This change is still pending some final refactoring of a painful browser test, but will likely be deployed to the live app before the end of the week, with Meme Factory’s counterpart coming shortly after.

Ethlance

Ethlance’s server is nearing completion, with most systems built and documented and testing suites refined. We’ve integrated our contracts with the standard Bounties Network contracts and we’ve developed a syncer and resolver. We’ve also cleared the hurdle with ingesting the necessary IPFS data in a way that was different from Meme Factory. Besides the ongoing front-end work with reframe, there is little left to do other than start attaching all the pieces together.

At this point, we’ve begun integration testing by hand-creating some jobs contracts as well as populating IPFS with test data. This has allowed us to begin experimenting with our events record and replay system, which we hope to make far more robust on day 1 than our previous applications.

The District Designer

The District Designer has been coming along nicely since our last update. The wireframing process is 95+% complete, with only the landing page and one page related to styling left to complete before our original vision has been framed. Once this is done, we can move towards the design phase as well as a more indepth technical planning phase.

However, we realized during the course of making the token parser that we would already be doing most of the work needed to implement two features that would enable quite powerful options for users, and leverage work we’ve done on side projects in the past. In particular, we would like to design and develop a TCR creation module, as well as a token creation module, both of which could be used as a basis for the District creation process. We’ve been adding those additional features to our wireframes this week, and expect to have complete frames in the scope of the next update.

These are uncertain times for many across our industry and all others. We’re thankful and lucky to have a very clear path laid before us that hasn’t been subject to much change. With any luck, we’ll be able to continue forward unabated for the many releases to come.