Airnode and Beacon Implementations for Pyliquid and Liquid Tooling.
- Docker: Includes set of images with necessary infrastructure to spin off the Service including the API(s) and Liquid infrastructure
- pyliquid: All the configurations and support utilities to set up the actual Airnode.
- src: Set of scripts to automated administrative tasks. Making use of @api3/airnode-adming library
- bin: Any shell script to be used either by typescript or docker.
- assets: Suite of outputs from src scripts. Like addresses, mnemonics, etc.
- dev: Set of configuration for 'dev' stage Airnodes. Follows the suggested structure from Airnode documentation
- utils: Set of scripts that might be of use across the whole repository. Including stuff like reading or writting JSON files.
- templates: Set of example files that are used in the repository, like the secrets for Airnode deployment.
Current goal: We want to build a basic environment to test out simple tasks being called from an EVM solidty smart contract that are reflected in Liquid. Current state: We are midway to finish up the API on our brother repository. We'll keep updating the docker images and configuration files based on the progress, keep track of both on their respective repositories.
Features: - DeFi Protocol for assets collaterization - Production ready Airnode for PyLiquid API - Terraform files for quick infrastructure provisioning - dApis for Prices Feeds from BitFinex
- Package Manager:
pnpm - Docker OS:
Ubuntu