Overview

Event streaming flips the interaction model by delivering blockchain events directly to customers. Currently, the delivery is limited to webhooks. Customers will have to register a webhook in order to receive blockchain events.

Blockchain events are delivered in near real-time as they happen on the chain. This enables an event-driven architecture where customers receive only the data they're interested in and only when relevant. Customers can control which events will be sent by event streaming. It works on a conditional basis that is reflected in the form of rules and variables.

❗️

Note

Each call incurs a fixed CU charge, plus additional CUs for API operations. See the Compute Units Usage page for details.

Supported Protocols

Event Types

Event Streaming has two conditions to receive events:

Config API

The Config API is the main entry point for initiating your journey with event streaming. The main URL for accessing the Config API is:

https://svc.blockdaemon.com/streaming/v2

Allow-listed IPs

To enhance security and prevent DDoS attacks, allow-list the following IP addresses that will hit your Events Webhook endpoints:

• 35.245.225.131
• 34.150.141.91
• 34.85.141.205

Example Setup

In this section, we go over the setup of a new rule to receive:

• Notifications for new blocks.
• Notifications for transactions and balances for an account.

Follow the steps below:

• Step 1. Get Supported Protocols and Networks
• Step 2. Create a New Target
• Step 3. Create a Variable
• Step 4. Add Variable Values
• Step 5. Create a Rule