Step 1. Get Supported Protocols and Networks
Check out a wide range of supported protocols and networks for seamless integration.
First, we need to get a list of supported protocols and networks that we'll be using to send and receive events. This can be done by using the Overview endpoint as shown below.
Request Payload
curl -X GET \
"https://svc.blockdaemon.com/streaming/v2/" \
-H "Accept: application/json" \
Response Payload
The response is a JSON array containing objects that display a protocol overview.
[
{
"match_variable_supported": true,
"match_variable_types": [
{
"data_source": [
"confirmed_tx",
"confirmed_balance"
],
"variable_type": "address"
},
{
"data_source": [
"block",
"reorg"
],
"variable_type": "event_type"
}
],
"network": "mainnet",
"protocol": "bitcoin"
},
{
"match_variable_supported": true,
"match_variable_types": [
{
"data_source": [
"confirmed_tx",
"confirmed_balance"
],
"variable_type": "address"
},
{
"data_source": [
"block",
"reorg"
],
"variable_type": "event_type"
}
],
"network": "testnet",
"protocol": "bitcoin"
},
{
"match_variable_supported": true,
"match_variable_types": [
{
"data_source": [
"confirmed_tx_log",
"staking_status",
"staking_reward",
"confirmed_tx_trace",
"confirmed_tx",
"confirmed_balance"
],
"variable_type": "address"
},
{
"data_source": [
"block",
"reorg"
],
"variable_type": "event_type"
}
],
"network": "mainnet",
"protocol": "ethereum"
},
{
"match_variable_supported": true,
"match_variable_types": [
{
"data_source": [
"confirmed_tx",
"confirmed_balance",
"confirmed_tx_log",
"staking_status",
"staking_reward",
"confirmed_tx_trace"
],
"variable_type": "address"
},
{
"data_source": [
"block",
"reorg"
],
"variable_type": "event_type"
}
],
"network": "holesky",
"protocol": "ethereum"
},
{
"match_variable_supported": true,
"match_variable_types": [
{
"data_source": [
"confirmed_tx",
"confirmed_balance"
],
"variable_type": "address"
},
{
"data_source": [
"block",
"reorg"
],
"variable_type": "event_type"
}
],
"network": "mainnet",
"protocol": "polkadot"
},
{
"match_variable_supported": true,
"match_variable_types": [
{
"data_source": [
"confirmed_balance",
"confirmed_tx"
],
"variable_type": "address"
},
{
"data_source": [
"block",
"reorg"
],
"variable_type": "event_type"
}
],
"network": "westend",
"protocol": "polkadot"
},
{
"match_variable_supported": true,
"match_variable_types": [
{
"data_source": [
"confirmed_tx",
"confirmed_balance",
"confirmed_tx_log"
],
"variable_type": "address"
},
{
"data_source": [
"block",
"reorg"
],
"variable_type": "event_type"
}
],
"network": "mainnet",
"protocol": "polygon"
},
{
"match_variable_supported": true,
"match_variable_types": [
{
"data_source": [
"confirmed_tx",
"confirmed_balance",
"confirmed_tx_log"
],
"variable_type": "address"
},
{
"data_source": [
"block",
"reorg"
],
"variable_type": "event_type"
}
],
"network": "amoy",
"protocol": "polygon"
}
]
Each object represents a protocol overview with the following fields:
| Fields | Details |
|---|---|
match_variable_types | An array of supported match variable types for the protocol. |
source | The data that will be received for each variable_type.For example: - event_type will produce block event.- address will produce confirmed_tx and confirmed_balance events. |
variable_type | The supported variable types. In this case, we have options such as address and event_type. This implies that we can create variables later on and use them to match against address or event_type. |
network | Associated network (e.g., mainnet). |
protocol | Protocol name (e.g., polkadot, dogecoin, ethereum). |
👋 Need Help?
Contact us through email or our support page for any issues, bugs, or assistance you may need.
Updated about 2 months ago