Ergo-inspired oracle pool protocol for Cardano. On-chain data aggregation with transparent individual oracle submissions, consumed by dApps via CIP-31 reference inputs at zero cost.

Status: Specification — contracts not yet implemented.

A fully on-chain oracle pool where:

• Multiple oracle operators independently post data points as individual UTxOs
• A smart contract aggregates them (average with outlier filtering)
• Any dApp reads the finalized value via reference inputs (free, no contention)
• Every individual submission is visible on-chain (full transparency)
• Oracle operators earn reward tokens for timely, accurate data

This differs from existing Cardano oracles (Orcfax, Charli3) which aggregate off-chain and only post the final value. Here, aggregation is deterministic, verifiable, and enforced by validators.

5 validators governing 5 UTxO types:

See docs/SPECIFICATION.md for the full design.

aiken build

aiken check

oracle_pool/
├── docs/
│   └── SPECIFICATION.md    # Full protocol specification
├── validators/             # Aiken validator contracts (Phase 1)
├── lib/                    # Shared types and helpers
├── aiken.toml              # Project config (Plutus V3, stdlib v3.0.0)
└── README.md

1. Core Contracts — Pool, Oracle, Refresh validators + bootstrap mint
2. Off-Chain Tooling — Oracle operator CLI, monitoring
3. Governance — Ballot and Update validators
4. Testnet Deployment — Preview testnet with ADAvault SPO operators
5. Hardening — Security audit, edge cases, execution budget optimization

Adapted from Ergo Oracle Pools v2 (EIP-0023) for Cardano's eUTXO model using CIP-31 reference inputs, CIP-32 inline datums, and CIP-33 reference scripts.

Apache-2.0