Skip to content

Query 02 - Treasury USDM Payees

Result

This table is the CSV result produced by Apache Jena over the state-audit graph. USDM quantities are decimal USDM.

treasuryLabel treasuryAddress payeeLabel payeeAddress paymentTxs paymentOutputs usdmPaid
amaru-treasury.network_compliance addr1xyezq8wpaqnssdjvd3p220uf7e6nzjae44w6yu625y965rfjyqwur6p8pqmycmzz55lcnan4x99mnt2a5fe54ggt4gxs8thzgk amaru.cag-payee addr1q8qrds2nnx7clx3kcpp2l0eu45twmdcahsfu9m0xcwy59j6xz3vs0hnfaz9nhje8z34kfnds4jyk7hs6dnrag6e2lfgqtyf4rl 2 2 418750.000000 
418,750.000000 USDM paid by network_compliance to the CAG payee bridge

What

This query lists USDM recipients paid by the amaru-treasury.network_compliance treasury. It is deliberately narrower than a raw "all USDM outputs" query: a row is included only when the transaction consumes a network_compliance treasury input and emits USDM to a configured payee bridge.

For May 2026, the graph returns one payee: amaru.cag-payee.

Why

A raw output-side query over every USDM output in the graph is too broad for the user question "who did the treasury pay USDM to?" because it mixes three different concepts:

  • network_compliance treasury change,
  • swap-side script outputs,
  • actual beneficiary/payee outputs.

The source proof is therefore part of the query. A counted payment transaction must consume a UTxO from network_compliance, and the counted output must go to the configured CAG payee bridge. USDM outputs that do not satisfy both conditions are not treasury payees.

Diagram

flowchart LR
  treasury[network_compliance treasury input]
  paymentTx[Payment transaction]
  cag[CAG payee bridge]
  table[Payee total]

  treasury --> paymentTx
  paymentTx --> cag
  cag --> table

How

The query pins the full on-chain USDM asset id in a VALUES block and resolves both the treasury address and CAG payee address through rules.yaml labels.

It scans USDM outputs to the configured payee bridge, then applies an EXISTS source proof:

Run

From the repository root, run this query through the tutorial setup script:

bash docs/may-2026-amaru-lattice/setup.sh \
  docs/may-2026-amaru-lattice/treasury-usdm-movement/02-usdm-output-addresses.rq

SPARQL

FILTER EXISTS {
  ?paymentTx cardano:hasInput ?input .
  ?input cardano:fromTxOutRef ?ref .
  ?ref cardano:hasTxId/cardano:bytesHex ?sourceTxId ;
       cardano:hasIndex ?sourceIx .
  ?sourceTx cardano:hasTxId/cardano:bytesHex ?sourceTxId ;
            cardano:hasOutput ?sourceOut .
  ?sourceOut cardano:hasIndex ?sourceIx ;
             cardano:atAddress/cardano:bech32 ?treasuryAddress .
}

That is the key distinction: the output is counted only if the same transaction spends a resolved UTxO from the network_compliance treasury.

The inner subquery groups by paid ledger output before the outer payee aggregation. That prevents multiple treasury inputs in one transaction from multiplying the paid output amount.

PREFIX cardano: <https://lambdasistemi.github.io/cardano-knowledge-maps/vocab/cardano#>
PREFIX rdf:     <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX rdfs:    <http://www.w3.org/2000/01/rdf-schema#>
PREFIX xsd:     <http://www.w3.org/2001/XMLSchema#>

# USDM recipients paid by the network_compliance treasury.
#
# This query intentionally does NOT list every output that carries USDM.
# A broad output-side query mixes together treasury change, swap-side script
# outputs, and actual beneficiary payments. For the user-facing question
# "who did the treasury pay USDM to?", the destination must satisfy both:
#
# - the transaction consumes at least one network_compliance treasury input;
# - the USDM output goes to a configured payee bridge.
#
# In the May 2026 graph, that leaves exactly the CAG payee bridge.
SELECT ?treasuryLabel ?treasuryAddress
       ?payeeLabel ?payeeAddress
       (COUNT(DISTINCT ?paymentTxId) AS ?paymentTxs)
       (COUNT(DISTINCT ?paymentOutputRef) AS ?paymentOutputs)
       ((xsd:decimal(SUM(?paymentUsdm)) / 1000000) AS ?usdmPaid)
WHERE {
  BIND("amaru-treasury.network_compliance" AS ?treasuryLabel)

  # Pin the full on-chain USDM asset id. Token ticker text is not sufficient
  # evidence because multiple assets can share the same display name.
  VALUES ?usdmAssetId {
    "c48cbb3d5e57ed56e276bc45f99ab39abe94e6cd7ac39fb402da47ad0014df105553444d"
  }

  # Resolve the treasury and payee addresses from rules.yaml labels. This
  # keeps the query tied to named graph entities rather than pasted addresses.
  ?treasury rdfs:label "amaru-treasury.network_compliance" ;
            cardano:bech32 ?treasuryAddress .
  ?payee rdfs:label ?payeeLabel ;
         cardano:bech32 ?payeeAddress .

  # The only configured USDM beneficiary bridge in this report is CAG. Vendor
  # entities may declare they are paid through this bridge, but this query
  # proves only the ledger output to the bridge address.
  VALUES ?payeeLabel { "amaru.cag-payee" }

  {
    # One row per paid output before the outer aggregation. The EXISTS clause
    # proves source: the same transaction must consume a UTxO whose resolved
    # producer output was at the network_compliance treasury address.
    SELECT ?treasuryAddress ?payeeLabel ?payeeAddress
           ?paymentTxId ?paymentOutputRef (SUM(?qty) AS ?paymentUsdm)
    WHERE {
      VALUES ?usdmAssetId {
        "c48cbb3d5e57ed56e276bc45f99ab39abe94e6cd7ac39fb402da47ad0014df105553444d"
      }

      ?paymentTx cardano:hasTxId/cardano:bytesHex ?paymentTxId ;
                 cardano:hasOutput ?out .
      ?out cardano:hasIndex ?outputIndex ;
           cardano:atAddress/cardano:bech32 ?payeeAddress ;
           cardano:hasAssetValue/rdf:rest*/rdf:first ?asset .
      ?asset cardano:hasIdentifier/cardano:bytesHex ?usdmAssetId ;
             cardano:quantity ?qty .

      FILTER EXISTS {
        ?paymentTx cardano:hasInput ?input .
        ?input cardano:fromTxOutRef ?ref .
        ?ref cardano:hasTxId/cardano:bytesHex ?sourceTxId ;
             cardano:hasIndex ?sourceIx .
        ?sourceTx cardano:hasTxId/cardano:bytesHex ?sourceTxId ;
                  cardano:hasOutput ?sourceOut .
        ?sourceOut cardano:hasIndex ?sourceIx ;
                   cardano:atAddress/cardano:bech32 ?treasuryAddress .
      }

      BIND(CONCAT(?paymentTxId, "#", STR(?outputIndex)) AS ?paymentOutputRef)
    }
    GROUP BY ?treasuryAddress ?payeeLabel ?payeeAddress ?paymentTxId ?paymentOutputRef
  }
}
GROUP BY ?treasuryLabel ?treasuryAddress ?payeeLabel ?payeeAddress
ORDER BY ?payeeLabel