Web3API – Web3 WASM runtime for universally compatible smart contract APIs

Key Highlights

🏆 Winner at HackFS. A hackathon featuring judges like Vitalik Buterin, Juan Benet from Protocol Labs, Austin Griffith from Ethereum Foundation and many more. The hackathon was important for Web3API for getting initial feedback from industry leaders and onboarding partners. The team were presented four awards at the hackathon issued by Protocol Labs, the Ethereum Foundation, Fleek and ENS.

Diagram

Description automatically generated

👨‍💻 The engineering teams behind the project have a wealth of experience in the crypto space, working and building custom integrations for Balancer, Gnosis, Aragon, ParaSwap, Ren, Wyre, MetaMask and more.

🙌 Successfully onboarded several launch partners, including Gnosis Safe, DXdao, Abridged, Fleek, Squad Games and Pocket.

Graphical user interface, application

Description automatically generated

Why We Like It

Energetic and highly compatible team with in-depth experience working for and with notable web3 protocols.

The team has a strong and varied business network, critical for bootstrapping phases and lighthouse partner onboarding.

Tackling a universally felt pain-point in the industry.

Early indicators of problem/solution validation in the form of keen launch partners and support from the likes of the Ethereum Foundation and Protocol Labs.

Community governed principles and values from the onset — the core development team are congruent with the ethos of the industry.


Project Description

What

Web3API is aiming to establish a new standard for integrating Web3 into applications that is as easy and simple as integrating Web2 APIs.

It achieves this by empowering dApp developers to integrate any Web3 protocol through simple GraphQL, a widely adopted query language in the world of Web2. The Web3API packages third-party developers are integrating are written in secure, efficient and portable WebAssembly by protocol developers.

Today, web3 integrations require embedding a variety of non-standardised web3 SDKs consisting of JavaScript wrappers and smart contract ABIs. With Web3API, however, applications will just need to integrate the Web3API client to be able to communicate with all available decentralised Web3API endpoints.

Developers will be able to discover, use and integrate the API(s) of their choice via the Web3Hub – the portal to the Web3API ecosystem.

Graphical user interface

Description automatically generatedWeb3API Portal

Why

Target Market

  • Web3 application & protocol developers
    • Application developers building decentralised applications that need to integrate with other DeFi or Web3 protocols.
    • Protocol developers wanting to make their protocol easy and hassle-free for application developers to integrate.
  • Non-JavaScript developers
    • Web3 can now be integrated into games and mobile & IoT applications easily.
  • Enterprises
    • Web3API can act as the missing Web3 tooling for the enterprise development environment (e.g. server-side applications, IoT networks).

What’s the Problem?

Achieving ‘composability’ and ‘extendability’ on Ethereum is a burden for developers today. Developers have no choice but to embed a variety of web3 SDKs comprising of JavaScript wrappers and smart contract ABIs to achieve cross-protocol communications for their application.

This leads to an integration problem due to:

  • Lack of standardisation — demanding bespoke integrations on a case-by-case basis. Lack of standardisation also risks technology failure, since all the SDKs will need to be individually maintained, monitored and upgraded when necessary. This means that an app developer needs to re-publish their application whenever an integrated protocol publishes an upgrade.
  • Capped composability and extendability— integrating multiple JavaScript SDKs into an application bloats the package, limiting the number of integrations an application can handle and therefore the extent of web3 features that can be offered to end-users.

The Web3API Solution — Value Propositions

  • Saves time and reduces technology risk by removing the need for JavaScript SDKs and introducing standardisation — Developers will no longer be required to embed JavaScript wrappers for each new protocol they want to integrate.
  • Increases the probability of web3 adoption — protocol developers will be incentivized to create Web3APIs for their smart contract protocols to make integration easier for others. Integrating with other protocols results in positive-sum outcomes.
  • Unlocks multi-platform functionality — Web3APIs are universal and can run in any language. This unlocks application integrations for mobile, games, and IoT devices. Protocol developers no longer have to maintain multiple SDKs in various languages.
  • “Hyper-composability” — Web3API allows decentralised applications to extend their available functionalities through integrations that far exceed what is possible today. Since the need for Javascript SDKs is eliminated, bloating of packages significantly reduces, allowing for more integrations with other protocols. This is particularly useful for complex decentralised applications that need to combine multiple DeFi protocols, connect to governance modules or integrate multiple Web3 networks at the same time.
  • All executed at runtime — Web3API does not rely on any central servers. Each protocol will have their own ENS address designated to their Web3API, e.g. “api.uniswap.eth”. After an incoming request, the Web3API Client will look at the respective protocol’s ENS address associated with their API to receive a content identifier in the form of an IPFS hash, which will be used for receiving a Web3API schema. Afterwards, the schema and WASM modules will be loaded and instantiated at runtime and the request will be executed. As a final step, the result will be returned.
  • “Extendability” — Web3API improves the network effect of protocols by allowing developers to easily and autonomously add new extensions to existing features.
  • Allows decentralised applications to be dynamic — Features within dApps can now be upgraded without requiring the app to rebuild itself. This allows for dynamic applications that can automatically upgrade, and have different views based on each end-user’s needs and preferences.
  • Eliminates need for developers to create custom UIs for their dApp integrations — connecting with web3 protocols via a Web3 API allows developers to utilize pre-existing user-friendly front-end interfaces with the new features added automatically. This proves very valuable when developers must deal with custom contracts, like custom governance.

Taking into consideration the above-mentioned value propositions, Web3API could arguably unlock many use cases that are yet to be fully realised in crypto.

How

Discovering and integrating APIs via the Web3Hub

Developers wishing to discoveruse or integrate these next-generation APIs can do so via the Web3Hub, an open-source platform being developed by the Web3API team. Similar to GitHub, users of the Web3Hub will be able to see a list of all the different available APIs, including their subdomains and versioning.

Once a user discovers their API of choice, the Web3Hub will give developers three different options when interacting with the respective API: (1) View the GraphQL schema; (2) Query the schema; or (3) Interact with a dashboard view.

The dashboard acts as a modular UI piece. It has the ability to auto-generate a UI based on the Web3API’s functionalities. As an example, a dashboard for the Uniswap Web3API could easily be spun up via the Web3Hub that auto-generates a user-friendly form to facilitate token swaps.

The auto-generated dashboards made possible by the Web3Hub make the protocol-to-protocol integration process even simpler for developers. Once a developer customises their application by combining multiple protocols via their respective APIs, the dashboard adapts by automatically incorporating the new features and presenting them in a user-friendly way.

Graphical user interface

Description automatically generatedDashboard UI

Graphical user interface

Description automatically generatedDashboard Configuration

Developing a Web3 enabled application using Web3API

Application developers integrating Web3APIs only have to include the Web3API Client inside of their app. The client is very light-weight and enables them to send queries to any API of their choosing through GraphQL.

With GraphQL, the process of integrating and interacting with Web3APIs becomes almost exactly like integrating a Web2 GraphQL API.

Developing an API for a decentralised protocol

Developers can create a Web3API for their contracts in any language of their choice, as long as it compiles to WebAssembly. This includes but is not limited to: Rust, Go, Java, TypeScript (AssemblyScript), C#, C/C++.

Web3APIs use GraphQL as the common interface language. A developer of a Web3 protocol can easily define a typical GraphQl schema, which allows for read and write functionality of the respective Web3 protocol. Developers can also publish additional documentation with their GraphQL schemas.

WebAssembly (WASM)

WASM is a lightweight and portable assembly standard, which achieves native code execution speed in any environment, including the browser. Since developers can run WASM within all popular languages, it allows for portable and efficient code. By using WASM, Web3API can quickly perform complex actions within any type of application.

Additionally, WASM is responsible for Web3API’s security and speed advantages over JavaScript. Firstly, its execution speed is much faster than JavaScript. Secondly, WASM is executed within a secure virtual machine, meaning that Web3APIs cannot reach inside an application’s memory. In turn, this keeps private keys safe and prevents common JavaScript-based attacks.

Furthermore, the execution of Web3API WASM is always verifiable as the WASM modules are downloaded from IPFS via designated hashes, meaning that the resulting executable code will never change.


The Web3API DAO

The DAO will govern all of Web3API. This includes financial control, on-boarding of new developer teams, partnerships, future control over the API standard and much more.

Currently, this is mostly focused around capital allocation, approval of roadmaps and ratification of MOUs. The most recent spending proposal for October can be found here.

The current process involves using Snapshot as an off-chain signalling mechanism to gauge initial sentiment. If consensus is reached on Snapshot an on-chain proposal will be created on Aragon if needed. In both cases, your number of votes is equal to the number of tokens you hold.

The current DAO configurations can be found here.

Web3API is an ecosystem standard that requires governance, funding, and continual adoption. Instead of having a single company building this project initially, causing rivalrous tendencies to propagate, the initial creators think it’s best to be building in a community first manner to maximize adoption and quality. This model is similar to that of the blockchain foundation model.

The DAO is currently spearheaded by a collection of individual contributors and credible builder teams, including dOrgNodeFactory, and Concorde Studio.


Governance Token Thesis

The Web3API vision is to make the Web3Hub the go-to portal for developers to discover, integrate and use the array of Web3APIs available. In the mid-to-long term, the governance token aims to serve as a work token whereby holders will be given control and responsibilities over the Web3Hub in return for token rewards. Decision-making power will be vital for things such as stewardship, curation and accrediting skilled-developers wishing to contribute to the ecosystem.

If the Web3Hub fulfils its vision as being the go-to gateway for APIs in blockchain, we assume that application providers will be incentivised to increase their share of voting power in the Web3API ecosystem. We believe that this demand will stem from protocol developers (and their respective business teams) wanting to ensure widespread exposure of their product and respective API in a bid to boost adoption.

The Web3API team are also exploring other additional utility mechanisms that may prove effective in the nearer term for its token. These include:

  • Application mining — Web3 protocols such as Aaave or Compound could accelerate their network effects through incentivising other application developers to build on their protocol through token rewards. This token-fuelled partnership/integration strategy has been termed “application mining”. Since Web3API aims to play a vital role in the integration process, the team is exploring ways in how some of the application mining rewards offered by the protocols can be captured by Web3API.
  • Premium services — Several API platforms have established a proven business model in Web2. They monetise through their managed services, which for example includes analytics, automation and enterprise tiers with custom dashboards. For instance, RapidAPI is being used by Reddit, Delta and Cisco. The Web3API team is exploring ways it could create premium services that can be sold to developers, with the revenues being collected by the Web3API DAO. Such premium features and insights that may have its place in the market may include analytical tools, API ratings, feature-rich dashboards, featuring an API at the top of the page and more.

A picture containing diagram

Description automatically generated

Bootstrapping the Supply Side

Building dashboards and APIs in-house to showcase benefits

To showcase the benefits of Web3API, the core team aims to channel some of its own development resources to building the initial wrapper APIs for several pre-existing protocols.

Due to the permissionless nature of the blockchain ecosystem, Web3API does not need permission to create a dashboard or a Web3API. For instance, they could easily create a Web3API at uniswap.web3api.eth and present the functionalities to the Uniswap founders and core team. If the Uniswap core team likes what they see, they may be inclined to fork it and upload it to their own ENS address. In return, Web3API will not only get important feedback on their product but also get direct exposure to a wide range of other projects that are seeking ways to integrate with Uniswap (in this example).

Obviously, this would result in considerable development work for the Web3API team. Therefore, current builders aim to focus only on high-profile and in-demand protocols.

Work Token Rewards

Web3API will be exploring ways to not only inspire developers for code contributions to the protocol but also ways to use token incentives to encourage API curation, audits, reviews and advanced managed services.

The Web3API DAO would serve as the standard-body, responsible for the accreditation of developers. Therefore, the DAO will appoint and verify certified consultants, which could be hired by projects wanting to build upon the Web3API standard.

Bootstrapping the Demand Side

Onboarding light-house partners and creating compelling case studies

The Web3API team is working alongside its diverse set of launch partners to help them utilise the full benefits of the technology. Aside from easing integration, the team aims to work with its partners to take full advantage of the hyper-composable characteristics in a bid to unlock innovative new capabilities unseen in this market.

In turn, Web3API wishes to use these case studies to drive marketing and prospect partner onboarding.


Stage of Maturity

A picture containing text, monitor, screenshot

Description automatically generated

Commercial Development

Web3API already has onboarded several demand-side launch partners (signed MOUs) including Gnosis Safe, DXdao, Abridged, Fleek and Pocket. As its early evangelists, these partners will play a vital role in providing feedback and influencing the roadmap.

Product Development

  • Web3API is at the Pre-Alpha stage.
Timeline

Description automatically generated

Token Distribution Details

Total Supply and DAO Voting

For the first 16 months, the total supply will be capped at 20,000 W3API tokens with the above distribution details. Afterwards, the DAO members will vote on further emission plans. This can also include plans for further fundraising activities or additional developer incentivization.

The DAO will further vote on when the tokens are to be unlocked and the corresponding vesting schedules for the funders and the builders.

DAO Configuration

Each proposal will be open for 7 days. For a proposal to pass at least 10% of the total supply needs to vote in favour of it. Furthermore, at least 60% of the casted votes need to vote in favour of the proposal for it to pass.

Pre-Seed Funders

Seed funders will receive 20% of the total supply. The vesting and unlock timing depends on the outcome of a DAO vote.

Table

Description automatically generated

Current progress and pre-seed funding contributors can be checked here.

The Pre-Seed Funder round will end on December 31st. Any unsold tokens will be distributed pro-rata to existing Pre-Seed Funders.

Pre-Seed Builders

Pre-seed builders will receive 20% of the total supply and are subject to the to-be-determined vesting schedules. The allocations and related work of each pre-seed builder can be found here.

Dev Mining

The DAO will distribute 60% of the total supply to the highest performing builders over a period of approximately 16 months (3.75% of total supply per month). This is meant to rapidly scale software and business development efforts while distributing control to the ecosystem’s most valuable contributors.

Both “builder” allocations will not only be paid out to developers but can be used for general value-add commitments as well, like for example business development or marketing activities.

Use of Funds

The successful completion of the raise will give the DAO enough runway for 12-16 months. It is anticipated that the DAO will allocate funds for:

●      Development – $42,000 / month

●      Ops & Adoption – $15,000 / month

●      Legal & SaaS – $5,500 / month


The Rarestone team has recently taken a position in Web3API based on the analysis provided in this written brief. This is meant to disclose any perceived conflict of interest and should not be mistaken as a recommendation to purchase Web3API tokens. This overview has been prepared solely for informational purposes and is not to be considered as investment advice. It does not purport to contain all of the information that may be required or desirable to evaluate all of the factors that might be relevant to a potential investor, and any recipient hereof should conduct its own due diligence investigation and analysis to make an independent determination of the suitability and consequences of any action.