Now, we want to share more information about the **stages** of the development process in [Open Forest Protocol](https://www.openforestprotocol.org/). The development of such a complex project requires a well-planned approach that is structured into different stages. In this post, we will explore the various stages of development that the Open Forest Protocol team went through🌳. The challenges we faced: The NEAR network had been launched just two months before we started work on OFP’s technical **architecture** and **functionalities**. Therefore the main challenge that we faced was the risk of adopting a new and largely untested technology, with a limited tech inventory and the ongoing development of **basic functionalities**, which were a must-have for the [OFP](https://www.openforestprotocol.org/) to function as intended🍃. Due to the urgency of the climate cause — this is a fast-developing industry — **reforestation, afforestation, conservation mechanisms**, and standards are constantly **growing and improving**. Such rapid progress directly influenced the protocol’s development, demanding flexibility and an instant response to any changes demanded by the technical team🌱. The last major challenge was the complexity of the product being built. **MRV** in the forestry, conservation, and carbon economy requires sophisticated data reporting standards, so both the product and the technical teams were striving to **deliver comprehensive** and, at the same time, concise interfaces that would cover the necessary scope of requirements while making sure the **protocol** would still be engaging and easy-to-use👩💻.