This article was first published on district0x - Medium
Development progress and product changes from district0x
In our last update, we noted our ongoing struggle with the current gas situation on the Ethereum network, and the impasse at which it puts us in regards to future application development. This situation has progressed unabated, and we’ve committed as a project to establishing a new direction for future endeavors. This will be described in greater detail in a series of separate upcoming posts. Stay tuned.
In the meantime, much of the team has been returning to different pieces of the Ethlance application in an attempt to fill in any remaining gaps and fix problems we’ve left unresolved. Primary among these is the GraphQL library upgrade, which is necessary to clear us for complete front end integration. The majority of our current issues stem from a very small subsection of middlewares within our GraphQL library. Working with these has been in a word, unfun. The typical kind of whack-a-mole problem solving that tends to crop up near the end of any development cycle.
Besides this, work on the District Designer has proceeded for a weeks worth of development progress, but the same reckoning with regards to fees will ultimately plague this application too, despite our best efforts to design a lightweight solution ahead of time. As a result, we’re critically analyzing the work we’ve already done, and seeing if we can’t instead use the District Designer or its components as the basis of a different kind of “generator” application for something other than marketplaces in our traditional style. Again, more info will be provided on this when our brainstorming solidifies.
Lastly, we are still in search of new developers to join the squad and help us build our newest generation of dApps. Check out our job listing below.
district0x is a global organization ...
To keep reading, please go to the original article at:
district0x - Medium