Event Coverage
Check which event types, protocols, and networks are supported together before building a rule.
Supported Events by Protocol
Search or browse below to see which event types are supported for each protocol and network.
Base
mainnet · sepolia
BNB Smart Chain
mainnet · testnet
Kaia
mainnet · kairos
Monad
mainnet · testnet
Optimism
mainnet
Ethereum
mainnet · hoodi (+ sepolia, no staking)
History depth & recovery windows
Event streaming is forward-only by design. What varies per chain is how much backfill is possible after an outage before data is permanently lost, bounded either by a chain-specific data layer or, by default, the platform-wide Kafka retention below. "Outage" here means an outage on the customer's side, for example a webhook target or WebSocket consumer being down, not an outage of Blockdaemon's own infrastructure.
Platform-wide limits (apply to all chains)
| Layer | Retention | Notes |
|---|---|---|
| Internal broadcast topic | 1 week | The default recovery ceiling for any chain without its own longer-lived backfill source. Outages longer than this lose data regardless of chain. |
| Queuing system (customer-facing) | 10,000 messages per target | Usually the tighter limit in practice; see example below. Beyond it, older messages are dropped and a system.dropped.messages event is sent. See Webhook Handling. |
ExampleFor a busy Solana target, the 1-week window is not a reliable safety net. A short consumer outage can queue up 10,000 messages in under an hour, so keeping the webhook consumer healthy and monitoring for
system.dropped.messagesmatters more than the 1-week figure suggests.
Per-chain recovery window
| Chain | Recovery window | Binding constraint |
|---|---|---|
| Solana | 1 week | BigTable slot storage retains 1 week of slots for gap detection. Backfill runs in parallel with live processing and does not block new data. |
| Stellar | 7 days | RPC getLedgers retention window. Beyond 7 days, recovery requires a self-hosted Galexie archive. |
| Ethereum, Base, BNB, Kaia, Monad, Polygon, Optimism, Tron, Polkadot/Assethub | 1 week (platform default) | No chain-specific backfill mechanism beyond the internal broadcast topic retention. |
| Bitcoin, Bitcoin Cash, Dogecoin, Litecoin | 1 week (platform default) | The underlying indexer holds full chain history, but the event-streaming delivery path itself is still bounded by the 1-week broadcast topic. |
NoteThese are the outer limits for backfilling from an upstream outage. The 10,000-message queuing cap above still applies independently and, for busy targets, is typically the one reached first; see the example above.
👋 Need Help?
Contact us through email or our support page for any issues, bugs, or assistance you may need.
Updated about 2 hours ago