---
updatedAt: 2026-04-01T12:35:22.000Z
---

Fetch the complete documentation index at: https://docs.blockdaemon.com/llms.txt. Use this file to discover all available pages before exploring further. Append .md to any documentation page URL to get its markdown version.

# Events Unified Format

Explore the standardized unified format for events across various protocols and networks.

Events are sent using the `UNIFIED_V1`format to all supported protocols and networks. This section will provide an overview of each supported event type that uses the format.

> ❗️ Important Note
>
> The `UNIFIED_V1` format is currently still in development. Some fields might still be subject to change.

> 📘 Info
>
> To get a list of supported protocols, networks, and their supported events, please refer to this [page](https://docs.blockdaemon.com/reference/get-protocol-overview).

> **Solana event coverage (beta)**\
> Solana support is currently in beta. Event type coverage and variable availability may expand over time. Refer to the changelog for the latest updates.

## Standardized Envelope

All events produced by Event Streaming will follow a standardized envelope in the `UNIFIED_V1` format. Below is an example of the structure:

```json
{
  "protocol":"bitcoin",
  "network":"mainnet",
  "event_type":"<event_type>",
  "chain_id":"<namespace>:<network-identifier>",
  "data": {}
}
```

The table below shows the schema breakdown:

<Table align={["left","left","left"]}>
  <thead>
    <tr>
      <th>
        Field
      </th>

      <th>
        Type
      </th>

      <th>
        Description
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        `protocol`
      </td>

      <td>
        string
      </td>

      <td>
        The blockchain protocol.
      </td>
    </tr>

    <tr>
      <td>
        `network`
      </td>

      <td>
        string
      </td>

      <td>
        The blockchain network.
      </td>
    </tr>

    <tr>
      <td>
        `event_type`
      </td>

      <td>
        string
      </td>

      <td>
        The name/type of the event.

        Based on the Event Type:

        * [unified_block](https://docs.blockdaemon.com/docs/unified-block)
        * [unified_reorg](https://docs.blockdaemon.com/docs/unified-reorg)

        Based on Address:

        * [unified_confirmed_tx_log](https://docs.blockdaemon.com/docs/unified-confirmed-transaction-log)
        * [unified_confirmed_balance](https://docs.blockdaemon.com/docs/unified-confirmed-balance)
        * [unified_confirmed_tx](https://docs.blockdaemon.com/docs/unified-confirmed-transaction)
        * [unified_confirmed_tx_trace](https://docs.blockdaemon.com/docs/unified-confirmed-transaction-trace)
        * [unified_staking_reward](https://docs.blockdaemon.com/docs/unified-staking-reward)
        * [unified_staking_status](https://docs.blockdaemon.com/docs/unified-staking-status)
      </td>
    </tr>

    <tr>
      <td>
        `chain_id`
      </td>

      <td>
        string
      </td>

      <td>
        The blockchain network where the event occurred. It combines a namespace with a network-specific identifier to uniquely reference the network.

        For example:

        * `eip155:1` for Ethereum
        * `bip122:<blockhash>` for Bitcoin.
      </td>
    </tr>

    <tr>
      <td>
        `data`
      </td>

      <td>
        object
      </td>

      <td>
        The event payload is determined by which `event_type` is shown.
      </td>
    </tr>

    <tr>
      <td>
        `raw`
      </td>

      <td>
        object
      </td>

      <td>
        Raw payload (not included by default)
      </td>
    </tr>
  </tbody>
</Table>

## Other Templates

By default, rules use the `UNIFIED_V1` template, a predefined option that applies the unified format. However, there are two other predefined templates you can use:

1. **UNIFIED\_V1\_RAW**: This template is the same as `UNIFIED_V1` but additionally adds a `raw` key to the envelope.
2. **ALL\_DATA**: This template does not apply any formatting or modifications and will return messages in their original form.

**How to use it?**

To use either of these templates, specify the predefined template in the `template` parameter when [creating or updating](https://docs.blockdaemon.com/docs/step-5-create-a-rule) rules.

## 👋 Need Help?

Contact us through [email](mailto:support@blockdaemon.com) or our [support page](https://www.blockdaemon.com/support) for any issues, bugs, or assistance you may need.