Hello, everyone. The Web3API DAO has been cultivating our ecosystem, which spans from our builders to launch partners, community, and everything in between. In the meantime, we want to share some of the progress we have made and we hope you find it as exciting as we do! 🍃
Two more development agencies have made proposals to work on Web3API. NodeFactory is going to be working on the first draft specification document of the Web3API standard. Concorde Studio is going to be creating a technical product specification and roadmap for the Web3Hub.
We would also like to welcome Torus as one of our latest launch partners. Torus is an open-source key management system that makes Web3 applications feel just like Web2. This is perfectly in-line with our initiative of bringing the Web2 developer experience to Web3. We are excited to involve them early in our pre-alpha launch journey.
But hold on, we’ve got more! Mantra DAO has been nothing but supportive of our venture. They will be joining us as an early builder. We can’t stress how galvanizing this crew is. Here’s an excerpt of a quote from JP Mullins, their Co-Founder:
“With cross-chain DeFi products at the core of what MANTRA DAO is building, this inherently involves building a tech stack that is blockchain and programming language agnostic. We believe that what Web3API is building is truly novel, and are looking forward to being a launch partner and strong participant within the Web3API DAO.”
Polyglot Web3API Development: We've refined the architecture around how we transfer data in between the different Web3API WASM modules and the Web3API client host environment. This will allow us to support any WASM- compatible language, so that developers can create Web3APIs in whatever language they're most comfortable in. Big shout out to the developers working on https://github.com/wapc for the help and inspiration here.
Web3API Dependencies: A standard around importing types and queries from external Web3APIs has been defined and implemented. This will allow for easy composability of Web3 protocols, through simple GraphQL interfaces. Additionally, you can easily walk a Web3API's dependency graph by just having access to its GraphQL schema.
Abstract Web3API Interfaces: We've identified the need for abstract Web3API interfaces, allowing for multiple 3rd parties to develop implementations of the standard interface. The specification around how this will work is still in flux, but the goal is to enable universal standards that developers can adhere to in their Web3APIs, allowing them to be used in place of any other module that implements the standard.