BEPRO Network has released the Code as a Service Protocol! After a year of developing the architecture of the EVM protocol we are happy to finally announce this milestone and welcome users to a new concept, the Code as a Service Protocol.
The BEPRO Network Protocol is a fully decentralized marketplace and protocol aiming to create a trust-less bridge between Operators and Developers. You can connect with builders and other developers and trade your commits, review, and work for rewards in BEPRO, USDC, or other tokens.
Decentralize your efforts, empower your community
You will be able to leverage the power of decentralization to engage, as needed, with a talented community of developers and manage your development and open issues within a single platform.
Instructions on how to login
Now that we have released the mainnet, which premiered at Moonriver, a few actions will be needed from your side to use the protocol.
Step 1: Install Metamask. Find more information on how to install Metamask and use it (here).
Step 2: Register via Github. You should connect with your Github to integrate all the protocol functionalities mapped via IPFS. Learn more about here.
Step 3: There are 2 ways of getting BEPRO on Moonriver. Get BEPRO on SushiSwap or bridge your BEPRO from Ethereum Network to Moonriver. Read more here.
Attention: Always make sure you are interacting with the real BEPRO token smart contract address.
How to participate?
You will be able to participate in the protocol in 3 different ways:
- As an Operator;
- As a Developer;
- As a Token Holder;
Operators are teams or individuals who are leading the efforts to build products and software in an open-source framework. BEPRO Network will allow projects or teams to build products and applications in a highly flexible environment*. You can work with a small core team, or you can take the role of a single CTO, and then you can leverage the power of decentralization to engage, as needed, with a talented community of developers and manage your development and open issues within a single platform.
Developers are talented individuals looking to work on a per-request and feature basis. As a developer, you will be able to connect with builders and other developers and trade your commits, review, and work for rewards in BEPRO, USDC, or other tokens.
Additionally, as a token holder and member of the community, you can also be part of the network and support it. Besides the direct interaction between operators and developers, a fully decentralized management and dispute resolution model has been provided for the protocol. This means that as a member of the community you can be part of the network, even if you’re not an Operator or Developer.
The curation of the protocol will be done via the BEPRO token, and as a holder, you can participate directly in the network. Token holders will be able to help manage disputes, curate the system and provide development resources.
For all Operators, Developers, and Token Holders, our *Terms & Conditions apply.
A lot of interesting and important things are still in the pipeline as we want to build a strong ecosystem for everyone who wants to develop amazing software. Our continuous improvement will be focused on regular updates to constantly improve UI/UX, utility, and usefulness of the network.
Find out more about BEPRO Network’s roadmap here. All development only mentions the Protocol Side of Development.
We would like to thank everyone for their support, and for being with us along this amazing journey. And, without further ado please visit https://development.bepro.network to use the BEPRO Network Protocol live.
Influential Projects and Vision
BEPRO Network Protocol and our daily work are inspired and influenced by projects such as Gitcoin, Radicle, and other protocols for decentralized development. Our idea has always been to develop a solution for EVM as a Code as a Service Protocol, and we believe that this approach is the correct one.
Also, we’re already envisioning a v2 with direct integration that will enable other projects to use BEPRO Network Protocol in their open-source repos. You can see more in the Public Roadmap (link).