district0x Dev Update - March 6th, 2018

Development progress and product changes from district0x

The last two week cycle has been chock-full of behind the scenes updates. Our final planned Name Bazaar feature has been shipped, security and infrastructure improvements were made, smart contract work for Meme Factory is largely complete, and devops work for Meme Factory’s deployment as well as design work for the upcoming Meme Factory Community Design Polls are all proceeding.

As we draw ever closer to the planned design contests, voting rounds, and eventual launch of our newest district, expect quite a few more announcements from the district0x and Aragon development teams as each building block necessary is put into place.

Name Bazaar Updates

Completed

After a long battle with some hard to squash bugs, our port of Name Bazaar’s frontend from SemanticUI Grid to CSS Grid has been completed. Going forward, CSS will be incorporated into d0xINFRA by default, and all frontend grids will be done in CSS.

d0xINFRA Updates

In Progress

A new project has begun to create a unique wrapper for our IPFS library. This will provide us a Clojurescript interface for the js-ipfs-api library that was previously otherwise unavailable. As we pride ourselves on building a platform for future development, these are the exact kind of tasks that allow us to force-multiply.

Completed

In the last Dev Update, we mentioned a more minor upgrade to the notifications slider in order to correctly prioritize notifications beyond just time of receipt. This upgrade has been completed, and is now in full effect on Name Bazaar.

Meme Factory Updates

In Progress

Design work for the upcoming Community Design Polls is progressing at a rapid pace. We’ve been working on refining a selection of color palettes for token holders to vote on, and will move on to prototyping for the DANK logo next.

Code deployment flows for Meme Factory smart contracts are in the works. Additionally, the team is embarking on a research project implementing GraphQL into Meme Factory, with the goal of utilizing this in every district going forward.

Completed

By and large, the majority of the smart contract work for Meme Factory has been completed and documented. Moreover, we’ve produced a diagram showing the relationship between users and the smart contract flow in the registry design.

Following from left to right, the top line illustrates the submission, challenge, vote, and reveal processes for meme proposals to the Dank registry. This is the flow that most users (Creators, Challengers, Voters, and Collectors) will participate in regularly on Meme Factory.

The bottom line illustrates the parameter change process — a nearly identical corollary process. This shows how proposals to change the parameters of the registry itself walk through a similar multi stage voting process, using a different set of contracts communicating back to the main DankToken and Meme Registry contracts.

Putting all of the contract and parameter names aside, this diagram shows not only how simple token curated registries can be, but how flexible and multipurpose they are, with endless possibilities for stacking, embedding, or entwining them amongst themselves.

What’s Next?

In the coming two weeks, we’ll continue to work on Meme Factory smart contract deployments and our IPFS wrapper. Our design efforts remain laser focused on the elements of Meme Factory that will be up for vote.

Following the completion of those elements and pending some external partner launches, we will put in place the Community Design Polls for Meme Factory and allow all district0x Network Token holders to have their voice heard.