district0x Dev Update - November 30th, 2021

Development progress and product changes from district0x

Published in
3 min readDec 1, 2021

--

Name Bazaar

In our last post we mentioned investigating the use of Wyvern protocol for Name Bazaar marketplace listings. While we originally were going to hold off on this for a future upgrade, we’ve recognized that without fee-free listings, we will not be competitive with the wider marketplace landscape.

  • As such, we’ve secured commitments from developers to help build out this feature set, and we will be holding off on Name Bazaar relaunch until this is done.
  • We’ve continued to battle-test and harden the Name Bazaar servers, investigating an issue that seems to be preventing restarts when the servers hiccup.
  • We are continuing to solicit any early listing of names we can find from the wider community. If you would like incentive or assistance with doing so, reach out to us at hello@district0x.io

d0xINFRA

Most of our infrastructure work has been dedicated towards getting the various QA and mainnet servers up and running for our upcoming application launches. However, we’ve still made some progress:

  • We’ve been tackling a larger project of rebuilding our nginx configuration, as well as reforming our AWS container methodology.

Meme Factory

Meme Factory’s relaunch has been moving along swimmingly, with the polygon testnet versions getting built out for main functionality, and accessory functions continuing forward as well:

  • Testnet instances were deployed to Görli and Mumbai, allowing us to effectively test bridging contracts in a QA environment as well as approach the total app functionality on Polygon.
  • We built a new component to check whether users are on the right chain/RPC based on their browser wallet.
  • We solved an issue with Infura not supporting our websocket selection for Polygon
  • We’ve fixed several small issues that crept up during QA testing routines
  • In the meantime, we’ve also been building out a UI for our NFT and token bridge between Polygon and ETH mainnet, as well as continuing to investigate more robust solutions for a DANK faucet on Polygon that doesn’t rely on Oracalize.

Streamtide

Streamtide has been in stride, building out countless pages and connecting them to their respective backend components.

  • We completed UI integrations and put together the admin page, an essential tool for QA testing.
  • We updated an important python script to fetch event results from IPFS. This required a redeployment to mainnet to continue testing.
  • Once we had this script working with our API regent, we had some troubles on certain related to tests and had to reach out to external vendors for advice.
  • We improved many minor parts of the front-end, including better gas estimates and better pricing on transactions.
  • We created a new repo to push all of these updates to.

Ethlance

  • We built out tooling and final touches on Ethlance before sending out for review. This included a pull request to improve the district server contracts in order to surface more errors and get more robust logging.
  • Meanwhile, started on the integration between contracts and backend. This included several pages, finishing most recently with the new job page.
  • We got tests running on our new CI setup.
  • We briefly looked into the new ZKsync EVM updates, but ultimately don’t have a clear path forward there.
  • We took an opportunity to improve the codebase flow from a high level that’s a bit of a middle ground solution between our old philosophy and our new one.
  • We rooted out some unexpected problems with our GraphQL queries not properly propagating through our backend. This work continues this week.

Joining the district0x DAO

For more information about the district0x network,

--

--