Cardano - Delfines

[lolaaimar]

Pyth Examples Contribution

Team name: Delfines
Submission name: Oracle-settled Invoices
Team members: Agustin Osiecki (@a-osiecki), Sofia Bobbiesi (@sofia-bobbiesi), Lola Aimar (@lolaaimar)
Contact: agustinosiecki@gmail.com

Type of Contribution

• New Example Project (Adding a new example to demonstrate Pyth integration)
• Bug Fix (Fixing an issue in existing examples)
• Documentation Update (Improving README, comments, or guides)
• Enhancement (Improving existing functionality or adding features)
• Hackathon Submission (Submitting a project from a hackathon)

Project Information

Project/Example Name:

Pyth Product Used:

• Pyth Price Feeds
• Pyth Entropy
• Multiple Products
• Other: ___________

Blockchain/Platform:]

• Cardano
• Ethereum/EVM
• Solana
• Aptos
• Sui
• Fuel
• Starknet
• TON
• Other: ___________

Description

What does this contribution do?

Oracle-Settled Invoice is a Cardano escrow that locks one asset and settles a liability indexed to another using Pyth prices.

This project is a practical blueprint for building oracle-driven settlement flows on Cardano with Pyth. It combines Aiken on-chain validators with a typeScript off-chain client, so you can go from contract logic to real transaction execution with minimal setup.

How does it integrate with Pyth?

Uses Pyth price feeds to determine payouts in ADA at a given time.

What problem does it solve or demonstrate?

Directory Structure

lazer/cardano/OSI/
├── on-chain/            # Smart contract
├── off-chain/            # Off-chain implementation 
└── README.md       # Project documentation

Prerequisites

• Node.js version: 22.14.0
• Aiken version: aiken v1.1.21+42babe5

Setup Instructions

1. Build the validator compiled code:

cd lazer/cardano/OSI/on-chain
aiken build

2. Install off-chain dependencies

cd lazer/cardano/OSI/off-chain
bun install

For further instructions to set up and run the project, check out the project's README.

Checklist

Code Quality

• Code follows existing patterns in the repository
• Proper error handling implemented
• No hardcoded values (use environment variables where appropriate)

Testing

• Tested locally and works as expected
• All existing functionality still works (no breaking changes)

Additional Context

Screenshots/Demo (if applicable)

Thank you for contributing to Pyth Examples!