Cardano Catalyst Fund 14

OData for
Cardano

OData V4 service exposing the Cardano blockchain. Packaged as a SAP CAP plugin - install with npm, configure via cds.requires, Cardano services register automatically.

# Install the CAP plugin
npm install @odatano/core

# package.json (cds.requires)
"odatano-core": {
  "network": "preview",
  "backends": ["blockfrost"],
  "blockfrostApiKey": "preview_api_key",
  "txBuilders": ["buildooor"]
}

# POST - build a simple ADA transaction
POST .../cardano-transaction/BuildSimpleAdaTransaction
{ "senderAddress": "addr1...",
  "recipientAddress": "addr1...",
  "lovelaceAmount": 5000000 }
  • 1285 Tests
  • 97% Statement Coverage
  • Apache 2.0 License
  • v1.7.8 NPM Package

Architecture

ODATANO is a bridge between business applications and the Cardano blockchain. Tools enterprises already use like SAP Fiori, Excel, Power BI, or any OData-aware client can read on-chain data and trigger transactions without learning complex blockchain APIs. ODATANO takes care of the hard parts like talking to multiple blockchain data providers, caching of the data, and safely building and submitting transactions on your behalf. Cardano as an OData service - it's that simple.

Your Application

SAP Fiori / UI5 Any OData Client REST / curl

ODATANO

CardanoODataService CardanoTransactionService CardanoSignService

Cardano Blockchain

Mainnet Preview Preprod

CDS services

Cardano core usage is exposed as OData V4 entities and actions. Standard query options ($filter, $select, $expand, $orderby) work as in any OData service after fetching the Blockchain data once. OData Actions for all kinds of Transaction operations with full Plutus V3 support. Full service metadata available at $metadata.

Read

CardanoODataService: 18 entities, 16 actions. Blocks, Transactions, Addresses, UTxOs, Pools, Accounts, DReps, Protocol Parameters, transaction CBOR parser. Lazy on-demand indexing with TTL refresh.

Transactions

CardanoTransactionService: 13 actions. ADA transfers, multi-asset, mint, Plutus V3 spend, CIP-20 metadata, CIP-31 reference inputs, CIP-33 reference scripts. Two builder engines: CSL and Buildooor.

Signing

CardanoSignService: 8 actions. External signing via CIP-30 wallets or Cardano CLI; server-side signing via PKCS#11 HSM. Private keys never reach the server in any flow.

Stack

Runtime, dependencies, and test coverage.

Framework SAP CAP 9.x
Language TypeScript 5.x
Runtime Node.js 20 / 22
Database SQLite · SAP HANA
Blockchain APIs Blockfrost · Koios · Ogmios
TX Builders CSL · Buildooor
Testing 31 automated test suites, 1285 tests
License Apache 2.0

Example Applications

Reference implementations built on top of @odatano/core - from full SAP Fiori + CAP apps with custom Plutus V3 validators to on-chain metadata anchoring and HTTP 402 payment gating.

Pharmaceutical Supply Chain

TRACE

SAP Fiori + CAP application built on top of @odatano/core. Tracks pharmaceutical batches across manufacturer, distributor, and pharmacy using NFTs minted under a Plutus V3 policy. Each handoff is a Plutus spend with a continuing-output datum update, anchoring certificates and cold-chain telemetry on-chain.

  • Batch NFT Mint Policy (Plutus V3)
  • Continuing-Output Datum Custody Chain
  • CIP-20 Document Anchoring
  • CIP-30 Browser Wallet Signing
Grand Prize · Charli3 Hackathon 2026

QUANTIX

SAP Fiori + CAP application built on top of @odatano/core. On-chain settlement of B2B raw-material orders against attested inventory and price feeds from a forked Charli3 multi-feed oracle stack. A custom Plutus V3 minting policy enforces inventory availability, price ceiling, payment, and deadline atomically. One CIP-30 wallet signature, one transaction, no escrow.

  • Atomic Mint Validator (Plutus V3)
  • Charli3 Multi-Feed Oracle Integration
  • Per-Supplier Reference Scripts on Cardano Preprod
  • Best Overall Project · Charli3 Oracle Hackathon 2026
Financial Data Anchoring

FINCA

SAP Fiori + CAP application built on top of @odatano/core. Anchors accounting data and financial reports - Balance Sheets and Income Statements - on Cardano as CIP-10 label-1447 metadata, following the Cardano Foundation Reeve specification. Verifiable accounting without a smart contract: one CIP-30 signature per anchor.

  • CIP-10 Label-1447 Metadata (Reeve Spec)
  • Double-Entry Journal · Decimal(23,2) Ledger Math
  • On-Chain Verification of Reports & Transactions
  • Excel / OData Spreadsheet Integration
HTTP 402 Payment Gating

x402

Payment-gating library for SAP CAP built on top of @odatano/core. Implements the Cardano-x402-v2 spec - gated OData endpoints return HTTP 402 until the caller proves on-chain settlement. Asset-agnostic, no database, no smart contract: replay defense is the Cardano UTxO model itself. Ships with a working example CAP app.

  • Cardano-x402-v2 Protocol (HTTP 402)
  • Nonce-UTxO Replay Defense - No Database
  • CAP Service Gating + Express Middleware
  • ADA or Any Native Token Pricing