【Network Introduction】MassBit

9 Mins read
Don’t forget to follow us before you read.

Network Detail

Brief Introduction

MassBit’s mission is to become an innovative infrastructure to make DeFi & Web3 apps development faster, easier, more reliable, and more cost effective. Furthermore, MassBit works with small API providers and validators to form decentralized gateways, with whom, validators can earn more rewards and serve numerous DeFi and Web3 apps.




MassBit Route

Testnet Phase II — Opening — Time: From 18th May 2022

After the success of the 1st Testnet for MassBit Route (MBR) product, MassBit is ready to launch Testnet Phase II til the Mainnet. During the period, they will continuously test, upgrade products, and confirm the reward month by month in the launch with more features.

Cross-chain Indexing

MassBit provides the infrastructure to index the data from different blockchains, such as Substrate, Ethereum-compatible chains and especially fast blockchains like BSC, Matic and Solana. Besides, MassBit also supports indexing logic in different languages as well (Rust, AssemblyScript, TypeScript).

MassBit Insights

Massbit Explorer allows you to check the information regarding all major blockchain networks. This project will allow users to verify price, transaction count, current epoch, market cap, block and slot height.


Detailed routine can be checked here:

Teams and Partners

Team Experience


If you are interested in building MassBit, you can submit an application for their Angel Program.

* The Angel Program has multiple roles available, and this program is a way to have a changing impact on the development of a leading web3 infrastructure project.

Those joining the Angel Program will help shape the future of web3 and the MassBit project pipeline. Application Page.


MassBit has three investors (refer from CypherHunter):


MassBit Tech Overview

Massbit Route is a blockchain distribution network (BDN) operated and governed by users all over the globe. It provides decentralized applications access to different blockchain APIs by routing request network traffic to a blockchain node that has optimized response time. In addition, Massbit Route is built to provide performance-optimized access to blockchains and aims at eliminating blockchain API single-point of failure by forming a global network of independent Node Providers.

We build a network operated and serviced by users that provide fast and redundant access to blockchain sources. Massbit Route facilitates a network of Gateways and Nodes infrastructure in 6 different zones around the world: Asia; North America; Africa; Europe; South America; Oceana.

Users can join Massbit network as Providers from any of those regions by running Gateway and Nodes that are connected to blockchain data-sources such as Ethereum or Polkadot. As the MassBit network grows in the number of Nodes and Gateways, the network becomes highly available and redundant. When a Provider experiences an issue with their nodes, blockchain API requests will be served by other Providers, which eliminates single-point-of-failure in Web2 CDN architecture.


Github Homepage

Massbit Core (MC) is the orchestrator of the entire Massbit network. It works along with other components to onboard new Gateways and Nodes onto the Massbit network, and make sure traffic is routed by Gateways and Nodes effectively. When Providers need to operate Nodes or Gateways in the Massbit network, they need to obtain a set of instructions created by the MC from the Portal for their servers. By executing the instructions in the form of Bash shell script, the server will negotiate with MC and Verification Service if it is qualified to participate in the MassBit routing network. Once a Gateway is successfully verified in the Massbit network, MC provides a list of dAPI entry points and Nodes in the same zone the Gateway needs to server request and forward traffic respectively.

As Massbit Route network grows globally and blockchain traffic needs to be directed optimally, MC constantly updates Gateways with a set of traffic routing and handling instructions to adopt a change within Massbit network. For example, when some nodes in a zone go offline, new nodes are added or Consumers adjust the request rate for dAPI entrypoint, MC generates a new set of configuration for all of the Gateway in the zone.

Tech Components

Gateway Manager

Gateway Manager the DNS component of Massbit network based on the opensource project gdnsd. It runs as an authoritative DNS system of the Massbit network, and can be seen as a directory for all Community Gateways and Nodes around the world. When a dApp query blockchain API through a Massbit dAPI entry-point, it needs to lookup the IP address for the dAPI entry-point through their configured recursive DNS servers. If the recursive DNS servers do not have the entry for the dAPI entry-point, they will perform authoritative lookup to Gateway Manager. With geographic IP capability, Gateway Manager resolves the DNS lookup with the IP of the Gateway closest to the requesting dApp based on the source IP in request Header.

Session Manager

When a dAPI entrypoint is created by Consumer, a dynamic DNS entry is created by Gateway Manager and resolved to the nearest Gateway IP based on the source IP in the request header. Once traffic reaches a Gateway, in order to accept the API request from Consumers, it needs to obtain a dAPI session key from Session Manager. The session key is only valid for a certain amount of time and will be renewed for the dAPI entrypoint if needed.

In addition, Session Manager also controls the usage of the dAPI entry-point. Consumers need to deposit an MBR token for the dAPI entrypoint in advance to pay for the cost of dAPI usage. Depending on the amount of MBR deposit, Consumers will receive a corresponding quota for dAPI usage. Session Manager will inform if a dAPI entrypoint is out of quota and Gateways will block incoming requests until more MBR token is funded for the dAPI.

Session Manager also prevents malicious actors from bypassing dAPI payments and sending blockchain requests directly to Gateway public IP. Without a valid session key and a dAPI entrypoint, Gateways will reject the requests destined to their public IP. This will maintain the security of the network and form a building block for Massbit Route tokenomic.


Massbit Route is constructed to be a reliable global blockchain distribution network, which distributes content to users anywhere around the globe with low latency and response time. For that reason, user-operated nodes and gateways need to meet certain performance criteria to remain routing traffic in the Massbit network and earn rewards.

Fisherman can be seen as a monitor service that periodically keeps track of Nodes and Gateway traffic routing performance. Data returned by Nodes and Gateways always need to be consistent with blockchain data sources to maintain data integrity and prevent malicious actors from performing man-in-the-middle attacks.

If any Nodes or Gateways experience a technical issue such as network connectivity, or high latency, Fisherman can also detect and eliminate those malfunctioned components and offload traffic to other healthy nodes. More specifically, gateways that are reported by Fisherman are removed from the Gateway Manager’s directory, and will no longer be able to serve dAPI blockchain requests. When a Node is eliminated due to a technical issue, Massbit Core notifies all of the Gateways in the same zone to stop forwarding blockchain requests to that node.

When Nodes or Gateways are reported by Fisherman, they are no longer part of the Massbit network and are not eligible for staking reward. This service plays an important role in Massbit network redundancy and high-availability.


Stats collects telemetry from all verified Gateways and Nodes in the Massbit network. The service provides different metric data to allow the Portal to visualize Nodes and Gateway performance with charts. In addition, it calculates and keeps track of the available quota for each dAPI based on the amount of MBT token deposit.

Massbit Routing Mechanism

In Massbit network, Gateway Manager, Community Nodes and Community Gateways form a global blockchain CDN network in order to optimize blockchain API request and response time.

Based on the public IP of each community-run Node and Gateway, a global geographic map of verified and staked Gateways is continuously updated. When a dApp sends a blockchain API request through Massbit Route API Entrypoint created by a Consumer, based on the global network IP map, the request is forwarded to a Gateway in which its zone is the same or closed to the request source IP.

Each Gateway constantly updates Massbit Core to maintain a list of verified Nodes in its zone. From the gateway, the request is then forwarded to one of the nodes in the same zone, which will then proxy the request to the blockchain data-source associated with the node.

When a node or gateway experiences issues such as poor CPU, memory, and network performance which result in high latency and response time, it will be deregistered from the Massbit network by Fisherman. Only nodes with “staked” status in the Massbit network can serve API requests and earn token rewards to guarantee the stability of the entire network.

Because Massbit Gateways, Nodes, and blockchain source nodes are operated by independent providers, single-point of failure is eliminated. Fisherman ensures DNS entries of offline or malfunctioned Nodes and Gateways are removed from the network and makes sure blockchain requests are forwarded through active nodes, which maintains redundancy for the Massbit network.


Token Functions

1. Node/Gateway staking and reward for Providers

2. Transaction fee

3. Provider Incentive Pot

4. Consumer dAPI Quota

5. Delegation

MBR Testnet

Overview Introduction

The main purpose of this Testnet is to introduce the core functionality of MassBit Route to the community that MassBit has been developing over the past few months. Building a blockchain distribution network is a challenging task, as we do not own and manage the nodes or control the traffic flow.

In this phase, anyone will be able to create nodes, and an automated process will select nodes in each zone to allow the nodes to be staked and earn token rewards at IDO. Staked nodes and gateways become part of the MassBit network and serve dApi requests during the TestNet period.

New Features for MBR Phase Ⅱ

1. Staking and claiming the reward for verified node/gateway resource with the unofficial token.

2. Updated dashboard.

3. New UX on onboarding flow.

4. Increased response time: 1000ms.

5. Faucet provides unofficial tokens for users to stake nodes and gateways.


Allocation for rewards: 200,000 $MBT per month for 100 approved nodes and gateways.

Total supply of MBR product: 10,000,000,000 $MBT.

That being said, every approved node/gateway earns 2,000 $MBT per month. Node/gateway daily reward (called A) = 2,000 $MBT / 30 days = 66.7 $MBT.

Total reward per month = Number of days in “staked” status x 66.7 $MBT.

*The (A) is only counted when the provider remains node/gateway in “staked” status for 24 hours from the time of staking.

*The target of approved 100 nodes & gateways per month will be changed by the demand of the consumer side (dAPI).

*The monthly reward is closed and calculated every month’s last day.

*The confirmation of the previous month’s reward is sent to the email on the 10th day of the following month.

Steps to Join

Time: From 18th May 2022

Step 1: Sign up / Log in at

Step 2: Check the email to verify the account.

Step 3: Set up node/gateway through the guidance.

Step 4: Check the approval of your node/gateway within 24 hours after step 3. Once a node/gateway is selected, the node status shows as “Approved.”

Step 5: Join the MassBit discord server and get a token from the faucet channel. Check the guide on how to get unofficial tokens here.

Step 6: Stake $MBT token for approved nodes/gateways.



100 approved nodes & gateways will be expected in 6 different zones.

Higher chance for approval: Nodes with higher resources and network bandwidth that provide stability/availability and satisfy the network benchmark baseline have a higher chance of being selected by an automated process.

Hardware Requirements

Node: 2 CPUs, 2GB Ram, 40GB SSD. 5Gbps Egress network bandwidth. (A Massbit node requires a blockchain data source node (ETH or DOT full or archive node) to be created.)

Gateway: 4 CPUs, 4GB Ram, 80GB SSD. 5Gbps Egress network bandwidth.

Node Approval Process

When a Node or Gateway joins Massbit, it needs to go through different states before it can serve dAPI traffic.

  • Created: Node/Gateway information (name, zone, blockchain type that is served by this node, blockchain node IP) is registered with Massbit network. Based on the registered information, an installation shell script is generated for the new node.
  • Installing: When the installation script is executed on a new server that needs to join Massbit network, the status changes to Installing, and public IP of Node/Gateway is recorded to Massbit chain
  • Verifying: When the installation completes on the new server, it will proceed with the verification process for eligibility to join Massbit network.

Node Verification Service

Massbit Route becomes a faster and more reliable BDN when the number of Community Nodes and Gateway increase. Nodes and gateways need to meet certain requirements in order to be part of the Massbit global network.

When a Node requests to join the Massbit network, Verification Service checks if the Node is able to forward requests to its blockchain datasource and return result matching with the blockchain data source such as block data, block hash and runtime version. If all checks pass the validation process, the node becomes a part of Massbit network, and ready to receive traffic from Gateways in the same zone.

In each zone, a minimum of 1 Node is required in order for a Gateway to be verified. Without any Node or blockchain datasource, it is unnecessary to run a Gateway in that zone because it introduces some routing overhead, and traffic will eventually be routed to a nearest zone.

When a Gateway needs to join the Massbit network, Verification Service will validate if the Gateway has obtained a list of Nodes in its zone from Massbit Core and whether it can proxy traffic to the Nodes properly. If blockchain data returned by Gateway is correct and matches with data from the Node and blockchain datasource in that zone, the Gateway is verified and its public IP is updated in the Gateway Manager directory.

Set-up Docs

Testnet — How to run Massbit Gateway?

How to run Massbit Node?


About BlockPower

Our Staking Services

👏Cosmos 👏Osmosis 👏Tezos 👏Ethereum 👏Juno 👏Celestia 👏Provenance 👏Aptos

Why Choose Us to Manage Your Assets

👏 Historical

BlockPower almost grew together with the establishment of the PoS consensus.

For instance, we have become Cosmos Genesis Validator since March 13, 2019.

👏 Experienced

BlockPower is one of the earliest participating service providers in Cosmos Network and Tezos Network. Furthermore, we have colorful experience in operating other networks like Juno, Osmosis, Aptos and so on (not only include Mainnet but also contain Devnets ). We have rich experience in emergency escalation, which reflects our instant crisis response capability.

👏 Communicated

BlockPower is actively participating in governance (like voting proposals and discussing in forums and discord channels), and what’s more, we have our own blog, disclosing information frequently.

WebsiteBlogMediumTwitterDiscord 丨Telegram

Leave a Reply

Your email address will not be published. Required fields are marked *