tx3 Dashboard

A monitoring dashboard for Tx3-described dApps. Builders and operators run it alongside tx3-lift's tracker to see their protocol's matched on-chain transactions in real time, with parties and transaction names lifted from the TII. The dashboard is a pure TypeScript app (TanStack Start + Nitro SSR) that observes the SQLite file the tracker writes — no custom backend, no API tier in the middle.

System context

C4Context
title System Context — tx3 Dashboard

Person(operator, "Builder / Operator", "Runs the dashboard for their own dApp")
System(dashboard, "tx3 Dashboard", "Tracker (sidecar) + SSR app that monitor a Tx3-described dApp")
System_Ext(utxorpc, "utxorpc Provider", "Cardano chain stream (v1beta WatchTx)")
System_Ext(registry, "Tx3 Registry", "Source of TII files (queried at vendor time, not runtime)")

Rel(operator, dashboard, "Views matched transactions", "HTTPS")
Rel(dashboard, utxorpc, "Subscribes to tx stream", "gRPC / TLS")
Rel(operator, registry, "Pulls TII once at vendor time", "GraphQL")

Loading

Run with Docker

The fastest way to get the full stack running. You need Docker (with Compose v2) and a Demeter utxorpc API key (free sign-up at demeter.run).

cp .env.example .env
# Open .env and set DMTR_API_KEY=dmtr_...
docker compose up

Open http://localhost:3000. The tracker streams Cardano mainnet and writes tracker.db into a Docker volume; the dashboard reads from it. Mainnet matches for the configured protocols typically appear within a few minutes.

Quick start (from source)

You need a clone of tx3-lang/tx3-lift as a sibling directory, Rust stable, Node 24, and a Demeter utxorpc API key.

# Once: clone tx3-lift sibling
git clone https://github.com/tx3-lang/tx3-lift ../tx3-lift

# Terminal A — tracker (sidecar that writes tracker.db)
cd ../tx3-lift
DMTR_API_KEY=dmtr_... cargo run -p tracker -- ../dashboard/tracker.toml

# Terminal B — dashboard (TanStack Start SSR app)
cd dashboard/frontend
pnpm install
pnpm dev

Open http://localhost:3000. See docs/running.md for prerequisites, env vars, and troubleshooting.

What the demo shows

The Docker Compose stack (deploy/tracker.toml) tracks five DeFi protocols on Cardano mainnet: Indigo, VyFi, Bodega Market, Fluid Aquarium, and Strike Staking. Matching uses mode = "best", which keeps only the highest-ranked candidate when a single transaction matches multiple TIIs. The matches list at / shows every matched transaction the tracker has seen, newest first; clicking through to /txs/<hash> shows the lifted parties and their addresses for that transaction.

The protocols/buidler-fest/ directory contains the earlier preview demo TII for reference, but the active configuration targets mainnet.

Documentation

• docs/architecture.md — two-process topology, data flow per page load, why the shape, Postgres outlook.
• docs/access-patterns.md — AP-1 (list) and AP-2 (detail), with type signatures and SQL.
• docs/running.md — prerequisites, env vars, first run, troubleshooting, deployment notes.

Project structure

dashboard/
├── README.md                     # this file
├── docker-compose.yml            # tracker + dashboard via Docker
├── .env.example                  # DMTR_API_KEY and optional PORT/RUST_LOG
├── tracker.toml                  # bare-metal tracker config (api_key commented out)
├── deploy/
│   └── tracker.toml              # Docker tracker config (mainnet, absolute paths)
├── docs/
│   ├── architecture.md
│   ├── access-patterns.md
│   └── running.md
├── protocols/
│   ├── indigo.tii
│   ├── vyfi.tii
│   ├── bodega_market.tii
│   ├── fluid-aquarium.tii
│   ├── strike-staking.tii
│   └── buidler-fest/
│       └── ticketing-2026.tii    # earlier preview demo (reference only)
└── frontend/                     # TanStack Start SSR app
    ├── package.json
    └── src/
        ├── lib/                  # db.ts, queries.ts, lifted.ts
        ├── components/           # PartyChip, TxNamePill, Header, ...
        └── routes/               # / (matches list), /txs/$hash (detail)