📚
Introduction
What makes BLAST special

Overview

Blast is Bware Labs' API provider platform that aims to solve Web 3 infrastructure issues related to reliability and latency, by employing geographically distributed third-party nodes.
Blast offers a multi-region architecture that, along with a series of clustering and geo-location mechanisms, ensures optimal routing of user requests to the closest point of presence relative to where a call is generated from. Moreover, using third party-nodes scattered all over the world Blast ensures the decentralization of the underlying blockchain infrastructures thus reducing down-time and increasing reliability.
The set of blockchain projects available within the Blast platform is carefully selected in order to support Web 3 development efforts on the most relevant networks in the industry. Platform users are able to easily generate an API endpoint (RPC/WSS/REST) in just a couple of easy steps, after registering with their Metamask account. Once registered, all users have access to a free subscription plan which allows for a number of requests on each of the Blast supported blockchains. If the free plan is not enough, users are able to upgrade to paid plans according to their development and/or production requirements.
Third-party Node Providers that support the platform by registering their full nodes and fulfilling query requests are included in an incentivization mechanism that allows them to receive a share of the funds coming into the platform via subscription plan fees. Additionally, all provider nodes have the option to create Staking Pools where they can stake BWR Tokens and receive an APY in order to increase their revenue for hosting full nodes on Blast supported blockchains.

API Usage

Blast offers a standardized Blockchain API service that covers all infrastructure aspects of Web 3 development. For each supported blockchain, users are able to generate a dedicated endpoint that will allow them access to the majority of RPC methods required for dAPP development and/or blockchain interaction. In the following sections of this documentation, you can find detailed steps for how to connect and generate your endpoints, as well as RPC and WSS usage examples together with platform limitations and payment conditions
Users joining the platform will be able to use the APIs for free within certain limits with the option to upgrade to one of our standard paid subscription plans or to contact us in order to create a customized plan suitable to their needs.
The platform currently supports crypto payments in stable coins in order to offer transparency and to allow its users to efficiently budget their infrastructure costs.

Registering as a Node Provider

In order to become a Node Provider on Blast, you need to already host or deploy a node on one of the Blockchain Networks currently supported. After registering their node's endpoints into the platform, on the condition that their node passes all the required tests, therefore meeting all the registration requirements, providers will start earning stable coin rewards as a share of the platform's total revenue. The percentage of revenue allocated to each node depends on the hardware requirements for running a node on each network as well as on the overall performance of the node in terms of availability, response time, and data integrity.
All the details regarding how performance and hardware scores are calculated and the requirements that need to be met by potential node providers will be documented when the next version of the application is released. The new version release will start with an incentivized testnet during which initial Node Providers will be onboarded into the platform.

Staking

To further incentivize Node Providers, in an effort to increase overall performance and reliability, a staking mechanism will be in place, allowing the creation of Staking Pools and giving third-party node owners the option to stake BWR tokens in order to earn an APY.
In order for a Staking Pool to become active and start producing rewards, Node Providers will be required to stake a fixed amount of BWR, which will be established at the beginning of the decentralization process. At least half of this amount will need to be supplied by the pool owner while for the other half, Node Providers will be able to receive delegations from other BWR token holders.
BWR token holders who wish to delegate their tokens will have the option to delegate directly to a specific Staking Pool but since the staking amount is capped, the staking slots for some Staking Pools might be limited. So, instead of delegating directly to a staking pool, users can delegate to a Delegation Queue which will automatically split the delegation and send it to the available slots on each staking pool. During the time that funds remain in the Delegation Queue, delegators will still receive an APY, although smaller compared to the APY coming from an active Staking Pool.
Last modified 1mo ago