Data Dictionary

Oura follows a Cardano chain and outputs events. Each event contains data about itself and about the context in which it occurred.

A consumer aggregating a sequence of multiple events will notice redundant / duplicated data. For example, the “block number” value will appear repeated in the context of every event of the same block. This behavior is intended, making each event a self-contained record is an architectural decision. We favor “consumption ergonomics” over “data normalization”.

Pipeline Data Model

This page is the static schema reference — the exact shape of an event. For the moving picture (how events flow and how rollbacks are surfaced), see How it works.

Internally, every unit that flows through an Oura v2 pipeline is a ChainEvent that wraps a chain point and (except for resets) a Record. When a sink serializes an event to JSON, it uses the following envelope:

{
  "event": "apply",
  "point": { "slot": 0, "hash": "" },
  "record": { }
}

• event: the kind of chain event — one of:
  • apply: a block/tx was applied to the chain.
  • undo: a block/tx was rolled back.
  • reset: the pipeline reset to the given point (carries no record).
• point: the chain position, with slot (number) and hash (hex string). The chain origin is represented as a null/empty point.
• record: the payload. Its shape depends on which filters ran before the sink (see below).

The record is one of the following variants, determined by the source and the filters in the pipeline:

Record	Produced by	Shape
CBOR block	sources, by default	{ "hex": "<cbor-hex>" } — the raw block CBOR.
CBOR tx	Split Block	{ "hex": "<cbor-hex>" } — the raw transaction CBOR.
Parsed block	ParseCbor	a UTxORPC Block.
Parsed tx	ParseCbor	a UTxORPC Tx.
Generic JSON	Into JSON	an arbitrary JSON value.
Legacy v1	LegacyV1	a v1-style event (see Legacy V1 events).

Available Events (ParseCbor Filter)

When the ParseCbor filter is enabled, records use the UTxORPC data structures: a CborBlock becomes a parsed Block and a CborTx becomes a parsed Tx. Refer to the UTxORPC Cardano spec for the complete field-level schema of those structures.

Available Events (Legacy V1 Filter)

When the LegacyV1 filter is enabled, records take the shape of the original Oura v1 events. That catalog is long, so it lives on its own page: Legacy V1 events.