Comment on page
⁉
FAQ
The list of FAQs below illustrates the concerns and issues that users faced during Testnet Phase II.
If you are using VMs just terminate it, create a new one and go through the installation again to prevent config conflicts
It won't work due to port/resource conflict
- 1.Open firewall on 80,443 port
- 2.Uninstall programs occupying port 80
- 3.run the script:
/massbit/massbitroute/app/src/sites/services/node/cmd_server nginx -tand check the status*You can SSH into your Massbit node/gw and copy paste that command to see if the config is ok. Make sure you have admin privilege.
- 1.Check spam / update / promotion box
- 2.If you can not find your email after step 1, please DM to @massbitintern#1665 in Discord for direct support
MassBit Team would like to inform community members about our technical support time, especially for those participating in MBR Testnet Phase II.
Weekdays: 5:00 PM UTC to 11:00 AM UTC (Next day).
Weekends: The response time may be slower than on weekdays.
The team finished lower bandwidth and response time requirements, which caused most nodes to fail during the verification process.
Temporary adjustment:
- Bandwidth: 1 Mb/s
- Respond time: < 500 millisecond
We urge everyone to create a new node and Login into the system.
Don't worry about the "Investigate" status, your nodes are still counted for reward. We just flag those cases to review.
If you don't want to delete your VPS and create a new one, you can run '
rm -rf /massbit', reboot your node, then install a new installation script from the web portal.It seems like you reuse the same installation script on a different host/vm. If you create a new VM/host, make sure you create a new node/gateway in the web portal and copy the new installation script.
It means your node/gateway did not pass the performance check. 95% of performance check traffic must be under 500ms.
I would suggest terminating and creating a new host/vm. Make sure you create a new node/gateway in the web portal and copy/run the new installation script.
It means Nginx is not set up properly on your node due to port conflicts with another process running. In addition, it can possibly cause the nginx configuration is not correct when multiple installation script is executed on the same host/VM/VPS.
We would suggest terminating and creating a new host/vm. Make sure you create a new node/gateway in the web portal and copy/run the new installation script.
In order to run node, you have to have at least 1 blockchain full node. Here are the references:
ETH: https://geth.ethereum.org/docs/install-and-build/installing-geth
DOT: https://wiki.polkadot.network/docs/maintain-guides-how-to-validate-polkadot
Once your MassBit node is reported. You will have to create a new VPS/VM and go through the installation with a new script again. The old VPS/VM 't be used, it will cause conflicts when you run a new installation script on it.
After your node is verified, it is still getting checked by Fisherman on other Gateways to make sure your node/gateway is fully functional. If there are any problems occurring during the check such as connectivity issues, offline node, or connection timeout, the status will switch back to “verifying”.
/massbit/massbitroute/app/src/sites/services/node/cmd_server _update nginx: [error] open() "/massbit/massbitroute/app/src/sites/services/node/tmp/nginx.pid" failed (2: No such file or directory) ++ /massbit/massbitroute/app/src/sites/services/node/mbr node nodeverify
After your node is "Staked", it is still getting checked by Fisherman on other Gateways to make sure your node/gateway is fully functional. If there are any problems occurring during the check such as connectivity issues, offline node, or connection timeout, the status will switch to "reported".
Basically, it looks like a website URL like this https://5f559996-d0c0-411c-aa29-685764e4612d.eth-mainnet.massbitroute.net/s9G0uxQd_GTze9M0qhGB6w.
Blockchain applications use this link to access data stored on a blockchain and submit transactions (like minting an NFT or transfer token …)
When the app access the URL, the nearest gateway serves the request (that’s why MB aims to be fast), then the gateway forwards the request to its nearest node in the same zone, then the node forwards the request to another computer that runs blockchain like ETH.
Massbit Node has a Blockchain Node (like ETH, BSC…) connected to it (MB node and blockchain nodes are 2 different types of nodes).
A node receives users' requests from nearby Gateways, then sends them to the blockchain node connected to it. The blockchain node process/write data to the blockchain and then responds back to the node. The node sends a response back to the previous gateway and then back to the user.
A gateway is an entry point to the MassBit network (that's why it's called a gateway). It serves its nearby users when they access the dAPI on their web3 apps. The more gateway and geo-location coverage we have, the faster the MassBit network becomes because the user can access a nearby gateway quickly.
You can be a node provider and run Massbit node/Gateway to earn a token reward, or you can use MassBit token to pay for dAPI usage. Your payment will be distributed back to node providers.
It is decentralized finance.
In Centralized finance (CeFi) - current banking system
- People must go through a trusted middle-man/entity (like commercial/investment banks) and ask for permission to transfer or loan money.
- Disadvantage:
- Those entities control users' data and activity.
- They can decide who can/can’t loan or transfer money.
- Money deposits into the back might be used for fraud or self-benefit activities without user content (not transparent).
- Policies are made by a few (head/CEO of those banks) and benefit a few.
All transaction data is stored on the blockchain, and anyone can review what happened in the financial system (transparent, less fraud). Users control their own data with the private key.
Policies are created through smart contracts. Smart contracts are open-source and can be reviewed by anyone to see how the system work, with no hidden rules (transparent). After review, if people think the policies (smart contracts) are fair, they will adopt and use them.
Basically, the developer translates financial policy into computer code. Smart contracts (loan or transfer policies) are executed by computers that run a blockchain, no human involved (no bias, no self-benefit, no fraud).
In Web2, users use products created by companies (centralized organizations) like Facebook, Twitter, and Netflix. Those companies' management chooses to censor what users can do/see/watch and use users' data without user's agreement for a different purpose (political, economic, conflict, self-benefits ....) -> centralized power and wealth to the hands of a few (like CEO, or managers).
Web3 fixes the centralization issue of web2.
- Everyone has an equal vote to decide what needs to be changed/created/updated, and none is better than another (similar to no government or managers in a company) (Exp: DAO).
- Everything is transparent (users know what is happening in a system, no fraud, no self-benefits between certain individuals) (Exp: Bitcoin, Defi).
- Users own and control their data/assets without going through a third party (you own, control, and decide how to use your asset/money. No bank, no government, no company needed, everyone decides how the economy works).
Any blockchain application that wants to connect to ETH and Polkadot.
Last modified 1yr ago