The Web3 Foundation, Polkadot’s equivalent of the Ethereum Foundation, announced a wave of funding for projects creating infrastructure and development tools for the ecosystem. With this move, Polkadot is ensuring future developers and users have a better experience building on the protocol.
Get Paid to Build on Polkadot
Creating sound infrastructure is a pre-requisite for a healthy blockchain network. Most smart contract platforms have a not-for-profit organization that helps fund the development needed for this infrastructure. Polkadot is no exception.
The Web3 Foundation is beginning its first-ever grants program. The categories being funded include infrastructure deployment, operations projects, and software development proposals. While this means DeFi projects cannot apply yet, teams building interoperability solutions, like SnowFork, are eligible.
Redspot (testing and development environment), Centrifuge and Substrate client (API provider), Polkascan (blockchain explorer), and Encointer (identity protocol) are the first four teams to submit their proposal for funding to the Web3 Foundation.
Teams building tools for Polkadot are strongly urged to apply for a grant to build out their idea.
Though excluded from this round, DeFi projects on Polkadot have had little funding issues these days. Acala, a Maker-like competitor, just raked in $7 million round of seed capital to build out its network.
But the importance of infrastructure funding cannot be understated. Building a robust application layer is essential, but without an equally strong infra layer, applications will not scale. Hence, the foundation’s decision to place foremost focus on funding this sector initially is in the best interest of Polkadot.
This article is strictly for informational purposes only. It is not a direct offer or solicitation of an offer to buy or sell, or a recommendation or endorsement of any products, services, or companies. CryptosOnline.com does not provide investment, tax, legal, business or accounting advice. Neither the company nor the author is responsible, directly or indirectly, for any loss or damage caused or alleged to be caused by, or in connection with, the use of or reliance on any content, goods, services or opinions mentioned in this article.