QUANTIX

Delivery commitments that enforce themselves on-chain.

QUANTIX is a SAP Fiori + CAP application built on top of @odatano/core. It demonstrates a B2B raw-materials buying flow where the order contract itself enforces the match between requested quantity, attested inventory, attested price, and supplier payment atomically, in a single transaction signed once by the buyer’s CIP-30 wallet.

QUANTIX won the Grand Prize (Best Overall) at the Charli3 Hackathon 2026 as a solo entry.

Thesis

In real-world B2B supply chains, the two numbers a buyer most needs to trust - what is actually in stock and what it costs right now - are often stored in different systems that drift apart over the course of a workday. QUANTIX does not tokenize the goods themselves; it tokenizes the facts about them (inventory, price, timestamp, signer set) so that purchase commitments can be enforced against attested oracle data instead of stale ERP screenshots or PDF quotes.

How it works

A buyer picks a supplier and a quantity of a raw material (e.g. lithium carbonate, in grams) and clicks Buy. The CAP service builds a single atomic Cardano transaction that, in one step, signed once by the buyer’s CIP-30 wallet, mints a per-order receipt NFT under a Plutus V3 minting policy parameterised for that supplier.

The mint is valid only if the same transaction:

  • References the supplier’s inventory and price AggState UTxOs as reference inputs
  • Both feeds are still inside their validity window
  • Inventory feed value ≥ requested quantity
  • Price feed value ≤ buyer’s max_price_lovelace
  • Transaction upper bound ≤ buyer’s deadline_ms
  • One output pays the supplier at least requested × price lovelace

Either the whole transaction settles atomically or nothing happens. The receipt NFT is the on-chain proof-of-purchase.

Architecture

Three parallel tracks:

  • Oracle track: 3 Charli3 oracle deployments on preprod (one per supplier), each with two distinct AggState UTxOs (C3AS_inventory, C3AS_price). Built on a fork of the upstream Charli3 stack (Aiken validator, Python node, off-chain SDK) extended for multi-feed deployments.
  • App track: SAP CAP service exposing Suppliers, Orders, and OData actions, using @odatano/core as the CDS plugin for all Cardano I/O. Fiori UI shows live inventory and price, a Refresh-Feed button that triggers an ODV round end-to-end in ~3 seconds, and a Buy button that round-trips through the user’s CIP-30 wallet.
  • Contract track: Custom order_mint.ak Plutus V3 minting policy, parameterised per supplier with (inventory_policy, inventory_asset, price_policy, price_asset, supplier_payment_hash), reading both AggStates as reference inputs.

Charli3 extension story

The upstream Charli3 stack was designed for single-feed financial oracles. Multi-feed supply-chain data required four connected changes, all implemented as public forks and candidates for upstream PRs:

RepoBranchPurpose
charli3-pull-oracle-contractsc3-supply/asset-prefixPrefix-match AggState beacon (54+2 tests green)
charli3-pull-oracle-nodec3-supply/multi-feedMulti-feed runtime + per-feed ODV services
charli3-pull-oracle-sdkc3-supply/multi-aggstateaggstate_asset_name plumbing in tx builder

Tech stack

  • Framework: SAP CAP (Node.js, CDS), Fiori/UI5 frontend
  • Cardano I/O: @odatano/core CDS plugin
  • Oracle: Charli3 pull-oracle stack (forked for multi-feed)
  • Contract: Custom Plutus V3 validator in Aiken (12 unit tests)
  • Wallet: CIP-30 (Eternl, Lace)
  • Network: Cardano preprod

Live deployments on preprod

Three oracle deployments, six live feeds (inventory + price per supplier), three per-supplier order-mint policies deployed as reference scripts.

Demo