MassBit Route

Inspiration

The project was inspired by that Vitalik once mentioned the importance of full decentralization. https://twitter.com/vitalikbuterin/status/1247607628668309507

People who say "full decentralization is overkill, you only need non-custodial" are missing the point. A fully decentralized (or "serverless") application is valuable because it gives users the confidence that *it will always be there*, so you can safely build on top of it.

This is why eg. Uniswap, Tornado Cash, and the like so easily excite people to build ecosystems around them while more centralized alternatives fail. Liveness, not just safety.

If you build a dapp on top of fully decentralized/serverless infrastructure, then even if the rest of the community around that infrastructure goes away, your dapp can continue to use it; it may be weaker because of a smaller network effect, but it will still work.

it was also inspired by the Infura outage incident

What it does

We are building decentralized APIs and CDN for blockchain.

How we built it

Firstly we can build a verification protocol based on proof-of-stake. Basically, all works who participate in the MassBit Route need to stake MassBit tokens first and earn the reward for their work. The verification protocol is to make sure participants behave honestly. Otherwise, they will get recognized and penalized by the protocol which incentivizes workers doing the same task to verify each other. The verifiers will earn an extra reward of finding out the bad workers.

Secondly, we have to build a software of node running different blockchains: etc: Solana, BSC, ETH, Matic, etc... and also run extra software for the node to participate in the MassBit protocol (registration, verification, reward counting, etc..) - from our observation, the cost to run Solana in AWS or Google Cloud will be about 1.5k a month while renting a bare metal server in the data center will be just $400. They just purchase the machine then it will be a very good investment to participate in the MassBit network assuming they have to take care all of the DevOps work.

Lastly, we also need to build the gateway to route the traffic to the right blockchain nodes. The gateway nodes will also do API caching like the CDN of the blockchain. The gateway node will also have to stake and follow MassBit verification protocol.

Challenges we ran into

1/ Verification protocol on the substrate framework. 2/ Software for blockchain nodes 3/ Software for gateway nodes

Accomplishments that we're proud of

The project we are working on will make a big impact on the decentralization of web3 apps. We believe the APIs should be provided by the community, but by not a single entity. We have built the software for blockchain nodes as well as the gateway nodes which will be eventually run by the incentivized community.