dAPI Team Cycle Update November 2022 — January 2023
I want to start this update off with apologizing for the lack of updates during the cycle itself, despite me promising monthly updates in the proposal. This will change going forward and the dAPI team will adhere to the monthly update cycle to keep the DAO informed about our progress. One of the major reasons there have been no updates is that many would have described them as boring or not “update-worthy”, hence my reluctance to write them up.
We spent the past three months building out critical infrastructure that will be required to roll out dAPIs in our four phased approach. This began with migrating our dAPI and Beacon structure from a Github based approach to a dedicated database. Additionally we worked on optimizing our event collectors to allow us to collect and analyze data for all chains where dapiserver.sol is deployed on. Some of this data was made available through APIs in order to display them on the API3 Market in preparation for the launch of Phase 1 (e.g. average gas consumption). This brings me to the last major item we’ve worked on — the API3 Market.
The current version of the market is being adjusted for our new approach to dAPIs. As mentioned in my previous article, dAPIs will start of as self-funded data feeds (previously called bring-your-own-gas) that are operated by a single provider. They allow us to offer any potential data without having much overhead (e.g. gas management) on any chain, thus allowing anybody to try out their desired data before committing to managed dAPIs. If people are going to use self-funded dAPIs, we’ll need to be giving them the tools to use them, which is where a lot of the effort this cycle went. The API3 Market will allow users to directly fund respective sponsor wallets, see the average gas consumption of a dAPI, how long it is approximately funded for, etc. Potential users won’t have to interact with API3 in any way for using self-funded dAPIs (given that their desired data exists). The only requirement is sending funds to the sponsor wallet that powers a specific dAPI, which will “bring it to life”.
When, wen, wen? We currently have an ongoing audit on the new dapiserver.sol contract, that was adjusted for the changes required for OEV. Alongside waiting for these audit results, we’re making final adjustments to the API3 Market. The current aim is a release towards the end of February, which shouldn’t be seen as a “deadline” as this date can still be heavily impacted by the audits results etc. The API3 Market already displays a banner for users that mentions the upcoming switch to a new DapiServer contract, which is required due to the immutable nature of it.
The release of Phase 1 is just around the corner, which means that self-funded dAPIs will be available on Ethereum, Polygon, BNB Chain, Avalanche, Optimism, Arbitrum, Metis, Moonbeam, Moonriver, RSK, Milkomeda, Gnosis Chain and Fantom. Specific data types on those chains can already be requested using this form.
If you have any questions, you can always shoot us a message in our discord. Cheers.