80
to the host and set your Tezos Node RPC to http://172.17.0.1:8732
.Pusher.Web
project inENV
variable Tezos:NodeUrl
has to be set. Configured Tezos RPC endpoint must support following calls monitor/heads/main
/chains/main/blocks/{hash}
Pusher.Web
project inappsettings.json
file. You will need to fill in this value "NodeUrl": ""
.
Configured Tezos RPC endpoint must support following calls monitor/heads/main
/chains/main/blocks/{hash}
ConsoleApp
project in the appsettings.json
file if you are running from compiled sources or ENV
variables if you are running from Docker. Tezos:NodeUrl
- Tezos RPC endpoint URLAzure:AzureFunctionUrl
- URL of your deployed function appAzure:AzureFunctionKey
- Access key for your message function of your deployed function appFunction
project in the local.settings.json
file if you are running it locally or Azure Applications Settings if you are running in Azure. There is a pre-filled endpoint which is hosted on Azure Free plan, so it might be already above daily threshold. You can create a SignalR Service on Azure for free on Azure and provide your own SignalR connection string."AzureSignalRConnectionString": ""
signalr.service.ts
)transactionAddresses
, delegationAddresses
and originationAdresses
are string[]
.signalr.service.ts
.x-tezos-live-userid
to identify a client during the initial call to negotiate
endpoint. In the sample client application we are using the npm uuid package to generate random UUIDs.signalr.service.ts
here by making a POST
request to subscribe
endpoint with the following parametersstring
- this is the UUID you have used for the negotiate
calltransactionAddresses
, delegationAddresses
and originationAddresses
are string[]
- this is the array of the addresses that you want to subscribe to. You can subscribe to all addresses by sending ['all']
subscribe
call. You need to provide the generated UUID that you used in the negotiate
call along with the array of the addresses.