adChain Dev Update — September 12th, 2018

adChain Publisher Registry

The past few weeks have been heavily research focused but we have made some enhancements to the adChain Publisher Registry Dapp. We have cut the page load time in half by removing a lot of unneeded data in the contract ABI files. When we compile the contracts on our machine with Truffle, it generates a JSON file with information about the contract. Within the file there is a lot of unnecessary data for actually instantiating the contract in Web3. After we cut out this data across three different contracts, the page load time improved significantly.

The engineering team has been doing a lot of research into potential avenues for layering in value to the TCR. We have been exploring various voting methods, upgradability of smart contracts, and analytics that can be extracted from interactions with the TCR. The next few sprints we will continue this research and looking into some POCs of what some of these implementations may look like. We have a good idea of one approach that will bring in professional research and opinion into the curation process. The details of the approach we take and the tooling we are looking to use like will probably be released in the upcoming weeks.

One thing we are currently developing is a KYC process to vet a community of ad ops professionals with hopes of engaging them in domain curation and review. With professional input we can start to provide the token holders with more imperative data to assist them in voting. We are also hoping that as an ongoing process we can formally define what is deemed “quality” in a domain.