> ## Documentation Index
> Fetch the complete documentation index at: https://docs.allium.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Outcome Metadata

> Hyperliquid HIP-4 outcome metadata snapshots.

The `hyperliquid.raw.outcome_metadata` table contains snapshots of Hyperliquid HIP-4 outcomes — the tradable units in HIP-4 prediction markets. Each row is a snapshot of one outcome at a given timestamp.

<Info>
  An outcome may be standalone (Recurring price-binary markets, where the description encodes class / underlying / expiry / target price / period) or grouped under a question via `question_metadata.named_outcomes`. Each outcome has exactly two binary token sides; trades happen on the individual side-tokens published by the HL API.
</Info>

## Table Columns

| Column Name   | Description                                                                                                                                                      |                 |                      |                   |               |
| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | -------------------- | ----------------- | ------------- |
| timestamp     | UTC timestamp of the snapshot.                                                                                                                                   |                 |                      |                   |               |
| outcome       | The outcome ID (numeric). Each outcome is a binary tradable unit on HIP-4.                                                                                       |                 |                      |                   |               |
| name          | Outcome name. `'Recurring'` for standalone price-binary outcomes; a specific name (e.g. 'Akami', 'Hypurr') when grouped under a question.                        |                 |                      |                   |               |
| description   | Outcome description. For Recurring outcomes, a pipe-separated key:value string, e.g. \`class:priceBinary                                                         | underlying:HYPE | expiry:20260428-1430 | targetPrice:37.86 | period:15m\`. |
| side\_specs   | 2-element VARIANT array describing each token side in order, e.g. `[{"name":"Yes"},{"name":"No"}]`. The element at index `token_side` defines that side's label. |                 |                      |                   |               |
| \_created\_at | Row creation timestamp.                                                                                                                                          |                 |                      |                   |               |
| \_updated\_at | Row last update timestamp.                                                                                                                                       |                 |                      |                   |               |

## Sample Query

```sql theme={null}
SELECT
  timestamp,
  outcome,
  name,
  description,
  side_specs
FROM hyperliquid.raw.outcome_metadata
WHERE TO_DATE(timestamp) >= CURRENT_DATE - 7
ORDER BY timestamp DESC, outcome
LIMIT 100
```