MassBit Route
Node/Gateway status

Hardware minimum recommendation

We encourage participants to prepare the system as below:
  • Node: 2 CPUs, 2GB Ram, 40GB SSD. 5Gbps Egress network bandwidth.
*A Massit 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.

Status Description

In the dashboard, there are many statuses to show the status of nodes and gateways operating in the system of MassBit Route.
  • After a new node/gateway is created on the web Portal and the installation script is successfully executed on your server, the node/gateway status changes from “Created” to “Installed.”
  • Once a node/gateway is approved, the node status shows as “Approved.”
  • Approved nodes are qualified for staking with unofficial Massbit tokens. You can obtain testnet tokens from the faucet channel on Massbit Route Discord
  • After nodes are selected to participate in Testnet, the reward will be calculated based on the time the nodes maintain “Staked” status in the Massbit network.
  • Nodes and gateways maintain “Staked” status while it correctly handles blockchain API calls to the blockchain data sources.
  • If a node/gateway experience issues and results in a performance downgrade or stop responding, a Fisherman component will flag the node, and the status changes to “Reported.”

How to maintain “Staked” status and earn daily rewards?

  • Fisherman is a component that keeps track of whether a node or gateway is qualified to join the MassBit network and remains “Staked” status and serves dAPI traffic by periodically checking.
  • When a node/gateway asks to join Massbit, and after they are officially part of Massbit, fisherman continuously checks to make sure nodes meet these criteria.
    1. 1.
      Fisherman makes sure Massbit nodes return results matching with base blockchain nodes such as block data, block hash, and runtime version. This ensures data integrity and prevents malicious actors from performing a man-in-the-middle attack
    2. 2.
      Average response time
    3. 3.
      Node’s blockchain data source is fully synchronized with
  • Nodes need to route blockchain queries to the nearest data sources, and the average response time for blockchain queries must be less than 1 second. Attention: this is AVERAGE response time, so that some responses can be more than 1s
    1. 1.
      The success rate of blockchain queries.
    2. 2.
      HTTP response code (200).
    3. 3.
      Each query has a timeout of 5 seconds. A query will fail if no result is returned within 5 seconds.
    4. 4.
      Data integrity: check if NODE return matching data with BASE node.
  • To receive a full daily reward, nodes or gateways must remain staked until the end of an Era, which is 24 hours.
Copy link
On this page
Hardware minimum recommendation
Status Description
How to maintain “Staked” status and earn daily rewards?