I’d like to create a playground environment for Airnode and API3 data feeds on testnets.
The API3 core tech team is (rightly) focused on production data feeds and only sets up Airnodes and data feeds on limited testnets. For example, QRNG is only on Ethereum’s testnets and data feeds are only on Polygon’s testnet. It’s also a nuisance for API providers to run first-party oracles on testnets because they can’t be monetized.
But protocols and dApps want to build on testnets for various reasons.
- They want to get familiar with API3 products, learn, and build confidence before committing to using them.
- They don’t want to spend money on gas during development.
- They may need an API or feed for development that doesn’t exist yet on the mainnet where they intend to deploy.
Additionally, APIs and data feeds on testnets don’t have the same quality, reliability, or security requirements as on mainnets.
- Devs understand that testnets are not for production and accept/expect some failures.
- There is no real money at risk when they fail.
- There is little/no reason they need to be first-party.
The API3 playground would be a set of third-party Airnodes, run by the marketing team and others who are interested in contributing, that make API3 products available on testnets so that developers on those chains can easily experiment and develop with API3 tech.
The priorities of the playground would contrast with and compliment API3 products on mainnets.
|Mainnet Products||Playground Products|
|Managed by the core tech team with quality in mind||Managed by the marketing team with growth in mind|
|Reliability and security are top priorities||Quick and easy access for developers on testnets|
|First-party oracles to minimize trust||Third-party oracles so API providers don’t need to deal with testnets|
|Limited to reputable, proven API providers||Able to experiment with other API providers|
|Requires redundant, dedicated RPC nodes||Public testnet RPC nodes are acceptable|
|Expectation that APIs and feeds will remain in service||APIs and feeds can be dropped without consequences|
|Ideal for production and late-stage testing||Ideal for learning, experimentation, and development|
In addition to the Airnodes and data feeds, the playground will have a website with features like
- Lists the APIs and feeds available on testnets
- Helps teach developers how to use them
- Allows users to make API requests and see the responses
There would be a soft goal, but with no promises, to mirror production dAPIs on the playground and to support testnets for any chain that we support its mainnet.