GetBlock rolls out Webhooks beta, welcomes testers: Highlights
On September 1, 2022, the GetBlock Webhooks beta testing campaign begins. Starting with a BNB chain such as Binance Smart Chain or BSC, new features will be implemented for the rest of the mainstream blockchains.
GetBlock Tracker opened up a new avenue for the Web3 space with this release. Webhooks are predetermined notifications sent from one party to another when conditions are met. They’re a subclass of automated notifications. The Webhook system is used in blockchain development to transmit automated messages regarding on-chain events. This can be events like blocks being mined or transactions being confirmed. GetBlock Tracker tracks over 40 block and transaction parameters in a seamless manner. Developers can use automated push notifications from Web3 to create a reliable notification system for their apps. GetBlock Tracker can supplement dApps, trading bots, analysis tools and no-code projects.
GetBlock welcomes Web3 experts to try out the beta version of Webhooks. They can experiment with the new features and provide feedback to the company. GetBlock’s Webhooks make data flow far more easily in blockchain applications with numerous features. They also greatly reduce the resources these applications use.
What are Webhooks, and why are they different from nodes APIs?
Webhooks are notifications that are automatically sent between actors. These notifications transfer information only after meeting certain criteria set by the user. Rather than making a series of manual requests, actors can simply set triggers to receive Webhooks when specific events occur. Webhooks and node APIs follow certain models for how askers and answerers relate to each other. In addition, the Webhook model is much more convenient and resource-efficient compared to the node APIs model. Webhooks are requests sent over HTTP that is received by a receiver system. These requests are triggered by an event in the source system, which is also known as the sender. Webhooks usually come with payload data, and they are sent out automatically when triggered.
All Webhook systems follow the same principle: Bob set the conditions that cause Alice to send him a message. Once these conditions are met — or user-defined conditions are met — Alice will send Bob a message without any further instructions or triggers.
Who needs Web3 Webhooks?
Using blockchains as a payment system or value transfer hub can lead to a variety of applications. These applications can use Web3 Webhooks, “crypto alerts” or on-chain notifications.
Webhooks are commonly used in blockchain for ten classes of services considered real-world applications:
- Cryptocurrency wallets
- Analytical systems based on on-chain data
- Decentralized finance protocols
- Trading bots
- Portfolio trackers and managers
- Accounting and taxation protocols related to cryptography
- AML/CFT Services
- Centralized crypto exchanges
- Hardware wallets
- Blockchain infrastructure providers
Webhooks can optimize the financial and technical design of every crypto-centric service that uses classic API instruments right now. It’s blockchain-agnostic, meaning it can work with both programmable and non-programmable blockchains. The modern blockchain space demands faster processing and higher costs. Webhooks can naturally replace APIs in the vast many cases.