This project provides a backend for Node Operators participating in Charli3's ODV (On-Demand Validation) Oracle network. It is designed to fetch, aggregate and validate price data for specified assets, and participate in the ODV protocol through feed signing and transaction aggregation. The node utilizes the pycardano library for Cardano blockchain interactions.

• Governance
• Support
• Maintainers
• Changelog

This project uses Poetry to manage dependencies. If you don't have Poetry installed, you can install it by following the instructions at Poetry documentation.

To install the required Python packages, run:

poetry install

Next, you will need to create a config.yml file containing the necessary configuration settings. You can use the provided example-config.yml as a starting point.

To run the backend locally, execute the main.py script inside the Poetry environment:

poetry run python node/main.py run -c config.yml

Build image and run two nodes using this command:

docker compose build node1 && docker compose up -d

Attach to one of the nodes:

docker compose logs -f node1

The backend can be configured using a config.yml file. This file allows you to customize various settings such as:

• ChainQuery configurations (BlockFrost and Ogmios)
• Node (addresses, keys, mnemonics, etc.)
• Data providers for base and quote currency rates

Refer to the example-config.yml file for an example configuration.

The ODV Node Operator Backend provides the following core functionality:

• ODV Node Api Implementation:

  • Feed value request handling
  • Aggregation Transaction signing

• Price Data Management:

  • Multi-source price aggregation
  • Outlier detection and filtering
  • Quote rate conversion

• Blockchain Integration:

  • Cardano network interaction via ChainQuery
  • Oracle NFT and Node Eligibility validations

This repository is licensed under the MIT license.

Charli3 uses a combination of OSI-approved open-source licenses, primarily AGPL-3.0 and MIT, depending on the role of each repository within the ecosystem. Repositories that implement core or protocol-critical logic are licensed under AGPL-3.0 to ensure that improvements and modifications remain transparent and benefit the entire ecosystem, including node operators, developers, and token holders, while maintaining full OSI compliance. This may include both on-chain and select off-chain components where protocol logic and token usage are integral.

Repositories focused on tooling, SDKs, and supporting components are typically licensed under the MIT License to promote broad adoption, flexibility, and ease of integration.

AGPL-3.0 is applied where reciprocal openness is important to protect shared protocol infrastructure, while MIT is used where permissiveness and developer flexibility are the primary goals.

Please refer to each repository’s LICENSE file for the specific terms that apply.

Charli3 maintains and supports only official deployments that use the $C3 token and unmodified protocol economics.