Events

In a traditional API, customers request data from the blockchain using the API. This process involves continuous polling where customers request new blocks, transactions, and related information. The system retrieves data on demand, creating a continuous query process cycle.

Event streaming flips the interaction model by delivering blockchain events directly to customers. Events can be delivered two ways:

• Webhook — Blockdaemon pushes events to a URL you host. See Webhook Streaming.
• WebSocket — you open an outbound connection to Blockdaemon and receive events over it. No inbound firewall rule or public endpoint needed on your side. See WebSocket Streaming.

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.

📘

Info

This API is part of the Chain Watch bundles.

❗️

Important Note

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

Supported Protocols

See Event Coverage for which event types are supported on each protocol and network. The table below is a quick overview.

Event Types

Blockdaemon Event Streaming supports several event types. These are split into two main condition categories:

• Receive events when a blockchain event of a specific type occurs
• Receive events when a blockchain event is related to a specific address

Check out the full list of supported event types.

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